From: Kalle Valo <kvalo@codeaurora.org>
To: Wright Feng <wright.feng@cypress.com>
Cc: arend.vanspriel@broadcom.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com, linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com
Subject: Re: [PATCH 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/opensecurity mode
Date: Wed, 02 Aug 2017 12:30:42 +0300 [thread overview]
Message-ID: <87r2wu48ql.fsf@codeaurora.org> (raw)
In-Reply-To: <1501577287-28904-1-git-send-email-wright.feng@cypress.com> (Wright Feng's message of "Tue, 1 Aug 2017 16:48:05 +0800")
Wright Feng <wright.feng@cypress.com> writes:
> When setting wpa_auth to WPA_AUTH_NONE(1) in AP mode with WEP secuirty,
> firmware will set privacy bit and add WPA OUI in VENDOR IE in beacon and
> probe response.
typo: "secuirty"
> It confuses the supplicant in sation client by the security type from
> softAP beacon and we will see [WPA-?] in scan result.
"sation"? Also the sentence is a bit unclear.
> So we set WPA_AUTH_DISABLED in softAP mode with opensecurity.
Space missing between "open" and "security".
--
Kalle Valo
prev parent reply other threads:[~2017-08-02 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 8:48 [PATCH 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/opensecurity mode Wright Feng
2017-08-01 8:48 ` [PATCH 2/3] brcmfmac: Add support for CYW4373 SDIO/USB chipset Wright Feng
2017-08-01 12:43 ` Arend van Spriel
2017-08-01 15:10 ` Chi-Hsien Lin
2017-08-01 21:03 ` Arend van Spriel
2017-08-02 8:15 ` Kalle Valo
2017-08-01 8:48 ` [PATCH 3/3] brcmfmac: fix wrong num_different_channels when mchan feature enabled Wright Feng
2017-08-01 12:44 ` Arend van Spriel
2017-08-02 9:32 ` Kalle Valo
2017-08-02 10:17 ` Arend van Spriel
2017-08-02 13:40 ` Kalle Valo
2017-08-03 1:57 ` Wright Feng
2017-08-01 12:41 ` [PATCH 1/3] brcmfmac: set wpa_auth to WPA_AUTH_DISABLED in AP/opensecurity mode Arend van Spriel
2017-08-02 2:56 ` Wright Feng
2017-08-02 9:30 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2wu48ql.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.