“Ignore event 44, not interested”

[CB7]

Hi,

I for the life of me can’t find anything about this in ASUS documentation, nor on Google, nor on this forum nor was ChatGPT any help (though it suggests its a “WPS probe”, but cannot explain why it believes that - it linked to a thread here that speaks of kernel panics heh).

As of today, my logfiles are flooded with the following and I was wondering if anybody knows what causes it?

Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:02 kernel: ignore event 44, not interested
Jul 28 22:29:07 kernel: ignore event 44, not interested
Jul 28 22:29:07 kernel: ignore event 44, not interested
Jul 28 22:29:07 kernel: ignore event 44, not interested
Jul 28 22:29:07 kernel: ignore event 44, not interested
Jul 28 22:29:08 kernel: ignore event 44, not interested
Jul 28 22:29:08 kernel: ignore event 44, not interested
Jul 28 22:29:08 kernel: ignore event 44, not interested
Jul 28 22:29:08 kernel: ignore event 44, not interested
Jul 28 22:29:13 kernel: ignore event 44, not interested
Jul 28 22:29:13 kernel: ignore event 44, not interested
Jul 28 22:29:13 kernel: ignore event 44, not interested
Jul 28 22:29:14 kernel: ignore event 44, not interested
Jul 28 22:29:14 kernel: ignore event 44, not interested
Jul 28 22:29:14 kernel: ignore event 44, not interested
Jul 28 22:29:14 kernel: ignore event 44, not interested
Jul 28 22:29:14 kernel: ignore event 44, not interested

-edit-
Apologies:
Asus AX3000v2, running 3004.388.9_2-gnuton1

 

[ColinTaylor]

Router model?
Firmware version?
Did you make any changes just before these messages appeared?

 

[Ripshod]

I seem to remember event 44 was related to DFS (detecting radar?) on broadcom wifi. That may not be the case these days though.

 

[dave14305]

Example of where the message originates:

asuswrt-merlin.ng/release/src-rt-5.04axhnd.675x/bcmdrivers/broadcom/net/wl/impl87/sys/src/wl/sys/wl_cfg80211.c at bd8391bd768028c94582908850f30adf7f517466 · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

No idea what it means.

 

[Justinh]

Sounds AI-ish to me, when a logger has a personal preference!

 

[CB7]

Router model?
Firmware version?
Did you make any changes just before these messages appeared?

Sorry! AX3000v2 with latest Gnuton (3004). No changes.

I seem to remember event 44 was related to DFS (detecting radar?) on broadcom wifi. That may not be the case these days though.

Checked it to be sure, wifi log is showing its broadcasting on its normal frequency with no events. (It is using a DFS channel, but cleared and no log entries)

Example of where the message originates:

asuswrt-merlin.ng/release/src-rt-5.04axhnd.675x/bcmdrivers/broadcom/net/wl/impl87/sys/src/wl/sys/wl_cfg80211.c at bd8391bd768028c94582908850f30adf7f517466 · RMerl/asuswrt-merlin.ng

Third party firmware for Asus routers (newer codebase) - RMerl/asuswrt-merlin.ng

github.com

No idea what it means.

Thank you, this is very interesting. So I looked at that and see the “WLC_E_PROBREQ_MSG” which with info from bcmevent.h seems to suggest that’s “44” and says as description: /* probe request received */.

… This got me thinking what would send continuous probes. Could be anything, but my thoughts go out to the repeater. Turns out I can’t reach it with SSH, so something is up with it. So I’ll ask my wife to unplug it and will report back.

 

[CB7]

Alas, the repeater unfortunately wasn’t the culprit.

 

[CB7]

Ok so the repeater thing did point me in the "right" direction. When back online it was showing a backhaul link-speed of ~20Mbit on 5Ghz and a sky-high rssi; it was definitely not connecting to the router in question that was throwing these errors (closest by, very strong signal). Probably losing connection intermittently, hence the earlier SSH issues. So... There was something about the errors showing 5 or 6 times in a recurring pattern, and some devices reportedly showed heavily degraded WiFi performance. (Source: stream of complaints from wife 'n kids started seeping in ) Conclusion: multiple devices, including the repeater were probably trying to connect to the router but couldn't establish a connection; and on every attempt it'd log the 44 error thingy. Explains the poor performance on some devices (though strangely: not all, the iPad was showing full speed and allegedly no buffering on TV.), they were all falling back to another AP two floors up for their WiFi. (either directly or through the repeater, which would just be repeating the very poor signal from upstairs.)

I would've really loved to diagnose this as I want to know why that elusive error suddenly popped up, what its origin is and why is it suddenly started doing that. But I know how annoying a poor connection is and I'm a sucker to complaints of my family, so I did what any sane person would've done as a last-resort cop-out: reboot everything. The problem has now been resolved, everything can connect again and repeater confirms (~1200Mbit 5Ghz link). But my curiosity is absolutely not satisfied and I'm... Kind of hoping it comes back when I'm back home so I can have a thorough look at it.

Thank you all for the quick replies!

 

[Tech9]

Don't worry about it. The router itself is not interested, obviously.

 

[CB7]

Don't worry about it. The router itself is not interested, obviously.

That's just a decoy to prevent you from having a closer look at what it's really doing