I have the same problem. I have use nfs to for my home and ldap to login. So I need networking before I login. If my laptop is wired it is no problem. But with wifi (wpa) and using networkmanager, I first have to login before wifi (wpa) can be enabled so I choose to configure wifi manual instead of roaming mode. After a reboot I can't login with my ldap/nfs account. Ldap is cached, but the home cannot be reached. So I do ctrl+alt+f1 and login to the console with a local account. With ipconfig i see that ath0 has a link local (169) address. With dhclient ath0 I don't get an proper IP address. I have to do a /etc/init.d/networking reload (or force-reload) to get an IP address for ath0. I log off and go to the x session (ctrl+alt+f7) and I can login with the ldap/nfs user.
As a workaround I put /etc/init.d/networking force-reload into /etc/rc.local but it isn't a need solution. Now I get an IP address from start, without switching to the console. -- wifi does not automatcially come on during boot up https://bugs.launchpad.net/bugs/229945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
