On Wed May 4 2005 10:45 am, Sunny wrote:
On 5/4/05, Nick LeRoy
wrote: Hi Nick, did I understand correctly that you have one internal dhcpd on another machine to assign the internal IP to eth1?
Yes, My network looks something like this (ASCII art sucks, I know, but...) Pretty standard setup, actually. [cable-modem] | [External hub] ------------------[Internal switch] | |eth0 |eth1 | | | | [other-Linux] [firewall] [File-Server] | | | | | [pc1] [pc2] ...
Can it be a conflict between the dhcp servers than. Try setting eth1 with static IP.
That seems unlikely -- the networks are physically separate. But, it's certainly worth trying, if nothing else to verify that the dhcpcd daemons aren't somehow conflicting with each other.
Saying "cable-modem hub", does it mean that you have a hub between the modem and the machine? Is it possible something else connected to that hub (or it by itself) be running another dhcp server? I had such a problem, connecting a wireless router (D-Link) between my machine and the modem, and I got the same problems as you. I solved it bu turning off the dhcp server of the modem, and letting the router to assign addresses.
I'm quite certain that they're not, but I'll check again when I get home. The hub in question is just a dumb-old 8 port 10-base-T hub.
Also, make sure that you get always the same name for each card. I read your system does not switch them, but who knows, reassurance is not so bad :)
I'll play around some more. Thanks! -Nick -- <<< The Matrix is everywhere. >>> /`-_ Nicholas R. LeRoy The Condor Project { }/ http://www.cs.wisc.edu/~nleroy http://www.cs.wisc.edu/condor \ / nleroy@cs.wisc.edu The University of Wisconsin |_*_| 608-265-5761 Department of Computer Sciences