Peter Memishian wrote:
> Why do we need to change dhcpagent? It already caches the previous
> lease by default and will attempt to confirm it first on a resume.
I don't believe it currently handles the case where the network changes
out from under it.
Unless I'm missing something, it should be falling back either to INIT
state and starting from scratch, which will of course work on a new
network, or going to INIT-REBOOT if there's a /etc/dhcp/<if>.dhc file,
and sending that request as a broadcast, in which case servers should
NAK the client if they know it's on the wrong network. The one case
where I think this breaks in the current code is if the client has an
infinite lease.
Dave
_______________________________________________
networking-discuss mailing list
[email protected]
