From: Tim Fletcher (groupstudy@fletchmail.net)
Date: Tue Jan 27 2004 - 15:36:32 GMT-3
William,
What you are seeing is perfectly normal. Here's an excerpt from RFC 2131:
DHCP defines a new 'client identifier' option that is used to pass an
explicit client identifier to a DHCP server. This change eliminates
the overloading of the 'chaddr' field in BOOTP messages, where
'chaddr' is used both as a hardware address for transmission of BOOTP
reply messages and as a client identifier. The 'client identifier'
is an opaque key, not to be interpreted by the server; for example,
the 'client identifier' may contain a hardware address, identical to
the contents of the 'chaddr' field, or it may contain another type of
identifier, such as a DNS name.
I don't know how they come up with the particular client ID that they use,
but it doesn't really matter as long as it's unique.
-Tim Fletcher
At 01:48 AM 1/28/2004 +0800, William Chen wrote:
>Dear all,
>
> I try to configure and test the manual binding of DHCP. I am running the
>DHCP sever in R5 (a 2500 router) and I simulate a client with another 2500
>router. After I shutdown and no shutdown the client, the following message
>is display in the DHCP server. It seems the debug message is so strange that
>the client hardware address is wired. Any idea?
>
>R5#
>01:12:56: DHCPD: DHCPDISCOVER received from client
>0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30 on interface
>Ethernet0.
>01:12:56: DHCPD: there is no address pool for 192.168.0.100.
>01:12:59: DHCPD: DHCPDISCOVER received from client
>0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30 on interface
>Ethernet0.
>01:12:59: DHCPD: there is no address pool for 192.168.0.100.
>01:13:02: DHCPD: DHCPDISCOVER received from client
>0063.6973.636f.2d30.3030.302e.3063.3865.2e64.6564.342d.4574.30 on interface
>Ethernet0.
>...
>01:15:20: DHCPD: there is no address pool for 192.168.0.100.
>01:15:21: DHCPD: DHCPDISCOVER received from client 0100.c002.b682.67 on
>interface Ethernet0.
>01:15:21: DHCPD: there is no address pool for 192.168.0.100.
>01:15:22: DHCPD: BOOTREQUEST received from BOOTP client 00c0.02b6.8267 on
>interface Ethernet0.
>
>Best Regards,
>William Chen
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:51 GMT-3