-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WDS: No traffic after group key handshake #242
Comments
how is your group key configured on ap side and how is your group key configured on station side. you missed something very important. your hostapd and your wpa supplicant config. a wrong group key config leads to non working connections (or just unicast but no broadcast/multicast is working) |
I will check it. You can disable group rekey as temporary solution. Thanks. |
@BrainSlayer Perhaps I am missing something... but I have not configured any group key; I just have an AP configured using "psk-mixed+aes" and WDS active on the main router, and a STA also configured with WDS active on the "wireless extender". |
group key cipher its what i mean. not the key itself. |
With group re-keying disabled, traffic has been flowing for a while, and everything seems to work as expected. |
Problem still present at driver 10.3.4.0-20180118 with firmware 9.3.2.4. |
Yes. This one is still under working |
Sure, I'll try your work-around. How do I dissable group key handshake? |
@gufus Just add a |
Thanks! WDS STA stays up now :-) |
Main router: WRT3200ACM running LEDE 17.01.4 plus updated (commit 843d00c) mwlwifi drivers.
Wireless extender: WDR4300 running LEDE 17.01.4
I have been running these two devices using "relayd" for a couple of months, and the connection was fast and rock solid. I recently changed to WDS using recent drives, and have noticed that traffic stops completely when the AP router performs a "group key handshake".
These are the logs at the AP when the STA is powered on and a connection is established:
Then traffic flows normally and everything works as expected; some time later these logs appear:
And traffic halts completely; however, after a few minutes I see these messages:
And traffic beings to flow again.
The text was updated successfully, but these errors were encountered: