On Thu, 10 Sep 1998, Daniel Manrique wrote:
> The problem is as follows: dhcpd says "network is unreachable" after
> issuing a DHCPOFFER. The windows station never gets the offer. I've traced
> the problem to the following: if I add a default route to either this same
> host or another (even nonexistent) Ip address on the segment I'm using,
> dhcpd works. If I have only the diald-provided default route (using sl0 as
> the routing device), dhcpd has the problem I described.
I believe this is mentioned somewhere in either dhcpd's docs or a
mini-howto or something, but I don't recall where I stumbled across it.
Linux's IP stack needs a little help in order to get an all-ones or
all-zeros IP address out the interface without being translated into the
appropriate subnet's broadcast address. Many DHCP clients accept this,
but MS's are picky and ignore anything not coming back on 255.255.255.255
exactly. The fix is to add an explicit route for 255.255.255.255 to the
ethernet interface you want to have dhcpd operate on - the corollary is
that you can only use one interface with dhcpd.
This restriction may be lifted with some recent kernel versions and/or a
patch, but the explicit 255.255.255.255 route has worked just fine for my
needs and I've never dug any further.
Luck!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
