roberts


Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: May 24 2006,19:20 |
 |
I have found some cards more fussy than others. Especially when configuring via script. For example by current setup requires a sleep 3 after modprobe ndiswrapper
Also, I do not use iwconfig wlan0 up After the modprobe doing a simple iwconfig shows me an unconfigured wlan0, so next I configure the card using iwconfig commands. Checking results with a simple iwconfig command.
After configuring the card, I use pump -i wlan0 to fetch an ip from the access point. I verify by using just an ifconfig wlan0
Also, for some cards/drivers I seem to need to set the essid via iwconfig command before I set the key. So two iwconfig commands. Some cards/drivers I can do all it all on one line like you have.
The main difference that I see is the pump -i wlan0
HTH
|