Question:
- It makes my wireless card connect to first thing it sees and not the
SSID I specifically told it to connect with using YaST / NetApplet.
- I also want to know how to have wpa_supplicant automatically run at boot
because my SSID uses WPA2.
Answer:
I thought this idea might work, but it also doesn't.
(There are bunch of different things in Suse that are used to config
wireless. Who knows which one is the one you are supposed to use?)
Setup in Control Center --> Internet and Network ---> Wireless Network
+ All four "config" tabs to point to the SSID I want it to use.
+ Encryption turned off because that configureator only allows for WEP, not
+ In the "Execute Script on Connect", got an idea that this would work -->
+ Pointed this to a permission-executable file I made called:
+ /usr/local/sbin/WPAd
+ which contains one line:
wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
In YaST2 Config Network Settings (Click on the Netapplet thingy and select
Config)
+ For the wireless card, the intended SSID is entered
+ WPA is selected, along with correct passphrase
+ Everything else is right
The main thing seems to be with wpa_supplicant. Its like its not "loading
at the right time" or something. If I manually run it, it works, but when
I tried to make it run at startup (by doing that "also run this script") it
ran but didn't work. I'm sensing that it needed to run before the network
stuff starts coming to life. I have no idea on the "right way" to make
wpa_supplicant load at startup. I've googled, read man pages, read docs,
deja searched, posted on Suse's web forum, etc, etc, but everything just
goes in circles.
