wpa_supplicant cannot authenticate connection on prism2 radios if interface names do not match
Tue Mar 17 09:59:15 PDT 2015
>> Well, the information on the pairing is actually available in the sysfs
>> filing system. Thus,
>> contains two directories, namely the two network interfaces the device
> Can you get a full 'ls -al' dump of /sys/class/net/wlan0/device/ ?
Sorry, this is /sys/class/net/wlan0/device/net (forgot the net). But
here we go, it's really quite simple:
thor at pike:~> ls -la /sys/class/net/wlan0/device/net
drwxr-xr-x 4 root root 0 Mar 17 17:55 .
drwxr-xr-x 4 root root 0 Mar 17 17:55 ..
drwxr-xr-x 6 root root 0 Mar 17 17:51 wifi0
drwxr-xr-x 6 root root 0 Mar 17 17:55 wlan0
As you see, currently, the system is setup fine. (wifi0 paired with
wlan0). There is nothing else in this directory.
> wpa_driver_wext_finish_drv_init() should probably do some sysfs parkour
> to find the wifi interface instead of relying on the device name.
Yes, I agree.
More information about the Hostap