From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: brcm80211-dev-list.pdl@broadcom.com, "Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: brcmfmac: problem using WPS with wpa_supplicant on BCM43362
Date: Fri, 24 Feb 2017 11:26:56 +0100 [thread overview]
Message-ID: <1487932016.3812.10.camel@embedded.rocks> (raw)
In-Reply-To: <ce3bf3a5-2cd7-eb77-bb7d-57df8388e1ba@broadcom.com>
Hi Arend,
On Fri, 2017-02-24 at 10:58 +0100, Arend Van Spriel wrote:
> On 24-2-2017 10:43, Jörg Krause wrote:
> > Hi Arend,
> >
> > On Fri, 2017-02-24 at 09:16 +0100, Arend Van Spriel wrote:
> > >
> > > On 23-2-2017 21:21, Jörg Krause wrote:
> > > > Hi,
> > > >
> > > > I am using Linux Kernel v4.9.9 and wpa_supplicant 2.6. When
> > > > running
> > > > 'wpa_cli wps_pin any', the following messages are printed:
> > > >
> > > > """
> > > > > wps_pin any
> > > >
> > > > [ 4011.779108] brcmfmac: brcmf_vif_set_mgmt_ie: vndr ie set
> > > > error :
> > > > -30
> > > > [ 4011.786190] brcmfmac: brcmf_config_ap_mgmt_ie: Set Beacon IE
> > > > Failed
> > > > """
> > > >
> > > > .. and nothing happens. The data sheet for the BCM43362 states
> > > > that
> > > > the
> > > > module supports WPS.
> > >
> > > Hi Jörg,
> > >
> > > We have never tested WPS with brcmfmac. Most of it is in firmware
> > > so
> > > it
> > > might work. We had some fixes related to setting management IE,
> > > but
> > > it
> > > should be in 4.9. I did not check it (yet).
> >
> > As it turns out, WPS does not work if a network configuration in
> > wpa_supplicant has the flag `mode=2` (access point mode) set:
> >
> > """
> > ctrl_interface=/var/run/wpa_supplicant
> > update_config=1
> >
> > network={
> > ssid="AP"
> > key_mgmt=NONE
> > mode=2
> > id_str="ap"
> > }
> > """
> >
> > Setting mode=2 for a network and having ap_scan=1 (default) means
> > if no
> > APs matching to the currently enabled networks are found, a new
> > network
> > (IBSS or AP mode operation) may be initialized (if configured).
> >
> > So, WPS does not work if the interface is operating in AP mode. I
> > wonder, if this is a desired behavior? At least, wpa_supplicant
> > does
> > not complain, but prints "WPS-PBC-ACTIVE", but no messages are
> > following, until "WPS-TIMEOUT".
>
> So what do you expect exactly? Are you trying to connect with some
> other
> device to this AP interface?
Sorry, I got confused. The device operating in AP mode shall be
connected to some other AP as a station. Of course, WPS cannot be used
to do so as long as the interface is operation in AP mode, as the
device should be the WPS enrollee and not the registrar. My bad! Thanks
for pointing that out.
So, to use WPS for connecting the device to another AP I have to bring
the interface into an non-AP mode first.
So, I can confirm that using WPS works when the interface is
unconfigured. However, if the in the interface is in AP mode and WPS is
started the error messages pop up.
Jörg
next prev parent reply other threads:[~2017-02-24 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 20:21 brcmfmac: problem using WPS with wpa_supplicant on BCM43362 Jörg Krause
2017-02-24 8:16 ` Arend Van Spriel
2017-02-24 8:51 ` Jörg Krause
2017-02-24 9:43 ` Jörg Krause
2017-02-24 9:58 ` Arend Van Spriel
2017-02-24 10:26 ` Jörg Krause [this message]
2017-02-24 12:15 ` Arend Van Spriel
2017-02-27 17:02 ` Jörg Krause
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=1487932016.3812.10.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rafal@milecki.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).