Kacheong Poon wrote:
Randy Fishel wrote:
So this isn't specifically related to the proposed DHCP changes, and is
probably more related to NWAM in general, but today Solaris suspends
and resumes on Sparc, and in the very near future, it will suspend and
resume on x86 platforms. What will be the interaction here on either
suspend or resume, and how should it best be addressed (after all, the
machine could resume on a completely different network, or without one
all together)?
We have not discussed suspend/resume yet. How does
the driver handle this? For example, suppose the
cable is plugged in at the suspend time and it is not
at resume time, will the driver send up the DL_NOTE_*
message up to IP?
I guess the issue related to DHCP is that the system
should probably try to get back the same address if
possible. We can treat the resume as a system start
up. NWAM can ask dhcpagent to drop the interface. If
the underlying link for the interface is available, it
can them ask dhcpagent do a discovery with the old
address (this is not supported in the current proposal,
the DHCP_DISCOVER request needs to be extended). And
depending on the address offered, NWAM can decide what
to do next.
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 see why NWAM should treat a suspend/resume cycle as approximately
a reboot, which seems to be what you're suggesting, that tends to defeat
the purpose of the feature.
Dave
_______________________________________________
networking-discuss mailing list
[email protected]
