p2p bug/feature when using intel 7260 and 5GHz
Fri May 15 02:23:43 PDT 2015
On 14 May 2015 at 13:42, Peer, Ilan <ilan.peer at intel.com> wrote:
>> -----Original Message-----
>> From: Janusz Dziedzic [mailto:janusz.dziedzic at tieto.com]
>> Sent: Thursday, May 14, 2015 13:57
>> 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 12:40, Peer, Ilan <ilan.peer at intel.com> wrote:
>> > Hi,
>> > 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?
>> Yes :)
>> After setup go_intent correctly, works fine:
> Great :)
BTW, is there special reason you don't allow beaconing on 5180 for 7260?
I see there is RELAX_NO_IR option, but not sure this is usefull for 7260.
More information about the Hostap