summaryrefslogtreecommitdiff
path: root/package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch
diff options
context:
space:
mode:
Diffstat (limited to 'package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch')
-rw-r--r--package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch25
1 files changed, 0 insertions, 25 deletions
diff --git a/package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch b/package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch
deleted file mode 100644
index 5c8b662..0000000
--- a/package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch
+++ /dev/null
@@ -1,25 +0,0 @@
-From: Matthias May <matthias.may@neratec.com>
-Date: Tue, 5 Jul 2016 15:00:43 +0200
-Subject: [PATCH] 4addr: fix reconnecting client on connection lost
-
-When a 4addr client suddenly looses its connection (no deauth/deassoc)
-the AP still thinks it is connected.
-If the client reconnects before the AP timeoutes the client, traffic
-cannot flow.
-
-Fix this by making sure the WLAN_STA_WDS flag is unset in the sta->flags
-when the client completes association.
-
-Signed-off-by: Matthias May <matthias.may@neratec.com>
----
-
---- a/src/ap/ieee802_11.c
-+++ b/src/ap/ieee802_11.c
-@@ -2826,6 +2826,7 @@ static void handle_assoc_cb(struct hosta
- new_assoc = 0;
- sta->flags |= WLAN_STA_ASSOC;
- sta->flags &= ~WLAN_STA_WNM_SLEEP_MODE;
-+ sta->flags &= ~WLAN_STA_WDS;
- if ((!hapd->conf->ieee802_1x && !hapd->conf->wpa && !hapd->conf->osen) ||
- sta->auth_alg == WLAN_AUTH_FT) {
- /*