One clue is in RFC2131 [1] [...] A client SHOULD use DHCP to reacquire or verify its IP address and network parameters whenever the local network parameters may have changed; e.g., at system boot time or after a disconnection from the local network.... [...]
Still it says SHOULD, not MUST so it is really not so definite. Best Regards, -mat [1] http://tools.ietf.org/html/rfc2131#section-3.7 2009/7/9 Michael Balasko <[email protected]>: > > Does anyone know of any RFC's that pertain to how a host device should > behave regarding DHCP when the link come up? Newer windows machines and > some flavors of *nix behave like I think they should and that is they > will attempt to renew a DHCP lease on a link up. What we are finding is > that all our Xerox devices and some specialized/ruggedized gizmos do NOT > do this and it wrecks havoc with DHCP Snooping as you can imagine. I was > hoping to beat Xerox with an RFC stick. > > Thanks for any help on this, > > > Mike > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
