On Mon, May 3, 2010 at 10:08, Zoran Kolic <zko...@sbb.rs> wrote:
> > | When I try to connect, wicd says that it is 'Putting interface up...', > 'Validating authentication...', 'Obtaining IP address...' then it times out > and says 'Connection failed: Unable to Get IP Address.' > > > > I have no clue what causes the problem, but I have found a clumsy > > workaround by trial and error: when I reset the router (Linksys > > WRT54GL) either to WPA from WPA2, or back the other way, wic manages > > to connect the next try. It doesn't seem to matter whether wic is > > looking for a password or a pre-shared key, so long as the the > > protocol is TKIP. Next time, I have to reset the router back the > > other way. No further change required -- until the next time, when the > > router needs to be reset _again_!. > > I have the same router. The very first thing was to > set it to "g only". Changing the channel may help > further. So, I would try that out, giving wpa2 a chan- > ce and using wpa_supplicant. Would be fine to know some > details about the hardware. Wifi chip at least. (I hope > I did not oversee it.) > Best regards > > Zoran > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/20100503043834.ga...@faust.net > > Also do not mix wicd, network-manager, /etc/init.d/networking etc. together, use only one of these. I once had a difficulty to connect because I was using both /etc/init.d/networking and network-manager together, one was stepping on another.