Since yesterday's updates, the behaviour has changed a little - I still have no network connection on boot (and the essid is not set). But now, when I run
$ sudo /etc/init.d/networking restart it does set the essid and start the network properly. So only one command to run each time I start my computer ... While this is an inconvenience for me (as I know the command line well) it could be a show stopper for others - so I think the priority should be increased. I am confident it is not my DHCP server - it worked fine for me while I was using hoary, warty, breezy, dapper and edgy ... As soon as iwconfig reports that wlan0 has the essid set, dhclient works fine. I did notice this section in /var/log/messages about 2 minutes after the boot - this may have been when I was running /etc/init.d/networking restart Mar 18 15:04:53 whisper kernel: [ 150.220452] ADDRCONF(NETDEV_UP): eth0: link is not ready Mar 18 15:04:55 whisper kernel: [ 151.728665] ADDRCONF(NETDEV_UP): wlan0: link is not ready Mar 18 15:04:57 whisper kernel: [ 154.296761] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 18 15:04:58 whisper kernel: [ 155.160302] wlan0: duplicate address detected! In case it matters, lscpi reports my wireless card as Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface Subsystem: Netgear Unknown device 4c00 -- Changing ESSID requires reboot or, or manual iwconfig for changes to take effect https://launchpad.net/bugs/80499 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
