This now happens to me constantly: after a resume, the network manager applet lists available networks, but does not try to connect to any of them automatically. Gconf shows those networks under /system/networking/wireless/networks, so I assume network manager is supposed to know about them.
It used to work earlier, but then I edited my /etc/network/interfaces and removed two lines: auto eth1 iface eth1 inet dhcp Network manager's readme says that it handles network interfaces only when they are not mentioned, or when they are configured with exactly these settings (auto and dhcp). It does not say anything about treating network interfaces differently depending on the presence of these two settings. I removed auto and inet eth1 dhcp lines from my /etc/network/interfaces because I thought they were interfering with network manager: * sometimes out of the blue my IP address would be reset to 0.0.0.0, while network manager would continue to thing that it is connected * sometimes I'd be online, but network manager would think I am not connected * sometimes I noticed that both dhclient and dhclient3 were running These symptoms are consistent with the theory that my networking was handled both by the standard infrastructure (that ran dhclient3) and network manager (that ran dhclient). Two DHCP clients on one network interface usually do not work that well. -- auto connect to network stopped working https://launchpad.net/bugs/44251 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
