Posted: Fri Apr 12, 2019 7:32 Post subject: Kong R7000 VAP Connection Failure Workground is annoying me
I’m running Kong AC Build 39345M but this issue existed on previous builds. I have 2 VAP’s on my 5ghz radio and if I reboot my clients are unable to connect to them. It’s like my client is sending the wrong WPA2 AES encryption key. I see others on this forum are having the same problem.
After many frustrating and sleepless nights of nvram erases and complete rebuild's, I managed to figure out a tried and true fix to make my VAP’s connectable again.
If I go into the Basic 5Ghz Wireless Settings and choose Disable Wireless SSID broadcast on the last 5ghz VAP, hit Apply Settings, then re-enable SSID broadcast, hit Apply Settings then all will be well and my clients can connect. Initially I did this for all 5ghz VAP's, one-by-one, but then noticed that it worked if I did it for just the last one. Hitting apply and not save is crucial.
Does anyone know what is causing this bug exist and how can we get it resolved? I'm a sys/net admin not a coder. All I can do to help is offer workaround that I am able to reproduce and hope that someone more code minded can figure out a true bug fix.
Something is broken after reboot and disabling/re-enabling SSID broadcast is the only way to fix it. Curious if this resolves the issue for others?
Last edited by ryanbtc on Fri Apr 12, 2019 7:36; edited 1 time in total
Joined: 18 Mar 2014 Posts: 12839 Location: Netherlands
Posted: Fri Apr 12, 2019 7:35 Post subject:
Unfortunately it is a known and frustrating bug, below a snippet of earlier threads:
Quote:
From approximately mid 2018 VAP's on Broadcom units are problematic, you cannot connect or do not get an IP address. There are workarounds :
1) When VAP is not working at boot; workaround startup command Administrationn/Commands, Save as Startup:
sleep 10; stopservice nas; stopservice wlconf; startservice wlconf; startservice nas;
2) Alternative way to get VAP working: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=317181
Ya on one of my sleepless nights I saw that post and tried those commands and they didn't work for me. Only the step by step disable, apply, renable, apply of the VAP SSID's work.
egc wrote:
Unfortunately it is a known and frustrating bug, below a snippet of earlier threads:
Quote:
From approximately mid 2018 VAP's on Broadcom units are problematic, you cannot connect or do not get an IP address. There are workarounds :
1) When VAP is not working at boot; workaround startup command Administrationn/Commands, Save as Startup:
sleep 10; stopservice nas; stopservice wlconf; startservice wlconf; startservice nas;
2) Alternative way to get VAP working: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=317181
From approximately mid 2018 VAP's on Broadcom units are problematic, you cannot connect or do not get an IP address. There are workarounds :
1) When VAP is not working at boot; workaround startup command Administrationn/Commands, Save as Startup:
sleep 10; stopservice nas; stopservice wlconf; startservice wlconf; startservice nas;
When I run those commands I get the following response from 'startservice wlfconf' :
eth1: Not supported
eth1: Not supported
eth2: Not supported
eth2: Not supported
Is this an issue preventing my VAPs from coming back up? Would really like even a scriptable work around then having to disable/renable SSID broadcast.
Saw some others posts and tried with stop/start nas service and also with start wlconf.
The nas service wasn't necessary for me to include in my commands.
The key was cron being stopped first and then the interfaces being brought up individually with 'wlconf {if} up' and not using startservice wlconf .
Now if we can get the bug fixed permanently that would be great. This workaround is viable for me now.
Joined: 04 Jan 2007 Posts: 11563 Location: Wherever the wind blows- North America
Posted: Sat Apr 13, 2019 11:45 Post subject:
I have never had any luck with the provided manual commands either. But this one does work for me on both R7000 and R6300v2 units. See if this works for you as well.