summaryrefslogtreecommitdiff
path: root/package/network/services/hostapd/patches/001-4addr-fix-reconnecting-client-on-connection-lost.patch
blob: 5c8b6622c9a257bee024de6c9db9e3da38312b6f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
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) {
 		/*