p2p bug/feature when using intel 7260 and 5GHz

Janusz Dziedzic janusz.dziedzic at tieto.com
Thu May 14 01:17:21 EDT 2015


Hello,

A) Connection to autonomous GO works fine:
t1-ath9k at wlan0 send: P2P_GROUP_ADD freq=5180
t1-ath9k at wlan0 recv: OK

t1-ath9k at wlan0 wait_msg: P2P-GROUP-STARTED (30)
t1-ath9k at wlan0 get: <3>P2P-GROUP-STARTED p2p-wlan0-0 GO
ssid="DIRECT-SG" freq=5180 passphrase="x7M4ScIq"
go_dev_addr=2c:d0:5a:d3:f1:e9

t2-intel-7260 at p2p-dev-wlan3 send: P2P_CONNECT 2c:d0:5a:d3:f1:e9 12345670 join
2-intel-7260 at p2p-dev-wlan3 get: <3>P2P-GROUP-STARTED p2p-wlan3-0
client ssid="DIRECT-SG" freq=5180

B) But when GO negotiation and intel with go_intent=1
t1-ath9k at wlan0 send: P2P_CONNECT 0c:8b:fd:1e:58:9e pbc freq=5180  go_intent=15
t2-intel-7260 at p2p-dev-wlan3 wait_msg: P2P-GO-NEG-REQUEST 2c:d0:5a:d3:f1:e9 (60)
t2-intel-7260 at p2p-dev-wlan3 send: P2P_CONNECT 2c:d0:5a:d3:f1:e9 pbc go_intent=1
t2-intel-7260 at p2p-dev-wlan3 get: <3>P2P-GO-NEG-FAILURE status=7

GO (ath9k) reject GO-NEG and in logs I see:

P2P: Own reg_classes 1 peer reg_classes 1 intersection reg_classes 0
P2P: No common channels found

While intel will be p2p client (no beaconnig required), why we reject
this? Are we to strict in this case?

BR
Janusz


More information about the HostAP mailing list