Mysterious messages in ZenWiFi AX system log

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

RogerSC

Part of the Furniture
Well, this surprised me. Getting a lot of assoc/auth/disassoc messages for wired clients. I thought that these were related to wifi clients, but no, the MAC Address here is an Apple TV streaming box connected via wired ethernet. I should mention that I'm using firmware version 9.0.1.4.386_46197, and all my clients are working well:

Code:
Oct 28 00:44:13 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind A8:81:7E:A2:DE:45, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-80
Oct 28 00:44:13 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 00:44:13 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 00:44:15 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:44:15 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:57:06 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 00:57:06 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 00:57:08 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:57:08 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:59:06 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 00:59:06 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 00:59:08 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:59:08 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:59:30 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 00:59:30 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 00:59:32 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 00:59:32 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:00:59 disk_monitor: Got SIGALRM...
Oct 28 01:04:26 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 01:04:26 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 01:04:28 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:04:28 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:06:26 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 01:06:26 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 01:06:28 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:06:28 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:08:34 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 01:08:34 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 01:08:36 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:08:36 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:10:34 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 01:10:34 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 01:11:17 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind F0:B3:EC:0B:31:64, status: 0, reason: Disassociated due to inactivity (4), rssi:-48
Oct 28 01:11:17 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind F0:B3:EC:0B:31:64, status: 0, reason: Previous authentication no longer valid (2), rssi:-48
Oct 28 01:11:18 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:22:32 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 01:22:32 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 01:22:34 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:22:34 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:25:21 wlceventd: wlceventd_proc_event(527): eth5: Auth F0:B3:EC:0B:31:64, status: Successful (0), rssi:0
Oct 28 01:25:21 wlceventd: wlceventd_proc_event(556): eth5: Assoc F0:B3:EC:0B:31:64, status: Successful (0), rssi:-49
Oct 28 01:25:22 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Oct 28 01:25:22 wlceventd: wlceventd_proc_event(508): eth5: Disassoc F0:B3:EC:0B:31:64, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

I have no idea if there's anything I can do about all this seemingly pointless activity for a wired ethernet client *smile*. Yes, I could lower the syslog message level so that I didn't see them, but this just bothers me.
 
Last edited:

ColinTaylor

Part of the Furniture
They're definitely wireless messages. Wired devices don't do assoc/auth/disassoc and wlceventd is the wireless event daemon.

I don't know anything about Apple devices but check whether it uses the same MAC address for both its wired and wireless interfaces. It may have connectivity issues with Ethernet and is failing over to WiFi.
 

RogerSC

Part of the Furniture
Well, interesting. That's what I thought, too...so I've switched the particular Apple TV box from wired to wifi, and the messages went away...whaddaya know? I'll see how that works for a while. I do like having my streaming boxes hard-wired, but we'll see. We do have really great wifi from the ZenWiFi *smile*. I would have switched it to wifi last night before posting, but I couldn't get access to the box at that time, being in a bedroom and all.

By the way, already replaced the ethernet jumper cable and did a "Restart" on the Apple TV box...need I say that didn't help *smile*?

To summarize, this is my plan, stopping when the problem's fixed and performance is good, of course:

1. Pull the power off the Apple TV box for about 5 minutes, and see if that helps.

2. Reset the Apple TV box in question and see if that helps. Lot of work there, but worth it if it fixes whatever's causing this issue. I do have "keep your Apple TV boxes in synch" set, so Apple might help to get the reset box back to where it was, using the other one that we have as a reference. Of course, that might cause the other one to get wiped, but Apple wouldn't do that, would they *smile*.

3. Block the Apple TV wifi Mac Address on the router, that should at least block the messages. Be interesting to see how it performs in that configuration, as well. Least desireable, since whatever's going on with the Apple TV box, it'll still be happening...however, no problem streaming with the box.

4. Leave the Apple TV box on wifi, pending long-term performance check.

I'd like to turn off the wifi interface on the Apple TV box, but I don't think that Apple would give their customers that degree of freedom *smile*.
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top