System doesn't detect unplugged network cable and doesn't set interface up properly with DHCP

[Jason Hellenthal]

On Fri, Jul 13, 2012 at 11:20:36AM -0700, Yuri wrote:
> On 07/13/2012 02:48, Peter Jeremy wrote:
> > This is a bug in dhclient - see PR bin/166656, which includes a fix.
> 
> I think this PR addresses part of the problem: dhclient doesn't exit when the link goes down.

To the best of my knowledge this is the correct way to handle this. Why
not reuse whats already been set if the link was to be brought back up
? ofcourse it should obviously change to the correct IP if another was
negotiated but that is rarely the case.

> But even if it exits, it leaves the IP address that it has set, which is wrong. This IP address survives through the next DHCP setup process and ends up being the second IP address.
> Should be very easy to on exit remove any IP address that was set during dhclient process lifetime.

I couldnt agree more. Interface tear down is definately needed here.


-- 

 - (2^(N-1))