Posted: Sun Jul 19, 2020 18:20 Post subject: No ath2?
Just updated to 43471 and seem to have lost ath2. In my config, I have some IoT devices that won't connect to the Marvel 2.4 network due to a driver issue in the Marvel code so I had been doing the work around of using ath2 to host a B/G network (which has worked fine).
I tried a factory reset to see if was an old config issue but still no Ath2. Did some Google searching but can't find anything recent (all posts from 2017-2018). Did it get removed somewhere along the way?
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Jul 19, 2020 21:23 Post subject: Re: No ath2?
whistler wrote:
Just updated to 43471 and seem to have lost ath2. In my config, I have some IoT devices that won't connect to the Marvel 2.4 network due to a driver issue in the Marvel code so I had been doing the work around of using ath2 to host a B/G network (which has worked fine).
I tried a factory reset to see if was an old config issue but still no Ath2. Did some Google searching but can't find anything recent (all posts from 2017-2018). Did it get removed somewhere along the way?
Thanks for any insights!
The first occurrence of this was a while back. None of the recent builds support using ath2 which is supposed to be for radar detection anyway. If you were using ath2 prior to upgrading you will need to revert back to an older build to restore it. Once restored you can then disable it and upgrade accordingly. Once upgraded "DO NOT ENABLE" ath2 as it will cause all kinds of strange problems with wifi and on the first reboot will disappear again but continue to cause strange problems. If you persist in using ath2, don't upgrade to any of the recent builds. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
I've been using 39715 for a long time. When I tried to migrate to a newer versions (40xxx, 41xxx, 42xxx), I had various issues. With automount, with SMB, with WiFi, with hanging, one or more of those at a time. Since then I switched to semi-manual mounting, so that's one thing off the list. I've started using 43471 recently and it seems okay (read as: everything that I've used on previous build is working and didn't need any adjustments).
Ath2 is present in my case but I've disabled it long ago as using it created nothing but problems.
So bad news on 43471. I've been running it now for a week, and been having similar issues to what I was seeing with the other 43xxx build. Namely, devices are having a hard time joining the 5GHz network, and some IoT devices are having a hard time with the 2.4GHz network as well. Rebooting the router seems to fix the problem for a few hours, but then it pops up again. Any other recommendations on builds?
I'm at 33 days uptime on 43471 on my 3200ACM and 1900ACSv1. However, I do experience what you are describing on some IOT devices from time to time. Just some ideas to try on the problematic IOT devices in no particular order: 1) Try setting static names, IPs and leases in DNSmasq with "dhcp-host=" options, 2) try moving the device - sometimes an inch makes a difference, 3) try forcing the device to use a particular radio with mac address filtering. Good luck.
While the IOT thing is annoying, I think a bigger deal is the 5GHz network not working reliably. I use the 5GHz network as an uncrowded band for devices that require fast access (laptop to NAS, etc), so I need it in operation.
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Sun Jul 26, 2020 2:34 Post subject:
Jozer99 wrote:
No luck with G only and WMM. Anyone suggest any other builds?
I may be way off base on this but you indicated that you had good success with an old build. Go back to it.
I have no idea why the newer builds don't like weaker signals but with 1900's if I use a newer build (other than r31924) I get the same sort of problems you are experiencing. This only happens with devices/routers both 2.4Ghz and 5Ghz that are on the fringe distance (Signal -70db or there about). In my case it was particularly noticeable with a 1900 that I have about 500' away on WDS and everytime it would rain the signal would weaken and the link would drop. to the router. Also many of my devices would also periodically drop from the 2.4Ghz on the remote router. Because I had a spare 1900 I now use the remote link WDS with two 1900's.
You will see from my profile that I still use the 3200's successfully both 2.4Ghz and 5Ghz. I moved all my 2.4Ghz from the master 3200 to the added 1900 as I have some esp8266 devices, but still retain the 2.4Ghz on the 3200 WDS slave unit which has no problems with IP Cameras and Laptops and Android devices connecting to it.
As has been said many times throughout the forum, the 3200 can be quite annoying with WiFi but it does work well with non-fringe signals.
Your specific problem maybe related to the same as I have with 1900's where the newer builds are range sensitive. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Joined: 04 Aug 2018 Posts: 1447 Location: Appalachian mountains, USA
Posted: Wed Jul 29, 2020 13:40 Post subject:
After not doing so for a couple of years, Linksys finally distributed updated driver blobs not long ago. I believe they made it into dd-wrt somewhere around January. Linksys doesn't distribute source code, and one dare not stay with the older drivers and miss out on the fix to whatever security situation finally prompted them to update drivers on older designs, so the dd-wrt community is stuck with the weird, glitchy behavior.
There are those here who know this story way better than I do, so if anyone else pipes up, do listen. _________________ 2x Netgear XR500 and 3x Linksys WRT1900ACSv2 on 53544: VLANs, VAPs, NAS, station mode, OpenVPN client (AirVPN), wireguard server (AirVPN port forward) and clients (AzireVPN, AirVPN, private), 3 DNSCrypt providers via VPN.
