Hi David,
Sorry for the late response. Hope the below can help :)
Regards,
Ilan.
> I tried again and masked the 5ghz channels (via "p2p_set", not "set" I
> guess?), however, still almost exactly the same log but on a 2.4ghz
> channel. I attached the full log to the email, I cut down all the
> "p2p-scan" log messages and inlined most parts of the log below.
>
> Another thing that I noticed is that I don't get any "P2P-XY" status
> messages to wpa_cli. I need to run "tail -f wpa.log | grep ^P2P-" in a
> separate session to actually see messages like P2P-DEVICE-FOUND,
> P2P-GO-NEG-SUCCESS, .. I only got "P2P-GROUP-" related messages
> directly forwarded to my wpa_cli. I really think this is all somehow
> related to the bunch of errors I get during p2p-dev-wlan0 setup, which
> you said you cannot reproduce.
>
>From the logs it looks like the wpa_supplicant tries to use the P2P Device interface for the GO instantiation (which is impossible since this is not a netdev but a P2P Device interface). Can you please try to invoke the wpa_supplicant with a global control interface and issue the P2P commands over the global control interface? Something like:
wpa_supplicant -i wlan0 -c <conf> -p allow_p2p_device=1 -t -s -d -T -B -g /tmp/wpa_global -G <group>
wpa_cli -g /tmp/wpa_global -G <group>
See the following commit from Jouni: 78f79fe5fc251e3ababa2970956cc9a84f29f209
P2P: Do not add ctrl interface for P2P_DEVICE (p2p-dev-*)
Adding a new wpa_supplicant control interface for the dedicated
P2P_DEVICE would be quite confusing for programs that manage P2P
operations. Remove this control interface and require the global control
interface to be used since it will provide consistent interface for both
the new dedicated P2P_DEVICE (non-netdev) and old style P2P management
through a netdev.
--
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
