Problem adding initial station to wpa_supplicant.
Ben Greear
greearb
Fri Apr 3 15:44:49 PDT 2015
In one of my tests, I admin down all stations, but I always start one
wpa_supplicant per radio. So, I have these running:
root 3579 0.0 0.0 53920 1844 ? S<s 15:24 0:00 ./local/bin/wpa_supplicant -g /var/run/wpa_supplicant_if_wiphy0 -B -P
/home/lanforge/wifi/wpa_supplicant-wiphy0.pid -t -f /home/lanforge//wifi/wpa_supplicant_log_wiphy0.txt
root 3584 0.0 0.0 53920 1924 ? S<s 15:24 0:00 ./local/bin/wpa_supplicant -g /var/run/wpa_supplicant_if_wiphy1 -B -P
/home/lanforge/wifi/wpa_supplicant-wiphy1.pid -t -f /home/lanforge//wifi/wpa_supplicant_log_wiphy1.txt -dd
My normal operation, is to then do an interface add when stations are created and
admin-up.
./local/bin/wpa_cli -g /var/run/wpa_supplicant_if_wiphy0 interface_add sta900 /home/lanforge/wifi/wpa_supplicant-wiphy0-sta900.conf nl80211
The problem I have is that when I do an 'interface_add', the supplicant doesn't actually
do anything obvious like trying to associate, and in particular, it does not create a /var/run/wpa_supplicant
directory with the interface name in it. So, I cannot use the 'reconfigure' or other
wpa-cli commands that I would normally use to kick off the scan and association for a station.
Am I missing something simple, or do I just need to go write some code in wpa_supplicant?
Thanks,
Ben
--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the Hostap
mailing list