On Tue, 17 Dec 2002, Petre Bandac wrote:
> [root@g38]:~# tail -f /var/log/all | grep dhcp
> Dec 16 20:16:34 g38 dhcpd: DHCPRELEASE of _IP_ from _MAC_ via eth2 (found)
> Dec 16 20:16:35 g38 dhcpd: DHCPDISCOVER from _MAC_ via eth2
> Dec 16 20:16:36 g38 dhcpd: DHCPOFFER on _IP_ to _MAC_ via eth2
> Dec 16 20:16:36 g38 dhcpd: DHCPREQUEST for _IP_ from _MAC_ via eth2
> Dec 16 20:16:36 g38 dhcpd: DHCPACK on _IP_ to _MAC_ via eth2
> Dec 16 20:36:50 g38 dhcpd: DHCPREQUEST for _IP_ from _MAC_ via eth2
> Dec 16 20:36:50 g38 dhcpd: DHCPACK on _IP_ to _MAC_ via eth2
> Dec 16 22:43:12 g38 dhcpd: DHCPINFORM from 192.168.0.111
>
> what is the order of a dhcp negotiation as viewed from syslog ?
It depends on the protocol
bootp - the base protocol
Request,Response
DHCP Adds options to bootp
Discover, Offer, Request, Ack
PXE Adds complexity to DHCP
Discover, Offer, Request, Ack, <Request, Inform...>
The reason for the four-phase DHCP is that offer isn't binding.
The client is allowed to choose or ignore the offer, and the server is
allowed to say "Nack, too late, I gave that address to someone else".
The 'inform' messages are used when the client already has an address
and wants to extend the lease or get additional info.
> in the rfc's I looked I did't find explicitely the order ....
See RFC2131 or the search for the PXE specs on developer.intel.com
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Scyld Beowulf cluster system
Annapolis MD 21403 410-990-9993
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
