Posted: Fri Dec 06, 2019 10:51 Post subject: 4WAY_HANDSHAKE_TIMEOUT after reboot
I've installed v3.0-r41517 std (11/11/19) to my Asus RT-AC68U C1 to my complete satisfaction.
However, everytime I reboot the router (which isn't often) I can't connect to the secondairy SSID's on my wl0 interface. wpa_supplicant tells me the authentication failed with a 4WAY_HANDSHAKE_TIMEOUT. The first SSID on wl0 is allways available and working, which helps a lot to fix the problem, namely:
The work-around I have found so far is to re-apply the wireless security settings tab, which probably magically clears some cached keys or credentials. Is this a known problem and if so, would clearing these stale keys or credentials on boot be a possibility?
Joined: 18 Mar 2014 Posts: 12877 Location: Netherlands
Posted: Fri Dec 06, 2019 17:20 Post subject: Re: 4WAY_HANDSHAKE_TIMEOUT after reboot
mrvanes wrote:
I've installed v3.0-r41517 std (11/11/19) to my Asus RT-AC68U C1 to my complete satisfaction.
However, everytime I reboot the router (which isn't often) I can't connect to the secondairy SSID's on my wl0 interface. wpa_supplicant tells me the authentication failed with a 4WAY_HANDSHAKE_TIMEOUT. The first SSID on wl0 is allways available and working, which helps a lot to fix the problem, namely:
The work-around I have found so far is to re-apply the wireless security settings tab, which probably magically clears some cached keys or credentials. Is this a known problem and if so, would clearing these stale keys or credentials on boot be a possibility?
Not sure but are talking about a VAP (wl0.1)?
If so you probably still need the VAP workaround, add the following to your startup (Administration/Commands, Save Startup):
Below some pointers which might help to get the best out of DDWRT and out of the forum:
1. Research your router, start with the supported devices wiki:
https://wiki.dd-wrt.com/wiki/index.php/Supported_Devices .
2. In the supported devices wiki you can see if your router is supported and what architecture your router has and if you are lucky also an install guide/wiki.
3. Post in the right forum, from the former step you can see if your router is Broadcom, Qualcomm/Atheros, Marvell or other, use that forum to post router specific questions, for networking questions post in the Advanced Networking forum and for other things in the General Questions forum.
4. When posting always state router model, build number and when applicable the Kernel version.
Describe your problem and how you think it can be solved.
Give as much detail as you can also provide your network setup if applicable.
For your Network setup, state what wiki you have used: https://wiki.dd-wrt.com/wiki/index.php/Linking_Routers
5. When posting pictures make sure the maximum width is not more than 600 pixels.
6. Do not hijack a thread, meaning do not post your own problem in someone else's thread. Just start your own thread.
7. If your post is answered and your problem solved, mark your thread with [SOLVED] (the header of your first post).
8. Do NOT use the router database, builds can be found at:
https://dd-wrt.com/support/other-downloads/?path=betas%2F2019%2F
All builds are beta including those from the router database.
9. Before uploading a new build to your router, research the build by looking in the build threads.
This is an example of a build thread for build 41328 for Broadcom routers:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=321699&highlight=41328
Search build threads with the search function and search on build number.
10. Use the build threads from the former step to report success or problems.
11. For older Broadcom routers (Linksys WRT54 and E series) read the peacock thread although some of it is outdated: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=51486
Builds can be found in the Broadcom directory for Linux kernel 2.4, in Broadcom_K26 for Linux K2.6 and in Broadcom_K3X for Linux K3.X.
12. If you are sure you have discovered a bug, after asking and querying the forum, you can report a real bug in the bug tracker: https://svn.dd-wrt.com/
This is also the place where the commits/changes to the source are administrated.
13. Recommended reading:
https://forum.dd-wrt.com/wiki/index.php/Main_Page https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=54845 https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=54959
14. If you are happy with DDWRT and want it to live on then donate:
https://dd-wrt.com/donations/ _________________ Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399 Install guide R7800/XR500:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614 Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Will try the new build and if that fails, the startup script. Thx for pointing that out.
egc wrote:
Below some pointers which might help to get the best out of DDWRT and out of the forum:
Was this really necessary?
Thanks again for helping me out and apologies for not complying to the rules.
Best regards,
Martin
If I thought you did not follow the rules I would have said so.
As you seem new to DDWRT (your second posting) I just want you to get the max out of DDWRT, the software is very versatile but has its peculiarities and the forum and Wiki are not always up to date.
Posted: Sat Dec 07, 2019 11:08 Post subject: Re: 4WAY_HANDSHAKE_TIMEOUT after reboot
egc wrote:
If I thought you did not follow the rules I would have said so.
As you seem new to DDWRT (your second posting)
DDWRT is so easy I didn't need any help until now
egc wrote:
Have fun and if you have questions just ask, we are here to help.
Well, 41664 sends my router into a bootloop, so may want to consider removing it from the downloads for RT-AC68U?
Took me the better part of the morning restoring via ASUS rescue tool and then DDWRT + Backup file. I'm on Linux, so had to fall back to Windows VM, never a pleasant experience...
Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Sat Dec 07, 2019 13:00 Post subject:
I saw that. I don't know how BS runs his builds. I know for all of the development stuff I do here, the entire tree is cleaned to pre-compiler launch status so things don't break. I don't know if it's a Subversion quirk or what, but I usually have no issues with Git. Northstar has been an ongoing thing, but if that were the specific case, then more than the AC68s would be affected.... this is definitely Asus-specific, methinks.
