Nate Bargmann wrote:
Admittedly, I didn't spend much time trying to sort things out, but
once udev 0.72+ was installed, waproamd stopped working so I rolled
udev back to 0.70 and have it on hold....
...I'm afraid that since (IIRC) waproamd is now
considered deprecated that it may not work with udev.
With waproamd, I recall that it would see an access point and then look for a script or config file in /etc/waproamd/scripts (or something similar) which matched either the ESSID or the MAC address of the AP. I found this a little awkward, since it wasn't completely clear what filenames waproamd was looking for. So, I had to edit the script to echo to the console the names of all of the script names it was checking for. *Then*, I'd have to go make one of those files.
With wpasupplicant, you put all of your settings (including order of preference) in /etc/wpasupplicant.conf. If all you're using right now is WEP, then it's as simple putting entries in like:
Also, don't forget to enable it and set your interface to use in /etc/default/wpasupplicant.# If my home AP is available, try that first (priority 9) network={ ssid="myhome" wep_key0="abcde" wep_tx_keyidx=0 priority=9 }# connect to my neighbor if my home AP is unavailable (priority 2) network={ ssid="myneighbor1" priority=2 }
Lastly, if it doesn't seem to be working, you can use "wpa_cli" as an interactive tool to diagnose what's going on. In fact, just *running* wpa_cli
sometimes gets things "unstuck". - Joe