Posted: Tue Nov 03, 2020 23:56 Post subject: Effective workarounds for bridged VAPs not working at boot
Creating this thread with the single purpose of listing which VAP workarounds actually work for specific router models and build versions. I'm intending that posts in this thread are only to confirm working configurations to make it easier to find them.
This thread is not looking for posts confirming that Wifi generally works, this is specifically referring to builds that are released with the issue listed as:
VAPs not working at boot fixed for unbridged VAPs with r40564:40566. Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas (there are a few alternatives, search).
For example, I tried a couple of workarounds for Netgear R7000 before I found one that worked, so that was easy. However, for R7000P, some people in other threads seem to be referring to having it working but I have tried all the workarounds I can find and multiple firmware versions and still do not have it working. That has taken some time to test all those combinations. It would be great if working configuration information could more easily be found.
Apologies for any confusion. I am no expert on these matters, you are probably much better informed. I will try to give some more background.
The WNDR4000 is an additional upstairs access point in our house, not the main wan side router. It has an extra VAP as a guest network. This VAP would not work properly at boot. VAP is visible but clients fail to connect.
I have added this bit of code to the Startup section, under Administration->Commands.
I cannot tell why it works. It is one of the options listed in the OP of this thread under "Some possible workarounds that I have found are:". Running this from the Startup section causes my VAP to accept client connections.
Feel free to ask for further clarification. If it would be helpful I can see if can pull more information from my access point for troubleshooting.
I went back to the OP and you guys are right. The cron bit wasn't there. I must have been confused with another piece of code. However, this snippet does help my router to get the VAP accessible. Shoot me, I don't understand why but it does work.
1. If Broadcom has closed-source proprietary drivers, why do Buffalo sell routers with dd-wrt preinstalled that stop working? That's dd-wrt's fault for not keeping compatibility even with these few routers.
5. YOU feel free to dig into the source code and submit patches. After all dd-wrt is the one selling routers with that firmware preinstalled. I payed for a dd-wrt router and I expect a dd-wrt router to work or at least to be fixed. I don't expect every single router model to be fully supported, but what's the point of having a few officially supported and sold dd-wrt routers if not total compatibility?
4. If It's not a high priority to fix the few routers sold with dd-wrt installed, what is? To have as many broken betas for as many devices as possible? 10 years of broken builds and there is not a single combination of (not 54g) modern router + build perfectly working. Not even the routers sold with dd-wrt preinstalled.