Ok, so what are we looking for in your web search results? Need to be specific...
Two Cases usually was happening
1. r36168, the user devices may connect unexpected wifi ap. For instance, I wanted to connect the device to dd-wrt 2.4 ap but it connected to dd-wrt 5.8 ap Mandatory. Using the ath2, the users needed to disable the ath1 broadcast and change different name of ap.
2. Now, the 2.4G wifi ap is an idling. No devices can connect
In WRT32X, I think it is a bug!
In WRT1900ACSV2, I assume my config had problem but it is operating.
So I hope that DD-WRT should consider this bug!
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Tue Jun 16, 2020 9:25 Post subject:
Let's wear out a rut in the rug, going in circles. I give up. Feel free to peruse the issues log for the upstream driver repository: https://github.com/kaloz/mwlwifi The Marvell drivers have known issues and the manufacturer no longer supports the hardware. So, not sure what magical miracle you are expecting.
Zyxx wrote:
Unfortunately our Linksys (Marvel chipset driven) devices are orphaned.
Marvell ceased the support for our devices at least two years ago, have a look at the official repo:
https://github.com/kaloz/mwlwifi/
Somewhere down in the issue tracker, a fired employee advices to not await any updates anymore.
To make things even worse, Marvell sold its chipset division to NXP.
Nobody knows if NXP even knows about the "open source" driver.
To sum it up, they promised to deliver but never did very well.
You can use your device as a performant router without wifi and add an additional AP for maximum performance, or "live with it" and use the sometimes strange Wifi.
My advice:
If possible return the WRT32x of yours and try to get hold on a much better supported device like Netgear R7800...
Since my WRT1900 acs v2 does its job quite well, I'll stay with it, but if it dies:
Never ever again a Linksys-Marvell product for me.
