Bob Proulx wrote: > I recommend that you work through the wicd problems.
Yes. > But is this laptop ever mobile? Do you take it off and connect to > other networks? Or does it *always* stay at home and *always* connect > up to your current access point? If so then you can set up a static > configuration for it using the ifupdown command line way. That will > cause wicd/NM to avoid it. > > allow-hotplug eth1 > iface eth1 inet dhcp > wireless-essid NETWORK_NAME Oh, I forgot to say that after doing this then it should connect automatically at a reboot. But with entries in /e/n/i you can then control the interface using the ifupdown commands. # ifup eth1 # ifdown eth1 Where if you do you will see something like this: root@mania:~# ifup wlan0 Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/64:5a:04:04:6c:45 Sending on LPF/wlan0/64:5a:04:04:6c:45 Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPOFFER from 192.168.91.1 DHCPACK from 192.168.91.1 bound to 192.168.91.100 -- renewal in 261 seconds. But for any mobile laptop using wicd is much preferred and easier for interactive use. Bob
signature.asc
Description: Digital signature
