Posted: Tue Dec 22, 2020 11:31 Post subject: Frozen WiFi Problem on - r45036 (WRT1900ACSv2)
Hi Forum,
Is anyone having issues on the new version r45036?
Yesterday I upgraded from an old r3xxxx version - everything went fine.
I don't have any complex config or anything, just regular access point.
My LAN seems to be without issue, and the laptop on wifi also didn't show any problems.
Our phones however, they stay connected just fine, but after a while of not using them, the WiFi becomes completely unresponsive.
If I switch WiFi off/on, they become fine again.
Seems to be they just freeze or lockup after not using them for a while.
Does anyone know what's causing this, or have any suggestions?
Maybe there is a rock solid older build that someone can suggest for me?
I have attached my Wifi settings, which I configured using the DDWRT recommended settings wiki.
The same at me with 44849
I'm investigating this issue.
Intertesting because I can't decide whether the phone (S10+) has an issue or the router.
Now I disabled the battery optimalization.
Maybe....
The same at me with 44849
I'm investigating this issue.
Intertesting because I can't decide whether the phone (S10+) has an issue or the router.
Now I disabled the battery optimalization.
Maybe....
Well mine is working fine now on the recommended firmware version.
So in my case it was related to the router firmware.
I have the same problem today. My router is wrt32x which is uptime about 8 days. This morning, all smartphone cannot connect to WRT32x but RPi and ESP32 IoT devices are still connected to WRT32x without connection problem. (AP mode only)
Firmware: DD-WRT v3.0-r45036 std (12/18/20)
Time: 11:15:24 up 8 days, 11:05,
load average: 0.07, 0.02, 0.00
WAN IP: 0.0.0.0
Joined: 04 Aug 2018 Posts: 1055 Location: Appalachian mountains, USA
Posted: Thu Jan 14, 2021 15:34 Post subject:
Set beacon interval back to the default 100. Really strange intermittent wifi problems happened to me from changing it even slightly. I saw this behavior across three different WRT1900ACSv2 routers on an April 2020 build. Apparently the drivers for our WRTblah routers don't handle nondefault BI values well at all.
While we are here, I have found that TurboQAM (in my WRT1900ACSv2) appears to do nothing useful. I have read that it only works (to radically increase connection speed) at close range, which is logical, but I can be less than 10 ft (3m) from the router and still get nothing from it. I don't think this is any part of your problem, but maybe add it to your future-tweak list once you actually get things working OK. _________________ Five WRT1900ACSv2's on 42926, 44048.
VLANs, VAPs, NAS, client-mode travel router, OpenVPN client (AirVPN), DDNS, wireguard servers, wireguard clients (AzireVPN), two DNSCrypt DNS providers (incl Quad9) via OpenVPN/wireguard clients.
Set beacon interval back to the default 100. Really strange intermittent wifi problems happened to me from changing it even slightly. I saw this behavior across three different WRT1900ACSv2 routers on an April 2020 build. Apparently the drivers for our WRTblah routers don't handle nondefault BI values well at all.
While we are here, I have found that TurboQAM (in my WRT1900ACSv2) appears to do nothing useful. I have read that it only works (to radically increase connection speed) at close range, which is logical, but I can be less than 10 ft (3m) from the router and still get nothing from it. I don't think this is any part of your problem, but maybe add it to your future-tweak list once you actually get things working OK.
Thanks for the tip.
I had my 5GHz set to 449 and 2.4GHz set to 523
I'll see how it does with them both set back to 100.
