I still get this bizarre behaviour, though with a slight variation. I get a connection OK, but about a minute or so later, the interface gets another lease from a dhclient that NM started, but nevertheless doesn't regard as a belonging to it (unrecognised PID). NM then *stops* the interface.
Really, this is just paranoid. Never mind the fact that NM's starting up multiple dhclient processes - why on earth should NM kill the connection dead when a new lease arrives/is refreshed? -- 0.7 Network-Manager requests DHCP configuration twice, gets confused and aborts the connection https://bugs.launchpad.net/bugs/255829 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
