Posted: Wed Mar 25, 2020 19:33 Post subject: WRT3200ACM 5GHz wifi stops responding
I am currently running build 42557 on my WRT3200ACM router and have found that I seem to be having some issues with the 5GHz wifi network. For some reason, after a few hours of it working just fine, the 5GHz wifi network stops working and new association attempts won't work. Here's what I see in the syslog:
Mar 25 14:18:08 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -65 (Accepted)
Mar 25 14:18:09 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -62 (Accepted)
Mar 25 14:18:09 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -59 (Accepted)
Mar 25 14:18:09 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -57 (Accepted)
Mar 25 14:18:10 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -57 (Accepted)
Mar 25 14:18:10 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -57 (Accepted)
Mar 25 14:18:10 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -57 (Accepted)
Mar 25 14:18:11 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 MLME: auth request, signal -57 (Accepted)
Mar 25 14:18:53 DD-WRT daemon.info hostapd: ath0: STA 64:16:66:a7:5c:01 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mar 25 14:19:52 DD-WRT daemon.info hostapd: ath0: STA 1c:f2:9a:45:7d:a8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mar 25 14:19:57 DD-WRT daemon.info hostapd: ath0: STA 1c:f2:9a:45:7d:a8 MLME: auth request, signal -64 (Accepted)
Mar 25 14:19:57 DD-WRT daemon.info hostapd: ath0: STA 1c:f2:9a:45:7d:a8 MLME: auth request, signal -64 (Accepted)
I don't know why it seems to do this, but it's rather frustrating when this causes various systems here at home (my TV, my Google Home Hub, etc.) to be unable to connect to the wifi network until I powercycle both the router and the device.
Is this a case where I need to upgrade to a newer firmware?
Newer firmware may or may not help, but the current build r42803 reverted to a previous wifi driver firmware binary that may be more stable for you.
The bigger problem is with the mwlwifi driver, and issues will not be resolved thanks to Marvell selling their wifi assets to NXP (and Linksys sold to Foxconn).
Smart Devices, Home Automation, Internet of Things, ESP8266, doorbells, you name it, these things generally will make your router lose its marbles.
64:16:66:a7:5c:01 and 1c:f2:9a:45:7d:a8 please locate these two devices on your network by MAC address. What are they?
The former is a Nest device. Probably either the Nest Hub or the thermostat. The latter is a Google device. All things being equal, I suspect that the latter is the Google Nest Hub and the former is the Nest thermostat.
Edit: Looked in the Google Home app and the latter MAC is definitely the Google Home Hub and the former would most likely be the thermostat.
While I don't wholly disagree with you about at least some of the "smart" devices, un-smarting my home isn't going to fly with the family. Given that this isn't an option, is there a next best option?
The only issue I've seen on R7800 turned out to be user error, a bad wireless security configuration.
However, you might be able to recreate the problem by jamming a Marvell board into an Atheros router shell casing.
Show-stopping wifi driver issues aside, problematic client devices are usually poorly documented. Their available or recommended wireless security options may not match reality.
Channel and width settings that are "non-standard" may confuse them too.
These nest things have both both 2.4 and 5 GHz bands simultaneously active, but automatically connect to one at a time.
blkt - My wifi security settings are all using WPA2 personal with AES encryption. The 5GHz network is the one most frequently having problems, though the 2.4 network occasionally burps as well.
I'm about to flash with the March 25th firmware... The whole reason I went down this road in the first place was because of the Cablehaunt vulnerability in Broadcom cable modems. I'm trying to prevent that from being exploited from my internal network.
I just got a WRT3200ACM last week and have also had a bit of a time getting it stable as well. I am seeing the exact same behavior as eplossl (and others) in that both the 2.4 GHz and 5 GHz work well for about a day or so, sometimes 2 or 3 days but eventually I have to reboot to fix the issues. My syslog looks identical to eplossl's where the devices seem to connect, authenticate, but then never receive an IP and it just times out (and these devices include my One Plus 7, Nintendo Switch and others, so not just Smart Home devices).
I had issues getting my "Smart" Home devices, Doorbell Camera, Robot Vacuum, and Garage Door to connect to the 2.4GHz at all. But after disabling WMM per blkt's suggestion, all of those devices are able to connect to the 2.4GHz. But eventually, like the 5 GHz, the 2.4 GHz just stops accepting connections after a day or so (usually around the DHCP lease expire).
I was using r42747 when experiencing these issues. I have just upgraded to r42803 and I will update the thread if that shows any improvement. But I just wanted to add my 2 cents to the thread to see if there is anything I can help try out.
Do the Linksys Firmwares even provide stability (if I decided to revert back to them as a last resort? I'd really prefer not to).
Outside of these issues, the Router is a beast when it's connected. It has made my Work From Home life this past week so much better.
My configuration settings are below in case there is any further suggestions on things I might be missing. Thanks!
ath0 (5GHz)
Wireless Mode: AP
Wireless Network Mode: Mixed (Haven't tried any other types yet)
Channel Width: Full (20 MHz)
Channel: 36
Wireless SSID Broadcast: Enabled (different than 2.4 GHz)
Security: WPA-2 Personal AES
WMM: Enabled
ath1 (2.4GHz)
Wireless Mode: AP
Wireless Network Mode: Mixed (Haven't tried any other types yet)
Channel Width: Full (20 MHz)
Channel: 8 (was the quietest looking channel according to WifiMan).
Wireless SSID Broadcast: Enabled (different than 5 GHz)
Security: WPA-2 Personal AES
WMM: Disabled
ath2
Wireless Network Mode: Disabled
Other Info
Current build: r42803
DHCP Lease Time: 1440
Maximum DHCP Users: 75 (Right now it's at 75 because at times in a 24 hour period, with like 2 of everything around the house, the family has managed to get pretty close to the default 50, so I changed to 75 to see if that helped).
UPnP: Enabled
1 Static DHCP Lease
The whole reason I went down this road in the first place was because of the Cablehaunt vulnerability in Broadcom cable modems. I'm trying to prevent that from being exploited from my internal network.
I found this after a brief search. "The flaw occurs because of a spectrum analyzer running on port 8080 in most instances. If you can block that port to your cable modem (at your AP, for instance), you eliminate the threat. It can only be fixed by the carrier."
So, until a firmware update is pushed out by your ISP you can port block for now.
For 2.4 GHz and 5 GHz problems, please first upgrade to r42803 as there is a revert to an older known stable wifi FW binary blob.
WMM off is a possible IoT workaround for the 2.4 GHz radio interface, but you will also need to test different Wireless Network Modes (G-Only, BG-Mixed, NG-Mixed as examples). Save and reboot.
Everyone has different client devices so there is no one solution that fits all, only to find the right combination that works for you.
You may need to locate and isolate devices triggering the authentication loops by connecting them to another access point, maybe an old wifi router.
It may appear as if most your devices are having issues, but once the offending devices are removed the other clients should stabilize.
There are reports of instability with this year's two new stock Linksys firmwares. YMMV.
For what it's worth, stock firmware 1.0.6.186168 from January 16, 2018 was stable for me.
Re the cablehaunt thing: Exactly. However, the stock firmware is completely unable to block outbound ports. This firmware, however, is.
I got up this morning and the 5GHz network is hosed again, despite having upgraded to 42803. I'm currently getting this for my TV as it tries to connect to the network:
Mar 28 10:07:34 DD-WRT daemon.info hostapd: ath0: STA e0:d0:83:ea:36:f9 MLME: auth request, signal -55 (Accepted)
Mar 28 10:07:35 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -63 (Accepted)
Mar 28 10:07:35 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -63 (Accepted)
Mar 28 10:07:35 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -62 (Accepted)
Mar 28 10:07:35 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -63 (Accepted)
Mar 28 10:07:46 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -62 (Accepted)
Mar 28 10:07:47 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -65 (Accepted)
Mar 28 10:07:47 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -63 (Accepted)
Mar 28 10:07:47 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -62 (Accepted)
Mar 28 10:07:48 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -65 (Accepted)
Mar 28 10:07:48 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -62 (Accepted)
Mar 28 10:07:48 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -62 (Accepted)
Mar 28 10:07:48 DD-WRT daemon.info hostapd: ath0: STA d4:9d:c0:95:f1:b8 MLME: auth request, signal -67 (Accepted)
Nothing else seems to be happening in the logs. Weirdly, only the 5GHz band seems to be impacted for me.
Yeah, sadly I am still seeing the same behavior with the r42803. I just lost my 5 GHz. So 24 hours pass, DHCP lease expires, things loose connection. Like eplossl though, I too only seemed to have lost the 5 GHz today. The 2.4 GHz seems unaffected (so far).
I will see if I can isolate what device(s) may be causing an issue. (I have a couple of hunches). I was starting to notice slow-downs and certain disconnects even with my old router (TP-Link AC1750). I may hook that back up with a different SSID like you suggested and try connecting certain devices to it 1 at a time to see if I can find the culprit.
I am also facing this issue, after a few days, 5Ghz stops responding. I noticed it starts with my android device and the other devices (iphone) are still working. But when you try to restablish the connection of IOS devices it also stops working.
