P2P_FIND command failed from wpa_cli

Fri Jan 25 21:40:38 PST 2013

Hello Dan,Arend and Jouni,

Thank you very much for taking time for looking into the issue.

It seems getting P2P work on my Think-pad little difficult.
We were facing the same issue on Raspberry PI board. Hence I started P2P
debugging on the ubuntu X86 machine ( think-pad). However when we check "iw
list" result on raspberry pi the P2P clinent and P2P Go Rx/Tx frame are
supported but in the interface supported list it was not mentioned.

I am attaching user story and necessary logs for Raspberry PI to get help
in resolving this issue.
Request all you to check the below details and suggest me, what could be
the root cause.Your help is greatly appreciated in resolving this issue.
----------------------------------------------------------------------------------------------------------------------------

User Story :
----------------

We want to try out WI-FI Display functionality. Just to try out things we
have a Raspberry PI as a sink with a USB wifi dongle !

We have Nexus S which has wifi-direct available and Nexus 7 ( no inbuilt
wifi-direct,  but using third party app called "wifi-direct" from the
playstore) as source /server.

We have to try this out with and without device being connected to an AP.

In the first instance we just want to connect and transfer some data
between these two devices. Once that is achieved we want to move further to
wifi-display. We have compiled the WPA_SUPPLICANT with P2P support on
raspberry PI ( ARM - Broadcom).

Logs and other details:
------------------------------

When we run p2p_find from wpa_cli it returns instantaneous FAIL message.

WPA_SUPPLICANT started with following command line arguments

wpa_supplicant -f /var/log/wpa.log -Dnl80211 -c
/etc/wpa_supplicant/wpa_supplicant.conf -i wlan0 -dt

WPA_CONFIG

root at raspberrypi:/home/pi# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

device_name=My P2P Device
device_type=1-0050F204-1

WPA_CLI - messages

>
> p2p_find 60
FAIL
> p2p_find 60
FAIL
> p2p_listen
FAIL

WPA_APPLICANT LOG

root at raspberrypi:/home/pi# tail -f /var/log/wpa.log
1359148764.076983: EAPOL: SUPP_PAE entering state AUTHENTICATING
1359148764.077035: EAPOL: SUPP_BE entering state SUCCESS
1359148764.077085: EAP: EAP entering state DISABLED
1359148764.077136: EAPOL: SUPP_PAE entering state AUTHENTICATED
1359148764.077185: EAPOL: Supplicant port status: Authorized
1359148764.077551: EAPOL: SUPP_BE entering state IDLE
1359148764.077647: EAPOL authentication completed successfully
1359148764.077807: RTM_NEWLINK: operstate=1 ifi_flags=0x11043
([UP][RUNNING][LOWER_UP])
1359148764.077889: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
1359148764.078023: nl80211: if_removed already cleared - ignore event
1359148794.078254: EAPOL: startWhen --> 0
1359148794.078480: EAPOL: disable timer tick
1359148951.474127: wlan0: BSS: Remove id 1 BSSID a0:21:b7:4a:3d:d8 SSID
'virginmedia1153663' due to wpa_bss_flush_by_age
1359148951.474445: wlan0: BSS: Remove id 2 BSSID 00:81:d8:3f:b6:62 SSID
'BTHub3-93S4' due to wpa_bss_flush_by_age
1359148951.474580: wlan0: BSS: Remove id 3 BSSID 12:81:d8:3f:b6:62 SSID
'BTWiFi-with-FON' due to wpa_bss_flush_by_age
1359148951.474699: wlan0: BSS: Remove id 4 BSSID 02:81:d8:3f:b6:62 SSID
'BTWiFi' due to wpa_bss_flush_by_age
1359148995.986465: CTRL_IFACE monitor attached - hexdump(len=21): 2f 74 6d
70 2f 77 70 61 5f 63 74 72 6c 5f 32 32 37 34 2d 32 00
1359149017.424316: RX ctrl_iface - hexdump_ascii(len=8):
50 32 50 5f 46 49 4e 44 P2P_FIND
1359149017.424693: wlan0: Control interface command 'P2P_FIND'
1359149017.424846: wlan0: P2P: Use 500 ms search delay due to concurrent
operation
1359149070.440343: RX ctrl_iface - hexdump_ascii(len=11):
50 32 50 5f 46 49 4e 44 20 36 30 P2P_FIND 60
1359149070.440730: wlan0: Control interface command 'P2P_FIND 60'
1359149070.440860: wlan0: P2P: Use 500 ms search delay due to concurrent
operation
1359149447.727077: RX ctrl_iface - hexdump_ascii(len=11):
50 32 50 5f 46 49 4e 44 20 36 30 P2P_FIND 60
1359149447.727464: wlan0: Control interface command 'P2P_FIND 60'
1359149447.727593: wlan0: P2P: Use 500 ms search delay due to concurrent
operation
1359149471.995872: RX ctrl_iface - hexdump_ascii(len=10):
50 32 50 5f 4c 49 53 54 45 4e P2P_LISTEN
1359149471.996255: wlan0: Control interface command 'P2P_LISTEN'

IW LIST

root at raspberrypi:/home/pi# iw list
Wiphy phy0
Band 1:
Capabilities: 0x172
HT20/HT40
Static SM Power Save
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 2 usec (0x04)
HT RX MCS rate indexes supported: 0-7, 32
TX unequal modulation not supported
HT TX Max spatial streams: 1
HT TX MCS rate indexes supported may differ
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (passive scanning, no IBSS)
* 2472 MHz [13] (20.0 dBm) (passive scanning, no IBSS)
* 2484 MHz [14] (20.0 dBm) (passive scanning, no IBSS)
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
Coverage class: 0 (up to 0m)
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* WDS
* monitor
* mesh point
software interface modes (can always be added):
* AP/VLAN
* monitor
interface combinations are not supported
Supported commands:
* new_interface
* set_interface
* new_key
* new_beacon
* new_station
* new_mpath
* set_mesh_params
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* remain_on_channel
* set_tx_bitrate_mask
* action
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0
0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0

lsmod Drivers  (rt2x000,cf80211,mac80211)

root at raspberrypi:/home/pi# lsmod
Module Size Used by
snd_bcm2835 12808 0
snd_pcm 74834 1 snd_bcm2835
snd_seq 52536 0
snd_timer 19698 2 snd_seq,snd_pcm
snd_seq_device 6300 1 snd_seq
snd 52489 5 snd_seq_device,snd_timer,snd_seq,snd_pcm,snd_bcm2835
snd_page_alloc 4951 1 snd_pcm
arc4 1187 2
rt2800usb 13009 0
rt2800lib 47242 1 rt2800usb
crc_ccitt 1465 1 rt2800lib
rt2x00usb 11075 1 rt2800usb
rt2x00lib 41057 3 rt2x00usb,rt2800lib,rt2800usb
mac80211 236178 3 rt2x00lib,rt2x00usb,rt2800lib
cfg80211 171957 2 mac80211,rt2x00lib

Hardware/Chipset - Ralink RT5370

Using white label USB WIFI dongle. Can't find the chipset datasheet but few
people suggesting on the internet that this chip supports P2P/wifi direct

root at raspberrypi:/home/pi# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless
Adapter

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=370569077102

Finally - rt800usb supports all the modes.

rt2800usb Ralink yes yes yes yes(5) yes A(1)/B/G/N USB
Driver Manufacturer cfg80211
AP
IBSS
mesh
monitor
PHY modes
Buses

-----------------------------------------------------------------------------

Thanks and Regards,
Nil

On Thu, Jan 24, 2013 at 12:15 AM, Dan Williams <dcbw at redhat.com> wrote:

> On Wed, 2013-01-23 at 13:37 +0100, Arend van Spriel wrote:
> > On 01/23/2013 05:12 AM, Nilkanth Ahirrao wrote:
> > > Additional information : I could connect to my wireless router using
> AP.
> > >
> > > Please let me know if you need further details.
> > >
> > > Thanks in advance.
> > >
> > > Regards,
> > > Nil
> >
> > Your thinkpad has wireless using iwlagn driver. Not sure if that
> > currently supports P2P. P2P involves two systems (hence the name) so
> > maybe you could explain what you are trying at a higher level, ie. what
> > devices are involved.
>
> iwlagn did get support for p2p (landed 2011-07-23, commit c6baf7fb,
> kernel v3.2), but it requires a firmware update to ucode API level 6 for
> the 1000 devices.  Without dmesg output of the driver loading to see
> what ucode revision he's got, it's hard to know whether the firmware
> supports it or not.  Plus, given he mentioned kernel 3.0, it's unlikely
> that his kernel has the right support unless it was backported by
> Canonical.
>
> Dan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20130126/487a45fa/attachment-0001.htm 