Mark Brier wrote:
My suggestion would be to use NetworkManager if it is for a customer and they are going to be using gnome/kde. It makes connection to accesspoints a breeze and supports both WEP and WPA (if wpa_supplicant is also installed).
Right, I've done this and it does improve things (the client didn't collect the laptop Thursday, so with being out of the office yesterday I gained this morning to work on it as he wants it at midday today).
However, I still have essentially the same problem; if I use KNetworkManager to connect to the wlan, it sits and thinks for a long time, before eventually popping up the login box into which I (re-)enter the WEP key and this time it connects. The WEP key is stored so there is obviously some delay in making a connection, which NetworkManager takes as meaning the passphrase is wrong (annoyingly it doesn't then remember the key and I have to re-enter it).
If I could introduce a delay somewhere so that it worked, or a retry, that would be great. For the time being I'm going to have to just hope its a problem with my access point and let the customer try it themselves. I find the odds of that strategy working out for the best to be fairly minimal.
[Aside: Yesterday we took delivery of a Belkin F5D7050 which I know to be supported, except of-course I get the new 4000 model which has a new and unsupported - even by ndiswraper it seems - chipset. The sooner the Win* monopoly is removed and manufacturers consider other people the better we'll all be.]