On Tue, 26 Apr 2011 16:11:40 +0100 Anthony Campbell <a...@acampbell.org.uk> wrote:
> I have this stanza in /etc/network/interfaces: > > auto eth1 > iface eth1 inet dhcp > wireless-mode managed > wireless-essid 'My ESSID' > > At the end of booting, the system tries to connect to the wireless > point but after repeated attempts it reports that no DHCP offers are > found. I then do: > sudo ifdown eth1 && sudo ifup eth1 > > and the wirless link comes up at once. > > As a work-around, to avoid delay, I have commented out "auto eth1". > Once the boot is complete I have to do "ifup eth1", which fails as > usual but can be stopped with Ctrl-C, and then continue with "sudo > ifdown eth1 && sudo ifup eth1". > > In summary, I can get wirelss to work in this rather clunky way but I > think there should be a better solution. I googled a suggestion to > turn off wpasupplicant, but that doesn't help. Any ideas? > > Incidentally, this happens both in Squeeze and in Sid. > > Anthony > This may or may not be of help however: I haven't tried network manager, but I had heaps of trouble trying to connect to a wireless network, and attempted all manner of stanza's in /etc/network/interfaces without any success at all. I finally tried wicd though I would have like to do it without that front end. But wicd didn't connect every time either, couldn't find the networks available. Googled found I had to install python-urwid and then it found the available networks and connection every time. Some bug in the current version of wicd. That's the fix, and don't know why it wasn't installed with the wicd packages. Maybe it was included but I missed it. Now I have to try to remember, because I'm not on that lappy. But in the properties of wicd, I had to choose - preshared - network or connection or something and add the name and also the passphrase. Any other of the connections wouldn't connect with all the right ESSID and passphrase. But your mileage may vary in this. When I got this working I ticked the box: connect automatically. It does, it works at least. I'm using an up to date updated Debian testing - a wireless dongle with package firmware-ralink on an Acer laptop and what else? It works with both 32 kernel and 38 kernel, but the 38 kernel has always locked up at various unknown times, even before I got the wireless connection working. Firmware-atheros didn't work, and that's what the lappy has inbuilt. That's about it. Anyway, hope that helps. Charlie -- Registered Linux User:- 329524 *********************************************** To myself I am only a child playing on the beach, while vast oceans of truth lie undiscovered before me. -------SIR ISAAC NEWTON *********************************************** Debian GNU/Linux - just the best way to create magic ----------------------------------------------------- -- 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/20110427095055.367a5a2e@taowild
