From 90a0daf4fe2aca55169c5ff7862b867516837c30 Mon Sep 17 00:00:00 2001 From: Hauke Mehrtens Date: Sat, 4 May 2019 01:58:53 +0200 Subject: hostapd: use config option CONFIG_NO_LINUX_PACKET_SOCKET_WAR Instead of patching the workaround away, just use the config option. Signed-off-by: Hauke Mehrtens (cherry picked from commit 9b4a27455c17c00698ce7ce24e0bcad419c6319e) --- package/network/services/hostapd/files/wpa_supplicant-full.config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'package/network/services/hostapd/files/wpa_supplicant-full.config') diff --git a/package/network/services/hostapd/files/wpa_supplicant-full.config b/package/network/services/hostapd/files/wpa_supplicant-full.config index 5f48d59eeb..2e9328234a 100644 --- a/package/network/services/hostapd/files/wpa_supplicant-full.config +++ b/package/network/services/hostapd/files/wpa_supplicant-full.config @@ -308,7 +308,7 @@ CONFIG_BACKEND=file # in a bridge for EAPOL frames. This should be uncommented only if the kernel # is known to not have the regression issue in packet socket behavior with # bridge interfaces (commit 'bridge: respect RFC2863 operational state')'). -#CONFIG_NO_LINUX_PACKET_SOCKET_WAR=y +CONFIG_NO_LINUX_PACKET_SOCKET_WAR=y # IEEE 802.11w (management frame protection), also known as PMF # Driver support is also needed for IEEE 802.11w. -- cgit v1.2.3