Comment 5 for bug 255829

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?