Sam Bayne <[EMAIL PROTECTED]> writes:
> One thing that would be kind of interesting would be to monitor the
> dhcp conversation with tcpdump to see what the difference is between
> the linux and windows requests. Can you even run tcpdump BEFORE you
> initialize a NIC?
I'm glad you've brought this up. I have recently done exactly this
reasearch and there is a crucial difference between the MS dhcp client
and Red Hat's pump dhcp client. I've not checked the ISC dhcp client
yet.
The MS dhcp client *always* sends a dhcp-client-identifier option
constructed from the network type and the network hardware address.
For ethernet this is the byte value 1 followed by the MAC address of
the client.
The Red Hat pump dhcp client doesn't send the dhcp-client-identifier
unless you tell it to, and will send whatever you tell it to send.
This comes into play when you want to statically allocate addresses to
an unknown mix of Windows and Linux systems because the
dhcp-client-identifier is given preference over the raw MAC address
for identifying the client in the dhcpd server. I ended up having to
put 2 host blocks into the dhcpd.conf file for each dhcp client
because we were not sure whether they would be running Windows or
Linux.
I was unable to find any way to turn off the inclusino of the
dhcp-client-identifier in the Windows dhcp client.
--[Lance]
Contractor @ NIEHS, ITSS Contract, SysAdmin task
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
