[pkg-wpa-devel] Bug#488309: here is wpa_supplicant.conf
prosolutions at gmx.net
prosolutions at gmx.net
Mon Jun 30 20:42:16 UTC 2008
Here is the wpa_supplicant.conf I am using. I can confirm again that
wpa_supplicant and ifup/down are basically totally broken with respect
to bringing up/down the wireless interface. At boot, based on the
/etc/network/interfaces above and this wpa_supplicant.conf, it will do
the correct thing and roam and associate with the best AP in range.
However, if the interface is taken up or down either with ifup/ifdown or
ifconfig, even when it is reconfigured, it fails to associate.
At this point, other than bootup, and for networks not requiring wpa authentication, I find that it is much easier to manage the wireless interface with my own custom scriptsand totally bypass the whole ifup/down system. However, for networks requiring authentication, unfortunately there is not clear information regarding how to use wpa_cli to manually associate with a given AP using specific parameters. I would be grateful at least for clear examples on how to manually configure wireless interfaces using only iwconfig and wpa_cli, and whether or not when using wpa_cli it is possible to have it use the info in /etc/wpa_supplicant/wpa_supplicant.conf or whether is is necessary to specify it all manually.
/etc/wpa_supplicant/wpa_supplicant.conf (please note I changed the ssid, id_str, and psk entries for reasons of privacy)
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
network={
ssid="foobar1"
key_mgmt=NONE
# wep_key0=6162636465
# wep_tx_keyidx=0
id_str="fb1"
}
network={
ssid="foobar2"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP
group=CCMP
psk="secretpass"
id_str="fb2"
}
network={
ssid="foobar3"
key_mgmt=WPA-PSK
proto=WPA2
pairwise=TKIP
group=TKIP
psk="secretpwd"
id_str="fb3"
}
network={
key_mgmt=NONE
}
More information about the Pkg-wpa-devel
mailing list