wpa_cli commands FAIL
Thu Aug 9 04:21:50 PDT 2012
On Wed, Aug 08, 2012 at 08:07:02PM +0530, Dr. Ajay N. Khosla wrote:
> Yes, you may be right. The log say
> 1344448969.602705: Interworking: ANQP Query Request to 02:27:22:4e:6e:5c
> 1344448969.602740: GAS: Starting request for 02:27:22:4e:6e:5c dialog_token 0
> 1344448969.602763: GAS: Send action frame to 02:27:22:4e:6e:5c len=29 freq=2462
> 1344448969.602786: Off-channel: Send action frame: freq=2462 dst=02:27:22:4e:6e:5c src=00:1b:77:7f:44:f4 bssid=02:27:22:4e:6e:5c len=29
> 1344448969.602813: Off-channel: Schedule Action frame to be transmitted once the driver gets to the requested channel
> 1344448969.602832: Off-channel: Failed to request driver to remain on channel (2462 MHz) for Action Frame TX
Which driver are you using?
> I used same command when I am not associated with any AP. The error is same Off-channel. This time status show DISCONNECTED.
In that case, it sounds like the driver you are using does not support
off-channel operations and as such, does not support GAS/ANQP (which
would be needed for Interworking to work).
> My credential are given below. Do we require more
This does not include username/password (or
private_key/client_cert/ca_cert). Please note that only WPA2-Enterprise
connections are currently supported for automatic network selection.
> > > > anqp_get 02:27:22:4e:6e:5c 261
> > > 'ANQP_GET 02:27:22:4e:6e:5c 261' command timed out.
> > > > 'PING' command failed.
> > I would like to see wpa_supplicant debug log showing this.
> Actually I can not find any log for this failure. It restart or reinitialized without any reason.
> 1344449252.719621: RX ctrl_iface - hexdump_ascii(len=30):
> 41 4e 51 50 5f 47 45 54 20 30 32 3a 32 37 3a 32 ANQP_GET 02:27:2
> 32 3a 34 65 3a 36 65 3a 35 63 20 32 36 31 2:4e:6e:5c 261
> 1344449252.719779: ANQP: Query Request to 02:27:22:4e:6e:5c for 1 id(s)
> 1344449252.923752: wpa_supplicant v2.0-devel
> 1344449252.923949: random: Trying to read entropy from /dev/random
> 1344449252.934449: Providing DBus service 'fi.epitest.hostap.WPASupplicant'.
> 1344449252.934579: Successfully initialized wpa_supplicant
> 1344449252.934619: Daemonize..
Interesting.. How did you start wpa_supplicant in the first place? The
second start here is setting the process to background, but it would be
easier to debug crashes by manually starting wpa_supplicant on the
foreground and using gdb or valgrind (etc.) to take a look at where the
> > > > interworking_select
> > > OK
> > > <3>Starting ANQP fetch for 02:27:22:4e:6e:5c
> > > > 'PING' command failed.
> Same, after ANQP: Query Request it restart.
> 1344450940.533481: wlan0: Starting ANQP fetch for 02:27:22:4e:6e:5c
> 1344450940.533498: CTRL_IFACE monitor send - hexdump(len=22): 2f 74 6d 70 2f 77 70 61 5f 63 74 72 6c 5f 31 39 30 31 38 2d 32 00
> 1344450940.533550: Interworking: ANQP Query Request to 02:27:22:4e:6e:5c
> 1344450940.715507: wpa_supplicant v2.0-devel
I have not been able to reproduce this. It would be useful if you could
either collect a coredump and a backtrace with gdb or run the
wpa_supplicant process under valgrind to get some more details of what
exactly happens here.
> My hostapd configuration is
Please note the comment about WPA2-Enterprise, i.e., the current
wpa_supplicant implementation won't be able to connect to this open
network based on Interworking network selection.
> When it is connected to some different SSID and I give interworking_select command. Again wpa_supplicant crash and restart
It is again in the same place, so it looks like something is going quite
wrong with ANQP operations.
> > > > list_cred
> > > cred id / realm / username / domain / imsi
> > > <3>CTRL-EVENT-SCAN-RESULTS
> I set cred
> Is it not enough to show in list_cred or not?
It should show and does show in my tests:
cred id / realm / username / domain / imsi
> I set only network without any specific SSID block as
> I have not set any SSID as I want to connect to AP with consortium ID 2233445566 irrespective of SSID.
This key_mgmt=NONE case is not currently supported with Interworking
network selection. That network block on its own will ask wpa_supplicant
to connect to any open network (regardless of roaming consortium, etc.
Then networks selection mechanism will automatically generate a
temporary network block when a network matching a credential is found,
so there is no need to add the network blocks manually. However, the
key_mgmt parameter is currently hardcoded to WPA-EAP (i.e.,
WPA2-Enterprise) since that is mode mandated for Wi-Fi Passpoint. It
would be possible to extend this to open network for other use cases
(i.e., when the AP does not advertise that it is a Hotspot 2.0 AP) if
that is something that people want to deploy. Though, I would recommend
use of WPA2-Enterprise wherever possible for hotspot deployments that
aim to use Interworking.
Jouni Malinen PGP id EFC895FA
More information about the Hostap