slurmsmckenzie
Occasional Visitor
I'm using an AX86U and XD4 in an AiMesh system which I originally setup in Feb 2022 with the latest stock FW etc. - I only had it running for 3-4 weeks because of unexplained issues with an IP camera that I could not live with (see https://www.snbforums.com/threads/ax86u-issue-with-hikvision-ip-camera.78705/). In that time I had zero problems with my Logitech Squeezeboxes, which was a blessing as I'd been nervous upgrading to AX class equipment would cause problems with them, but it didn't - I'd disabled AX anyway as I don't have any devices that use it yet.
5 weeks ago I set the AX86U & XD4 system back up again (I had a plan to use a mini access point with the IP camera which seems to work) and until the last few days it has all been flawless - not a single problem that I have noticed. Until a couple of days ago, when my Squeezebox radios starting having massive connectivity issues. I have three of them and one is able to reconnect due to using the "wlanpoke" add-on, but that only lasts a certain amount of time and eventually it needs a reboot too. The others are failing regularly and won't re-connect without a reboot, many times they are failing in the middle of actively streaming audio and only 20-30 minutes after being rebooted. What I see in the system log when this happens is always this:
Nov 15 08:05:17 wlceventd: wlceventd_proc_event(530): eth6: Auth 00:04:20:xx:yy:zz, status: Successful (0), rssi:0
Nov 15 08:05:17 wlceventd: wlceventd_proc_event(559): eth6: Assoc 00:04:20:xx:yy:zz, status: Successful (0), rssi:-48
Nov 15 08:19:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 00:04:20:xx:yy:zz, status: 0, reason: Disassociated due to inactivity (4), rssi:-48
Nov 15 08:19:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 00:04:20:xx:yy:zz, status: 0, reason: Previous authentication no longer valid (2), rssi:-48
Nov 15 08:20:00 wlceventd: wlceventd_proc_event(511): eth6: Disassoc 00:04:20:xx:yy:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
I find it a bit galling that the log says "Disassociated due to inactivity" when the device was in the middle of streaming music. Seems to me there is a problem with functionality or the wording of the log when I see that given the device is very much active at the time. Given this is happening across all three radios and nothing has changed with them I can't see that it is a hardware problem with the radios themselves.
Just to note that I've done all of the normally recommended things - reset everything to oblivion before setting up, use 8 character SSIDs, disabled Smart Connect, Airtime Fairness, Roaming Assistant etc., configured 2.4GHz to 20MHz, all of that - plus all three radios are bound to an AiMesh node. On stock FW 388_20566. Current system uptime is 36 days.
As well as wanting to solve the above issue, I can't help but wonder - why does this happen suddenly after 5 weeks of zero issues? I also had 4 weeks of no issues back in Feb. Nothing has changed but the weather, and I hope I can assume this won't have anything to do with it!
If anyone has any thoughts on the issue itself or generally why something like this would suddenly happen it would be much appreciated.
5 weeks ago I set the AX86U & XD4 system back up again (I had a plan to use a mini access point with the IP camera which seems to work) and until the last few days it has all been flawless - not a single problem that I have noticed. Until a couple of days ago, when my Squeezebox radios starting having massive connectivity issues. I have three of them and one is able to reconnect due to using the "wlanpoke" add-on, but that only lasts a certain amount of time and eventually it needs a reboot too. The others are failing regularly and won't re-connect without a reboot, many times they are failing in the middle of actively streaming audio and only 20-30 minutes after being rebooted. What I see in the system log when this happens is always this:
Nov 15 08:05:17 wlceventd: wlceventd_proc_event(530): eth6: Auth 00:04:20:xx:yy:zz, status: Successful (0), rssi:0
Nov 15 08:05:17 wlceventd: wlceventd_proc_event(559): eth6: Assoc 00:04:20:xx:yy:zz, status: Successful (0), rssi:-48
Nov 15 08:19:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 00:04:20:xx:yy:zz, status: 0, reason: Disassociated due to inactivity (4), rssi:-48
Nov 15 08:19:59 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 00:04:20:xx:yy:zz, status: 0, reason: Previous authentication no longer valid (2), rssi:-48
Nov 15 08:20:00 wlceventd: wlceventd_proc_event(511): eth6: Disassoc 00:04:20:xx:yy:zz, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
I find it a bit galling that the log says "Disassociated due to inactivity" when the device was in the middle of streaming music. Seems to me there is a problem with functionality or the wording of the log when I see that given the device is very much active at the time. Given this is happening across all three radios and nothing has changed with them I can't see that it is a hardware problem with the radios themselves.
Just to note that I've done all of the normally recommended things - reset everything to oblivion before setting up, use 8 character SSIDs, disabled Smart Connect, Airtime Fairness, Roaming Assistant etc., configured 2.4GHz to 20MHz, all of that - plus all three radios are bound to an AiMesh node. On stock FW 388_20566. Current system uptime is 36 days.
As well as wanting to solve the above issue, I can't help but wonder - why does this happen suddenly after 5 weeks of zero issues? I also had 4 weeks of no issues back in Feb. Nothing has changed but the weather, and I hope I can assume this won't have anything to do with it!
If anyone has any thoughts on the issue itself or generally why something like this would suddenly happen it would be much appreciated.