From: Jouni Malinen <j@w1.fi>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
brcm80211 development <brcm80211-dev-list@broadcom.com>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>
Subject: Re: P2P_DEVICE support in Android KitKat
Date: Wed, 10 Sep 2014 14:10:40 +0300 [thread overview]
Message-ID: <20140910111040.GA5269@w1.fi> (raw)
In-Reply-To: <540FFDFD.2070302@broadcom.com>
On Wed, Sep 10, 2014 at 09:30:05AM +0200, Arend van Spriel wrote:
> I am running some tests on a haswell target with Android KitKat
> (3.10.20 kernel). In this configuration our brcmfmac driver is used
> with driver param 'p2p_device=1'. So we end up with wlan0 and
> p2p-dev-wlan0 interfaces (can blame myself for that). The
> configuration has a network configured, but I did not expect
> wpa_supplicant to start association using the p2p device interface.
> The wlan0 interface is already connected to the AP. How can I fix
> this to assure p2p-dev-wlan0 is only used for p2p management
> scenarios.
Hmm.. Can you please show the wpa_supplicant command line that is used
here and describe how that network block gets configured for the
p2p-dev-wlan0 "interface"? I would have expected that there would never
be a configuration with an enabled network block being passed for the
P2P management interface.. Internally, wpa_supplicant should not add
such for P2P groups, but I don't think there is any filtering on
configuration if something is externally trying to make wpa_supplicant
use that management interface for a station mode connection.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2014-09-10 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 7:30 P2P_DEVICE support in Android KitKat Arend van Spriel
2014-09-10 11:10 ` Jouni Malinen [this message]
2014-09-10 14:00 ` Peer, Ilan
2014-09-10 14:22 ` Arend van Spriel
2014-09-10 14:15 ` Arend van Spriel
2014-09-11 9:57 ` Arend van Spriel
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=20140910111040.GA5269@w1.fi \
--to=j@w1.fi \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
/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.