On Thu, 10 Sep 1998, Daniel Manrique wrote:
>
>
> I'm using diald on a little server to provide access to a bunch of
> Win9x boxen on a LAN. Diald by itself works awesomely. The problem is that
> the box also needs to run dhcpd, so that the winboxen can get their
> configuration with as little hassle as possible.
>
> 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.
The DHCP HOWTO says that in order to serve win95 boxes (and in some other
situations as well), you need to have a network route of 255.255.255.255
on the ethernet port you are trying to serve. Aparently, win95 boxes use
this address when they are trying to get an IP address.
> I'm sure someone else has had this problem and can help me, I've been at
> this all day and can't get both things to work together (they work great
> without each other, though).
>
>
> Thanks in advance :9
>
> - Roadmaster
>
> ----------------
> *
> Save a tree- use E-Mail! [EMAIL PROTECTED]
> *
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-----
Jim Kusznir ([EMAIL PROTECTED])
RidgeNET Tech Support
371-3501
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
