aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/generic/patches-4.4/040-0001-mtd-bcm47xxpart-limit-scanned-flash-area-on-BCM47XX-.patch
diff options
context:
space:
mode:
authorSujith Manoharan <m.sujith@gmail.com>2017-01-11 07:39:22 +0530
committerStijn Tintel <stijn@linux-ipv6.be>2017-01-11 04:01:07 +0100
commit593240075f8d3074164ffce99ab67a88277f9fb3 (patch)
treeff03aabcd112fb9be6bc8338bf32bdf715a77731 /target/linux/generic/patches-4.4/040-0001-mtd-bcm47xxpart-limit-scanned-flash-area-on-BCM47XX-.patch
parentb95494baedbc46d088550e18370e3507af4f732e (diff)
downloadupstream-593240075f8d3074164ffce99ab67a88277f9fb3.tar.gz
upstream-593240075f8d3074164ffce99ab67a88277f9fb3.tar.bz2
upstream-593240075f8d3074164ffce99ab67a88277f9fb3.zip
wpa_supplicant: Fix mesh encryption config
wpa_supplicant allows only SAE as the key management type for mesh mode. The recent key_mgmt rework unconditionally added WPA-PSK - this breaks interface bringup and wpa_s throws this error message: Line 10: key_mgmt for mesh network should be open or SAE Line 10: failed to parse network block. Failed to read or parse configuration '/var/run/wpa_supplicant-wlan0.conf Fix this by making sure that only SAE is used for mesh. Signed-off-by: Sujith Manoharan <m.sujith@gmail.com>
Diffstat (limited to 'target/linux/generic/patches-4.4/040-0001-mtd-bcm47xxpart-limit-scanned-flash-area-on-BCM47XX-.patch')
0 files changed, 0 insertions, 0 deletions