On Tue, 02 Feb 1999, you wrote:
>I am having problems getting DHCPd to work on eth0 (giving out IP's to
>windows machines) and at the same time getting DHCPcd to work on eth1
>(getting an IP from roadrunner). DHCPcd seems to have a problem with the
>route configuration that windows requires in order to obtain an ip from a
>DHCP server:
>
>/sbin/route add -host 255.255.255.255 eth0
>
>When that route is added, DHCPcd freaks out, and doesn't get any offers from
>roadrunner's DHCP servers. If that route is left out, DHCPcd is fine and
>dandy, but of course my windows machines don't get the IP address from
>DHCPd. Kind of a catch 22, idn't it? Does anyone have any suggestions on
>how to work around this? Is anyone else using DHCPcd and DHCPd
>simutaneously? If so, I would greatly appreciate any help in getting this
>set up.
Err... you have two interfaces, no? One for the rr, and one for your internal
lan? Then one is ethA (running dhcpCd) and the other is ethB (running dhcpd).
Also, dhcpd doesn't care about routing entries, so if you're not able to issue
IPs without that, maybe you have a bigger problem?
I'm sort of out of my depth here, since I don't run dhcpd, but you might want
to try upgrading to the 1.x versions of dhcpcd, since they use AF_PACKET
instead of AF_INET and so don't use routing entries...
Taral
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
