I finally got some time to sit down with Wireshark and compare the bootp
packets between the D-Link
and the Linux box... The first thing that jumped out as different was
the source address on the DHCP Offer
packets.
D-Link: 192.168.1.1
Linux: 127.0.0.1
So, something wasn't right. I began mucking around with a bunch of
different settings based on the
dhcpd.conf(5) pages. None seemed to work...
After looking a little closer at the server-identifier tag, it was
misconfigured... I was using the name instead of
IP address. The man pages are a bit confusing though... It states:
Theserver-identifier statement
*server-identifier* hostname*;*
The server-identifier statement can be used to define the value that
is sent in the DHCP Server Identifier option for a given scope. The
value specified*must* be an IP address for the DHCP server, and must
be reachable by all clients served by a particular scope.
So, it needs to be set to the --hostname-- but they really mean --IP--
Why they didn't just specify it as:
Theserver-identifier statement
*server-identifier* *address;*
I guess we will never know... Right below that is the server-name tag,
which really is the name. So, if anyone
else runs into this problem, the answer is RTFM --Carefully-- before
adding things to the config.
Thanks to everyone for their help!
- Todd
On 1/30/2010 11:03 PM, Brian St. Pierre wrote:
On Fri, January 29, 2010 7:10 pm, Todd Littlefield wrote:
If I disable the daemon on the server and use the one on the router,
the Windows boxes are happy... But that makes me unhappy. I'm at my wits
end trying to get it figured out.
Can you get a wireshark capture of (a) the broken request and (b) the
working request?
Then compare the two and change whatever is needed in your config (one
thing at a time) to make (a) look more like (b).
--
Brian St. Pierre
_______________________________________________
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
