-
Notifications
You must be signed in to change notification settings - Fork 67
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
How to configure DAWN to kick "legacy" devices? #215
Comments
I also try to achieve that, I see constant kicks in the log, but the client stays happily connected. I also can confirm a disconnect in the UI or a From what I understand https://github.com/berlin-open-wireless-lab/DAWN/blob/master/CONFIGURE.md#note-1-legacy-clients mentions Mh, while reading https://github.com/berlin-open-wireless-lab/DAWN/blob/master/CONFIGURE.md#kicking-method-2-absolute-rssi again one may assume that dawn
wireless
OpenWrt 22.03.5 r20134-5f15225c1e / LuCI openwrt-22.03 branch git-23.119.80898-65ef406 |
Looks like the code to do that is currently commented out. |
I have a few devices that don't seem to respect the 802.11v signal to move to another AP. I thought that setting
eval_probe_req
,eval_auth_req
,eval_assoc_req
to 1 would have it properly kick these devices but it still seems to not work. It simply keeps trying to issue a kick (according to the system log) to no avail. (NOTE: forcibly disconnecting it using the hostapd ubus interface makes it roam to the nearest AP instantly)OS: OpenWrt SNAPSHOT r22528-0c53801968 / LuCI Master git-23.093.56957-2145121
Using hostapd-wolfssl
The text was updated successfully, but these errors were encountered: