Thread: [Ndiswrapper-general] Centrino 2200BG, losing track of its parameters
Status: Beta
Brought to you by:
pgiri
From: Matthew B. <mat...@gm...> - 2004-08-21 03:54:43
|
Hi, Just to update my previous post on problems setting ESSID on my 2200BG in a Thinkpad 40. The problem has turned out to be very bizarre - at least to me. It seems that the information being returned by iwconfig changes randomly without any input from me. Only when the information returned by iwconfig is correct will the card connect. For example, I load the module without problems. I set iwconfig like this: iwconfig wlan0 mode Managed key open <my_key> essid <my_ap> I run iwconfig with no parameters; the key is set, but the essid is not. I run iwconfig with no parameters again, immediately, and the essid is set but the key is not. I run the whole command again (... essid <my_ap>). Then iwconfig with no parameters; the key is set, the essid is not. I run iwconfig again with no parameters, and both key and the essid are set. At which point, for the first time, I can connect to my WEP encrypted network. I have also found that I have to run iwconfig several times in order to be able to set the essid (and connect) on unencrypted networks. This was easier than for my WEP network; maybe because the card does not have to keep the essid _and_ the key in memory in order to connect. Sad to say, the linuxant driver works very well. So, it looks as though the ndiswrapper driver has somehow got a slightly vague grip on the hardware settings. Is that possible? Thanks a lot for any help, Matthew |
From: Andrew R. <ar...@we...> - 2004-08-21 04:11:14
|
On Sat, 2004-08-21 at 13:54, Matthew Brett wrote: > The problem has turned out to be very bizarre - at least to me. It > seems that the information being returned by iwconfig changes randomly > without any input from me. Only when the information returned by > iwconfig is correct will the card connect. > > For example, I load the module without problems. I set iwconfig like this: > > iwconfig wlan0 mode Managed key open <my_key> essid <my_ap> > > I run iwconfig with no parameters; the key is set, but the essid is not. > > I run iwconfig with no parameters again, immediately, and the essid is > set but the key is not. > > I run the whole command again (... essid <my_ap>). Then iwconfig > with no parameters; the key is set, the essid is not. > > I run iwconfig again with no parameters, and both key and the essid > are set. At which point, for the first time, I can connect to my WEP > encrypted network. Do you see the same behaviour when you append "commit" to your iwconfig set command? eg. iwconfig wlan0 mode Managed key open <my_key> essid <my_ap> commit Cheers Andrew |
From: Matthew B. <mat...@gm...> - 2004-08-21 04:25:36
|
Hi, > Do you see the same behaviour when you append "commit" to your iwconfig > set command? eg. > > iwconfig wlan0 mode Managed key open <my_key> essid <my_ap> commit Thanks for the quick reply; yes, I'm afraid it does look the same if I append "commit". Best, Matthew |
From: Giridhar P. <gi...@lm...> - 2004-08-21 17:28:09
|
Apparently needs the mode to be set before other things. But wireless-tools set essid first and mode later if you specify both. So, to get WEP to work reliably, set the mode alone first: iwconfig wlan0 mode Managed and then other settings: iwconfig wlan0 essid <ssid> key <key> etc. -- Giri |
From: Matthew B. <mat...@gm...> - 2004-08-21 21:35:48
|
Hi, > Apparently needs the mode to be set before other things. But > wireless-tools set essid first and mode later if you specify both. So, > to get WEP to work reliably, set the mode alone first: > > iwconfig wlan0 mode Managed > > and then other settings: > > iwconfig wlan0 essid <ssid> key <key> For me, it makes no difference if I set the mode on its own first, and then the other settings; it still takes a random number of repeats (1-4) of the following iwconfig commands before the settings will take, and I can connect. iwconfig wlan0 mode Managed ; iwconfig wlan0 key open <my_key> ; iwconfig wlan0 essid <my_essid> ; iwconfig So, the line below has exactly the same effect: iwconfig wlan0 mode Managed key open <my_key> essid <my_essid> ; iwconfig I do need to set the essid last though, as above, otherwise the essid is never set; for example the last iwconfig line in your mail will not work for me. Interestingly, if the essid and key are set after (say) 2 iwconfig lines as above, then they may spontaneously unset (according to output of iwconfig) - without any further input from me. After 4 repeats of the iwconfig setting line, the essid and the key seem to be stable. Best, Matthew |