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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
