p2p bug/feature when using intel 7260 and 5GHz

Peer, Ilan ilan.peer
Thu May 14 03:40:12 PDT 2015


This is opposite to the pervious case. In this case the ath device is initiating a p2p_connection forcing the use of frequency 5180 but with go_intent=1, while the Intel device is responding with go_intent=15. Thus, in this case the Intel device is going to be the P2P GO, but according to the regulatory channel information on the Intel device only 1..11 are allowed for use for beaconing, so this scenario will fail.

Did you try the opposite?



> -----Original Message-----
> From: Janusz Dziedzic [mailto:janusz.dziedzic at tieto.com]
> Sent: Thursday, May 14, 2015 13:22
> To: Peer, Ilan
> Cc: hostap at lists.shmoo.com
> Subject: Re: p2p bug/feature when using intel 7260 and 5GHz
> On 14 May 2015 at 08:01, Peer, Ilan <ilan.peer at intel.com> wrote:
> > Hi Janusz,
> >
> > Did you set p2p_add_cli_chan in the P2P Device configuration file? Without
> setting it, passive-scan channels will not be added in the P2P channels.
> >
> > It this still fails, can you please send me wpa_supplicant log file and also the
> output of iw list?
> >
> attached logs

More information about the Hostap mailing list