So I bought a WRT3200ACM for VPN performance and now my Nest Thermostats constantly go offline and connecting with the Nest App is completely spotty. Before this I was using a TP-Link WDR3600 and it worked flawlessly with DD-WRT build 36698, which is the same build I am using on the WRT3200ACM. Any advice on getting them working. I have tried some of the stuff I have seen online, like increasing DTIM, but that hasn't fixed the issue. I also tried increasing the Beacon Interval but my Lenovo Ultrabook doesn't like it when I set it to 200 ms. The Ultrabook refuses to connect to the Internet although it connects to the 3200ACM just fine. Thanks in advance for any advice.
Same advice as Adamcarter, install release r35898 from May 7th. That's the last release that didn't suffer the WiFi disconnect/hang issues. The device connecting but having no internet connection is a good description of the 'hang' part.
Thanks for the advice. Can I flash that without performing a factory default reset and will it save my configuration. Kinda like upgrading using stock Linksys firmware. Thanks.
Thanks for the advice. Can I flash that without performing a factory default reset and will it save my configuration. Kinda like upgrading using stock Linksys firmware. Thanks.
I flashed to r35898 using the Wiki instructions for the WRT3200ACM. Worked perfectly and kept all configuration settings. Now we will see if the Nest Thermostats stay online and connected to the internet.
They have been rock solid, no going offline at all. So since you say never update, I take it this version is near perfection and everything is working? I see it appears that a new version just came out, but I will heed the advice provided and stick where I'm at. Everything seems to be working great for me on r35898. Thanks again for the advice.
Also, u may want to read the stickies. About not putting dd-wrt on both partitions on the 3200acm.
You may have already, some like to have the original oem linksys firmware on one partition and one dd-wrt on the other partition _________________ WRT3200ACM V1 r39267 std (03/22/19) OpenVPN client
Also, u may want to read the stickies. About not putting dd-wrt on both partitions on the 3200acm.
You may have already, some like to have the original oem linksys firmware on one partition and one dd-wrt on the other partition
Nope, I read the WRT3200ACM specific forum before flashing DD-WRT at all. I was pleasantly surprised to see that it had dual partitions. After flashing DD-WRT I used the process spelled out in the the WRT3200ACM thread. Used command "ubootenv set boot_part 1", didn't reboot, and flashed r35898 over r36698. Worked perfectly. So far everything is working as expected. Unfortunately that forum thread also recommends using the latest build, and admittedly, I didn't read the entire thread.
Is there anything with build r35898 that is glaringly faulty? I have now read some of the other threads about the frustration with BS seemingly ignoring the 6319 SVN. Glad it's fixed, unless r35898 has issues that would affect me, I might just stick with it, unless there is good reason to upgrade.
Its still early days with the new build. With the addition of wpa3 which maybe 2 or 3 devices in the world have, i am sure all the new stuff added broke other things. Will take some time to flesh out. _________________ WRT3200ACM V1 r39267 std (03/22/19) OpenVPN client
I'm running Firmware: DD-WRT v3.0-r37305 std (10/10/18 on my WRT3200AC and I have what sounds like the same problem now where I have to disable all DNSmasq funtions to get it to connect to the nest service. I'm not clear on how was debugged so if this is not the same behavior I can open a new post instead.
Joined: 17 Feb 2010 Posts: 611 Location: Yorkshire (GOC)
Posted: Wed Jan 23, 2019 12:31 Post subject:
jeffsko wrote:
I'm running Firmware: DD-WRT v3.0-r37305 std (10/10/18 on my WRT3200AC and I have what sounds like the same problem now where I have to disable all DNSmasq funtions to get it to connect to the nest service. I'm not clear on how was debugged so if this is not the same behavior I can open a new post instead.
Why not try a more current build first, to see it it has been fixed? You can easily revert back. _________________ Linksys WRT32X v1 - r45677
Linksys WRT1900AC v1 - r45677
TP-Link Archer C9 v1 - r45677
Firmware: ftp://ftp.dd-wrt.com/betas/2021/
