Re: [v2, 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode
Wright Fengwrote: > When setting wpa_auth to WPA_AUTH_NONE(1) in AP mode with WEP security, > firmware will set privacy bit and add WPA OUI in VENDOR IE in beacon and > probe response. The security type in softAP beacons confuse the > supplicant in client side, and the user client will see [WPA-?] in > supplicant scan result. So we set WPA_AUTH_DISABLED in softAP mode with > OPEN security. > > Signed-off-by: Wright Feng > Acked-by: Arend van Spriel 3 patches applied to wireless-drivers-next.git, thanks. fdfb0f94bfb7 brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode 0ec9eb90feec brcmfmac: Add support for CYW4373 SDIO/USB chipset 99976fc08412 brcmfmac: fix wrong num_different_channels when mchan feature enabled -- https://patchwork.kernel.org/patch/9878545/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Re: [PATCH v2 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode
On 8/3/2017 11:37 AM, Wright Feng wrote: brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode When setting wpa_auth to WPA_AUTH_NONE(1) in AP mode with WEP security, firmware will set privacy bit and add WPA OUI in VENDOR IE in beacon and probe response. The security type in softAP beacons confuse the supplicant in client side, and the user client will see [WPA-?] in supplicant scan result. So we set WPA_AUTH_DISABLED in softAP mode with OPEN security. Acked-by: Arend van SprielSigned-off-by: Wright Feng --- v2: fix typo in commit message --- drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-)
Re: [PATCH v2 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode
Wright Fengwrites: > brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/OPEN security mode > > When setting wpa_auth to WPA_AUTH_NONE(1) in AP mode with WEP security, > firmware will set privacy bit and add WPA OUI in VENDOR IE in beacon and > probe response. The security type in softAP beacons confuse the > supplicant in client side, and the user client will see [WPA-?] in > supplicant scan result. So we set WPA_AUTH_DISABLED in softAP mode with > OPEN security. The title is now duplicated, it's now in Subject and in the body, but I can fix that. -- Kalle Valo