eth0 not getting IP address from DHCP server
I have this computer I use to play around with linux (let's call it a test system :) ) and all was well ... until our internet connection got upgraded - we moved from IP addresses starting with 192. to a range starting with 82. The Windows computers (my father's, brother's and my other one) are fine, no problem at all, but the linux computer suddenly refused to load the module for the NIC.
After some searching I found what module it should load (tulip) and uncommented this line in /etc/rc.d/rc.modules
Still no go.
Some searching around left me with a few topics here that seemed more or less relevant at the time (when I was looking for the correct module to load) but, unfortunately, none of them had a solution to offer.
What they did offer me was a few commands I should run and that you might need.
ifconfig -a gives me this :
I tried running dhcpcd (as a background process, should that matter) but after some time it exits with code 14 (whatever that means).
Another thing I came across was someone who solved a problem by getting rid of the dhcpcd-eth0.cache, dhcpcd-eth0.info and dhcpcd-eth0.pid (which I don't have) in the /etc/dhcpc dir through his shutdown script (which makes me assume they don't need to exist when the computer boots).
I tried manually renaming these files by adding .bak to the end. The only result of this is that now at boot, I also get the message
When doing this through the rc.6 script (inserting the mv command right after the code that gets rid of the dhcpcd) the exact same thing happens : a DHCP_DISCOVER without a result.
I'd start to think that the DHCP server was unreachable, but both the linux computer and the computer I'm using atm are connected to the same hub, which is then connected to the cable modem via another hub. The hardware all seems to be fine as far as I can tell.
Any ideas on what the problem could be in the first place? (solutions are more than welcome as well of course, but I don't mind doing some searching if I know what to look for :P)
Try in a root terminal
First of all, thanks for taking the time to read all that. I assume that by ifdown eth0 you mean ifconfig eth0 down.
eth0 was already down (since it did not show up when running ifconfig, only with the -a option). So to my (untrained) eye, the only effect of this is that I don't need the -a option when running ifconfig to see eth0.
Your on a router with 2 other systems? Try to restart service
in root terminal
I think I created a small misunderstanding somewhere : I don't use a router, only two hubs. Hub1 is attached to the cable modem. Hub2, my father's computer and my brother's computer are also attached to Hub1. My two computers are attached to Hub2
As for the network service : I have but one dir called init.d on my system and that's located in /usr/lib/mozilla-1.7.5/
Searching for a file named "*network*" returned a lot of HTML and other documents, icons, lib files?
Searching for a file named "network" did the same thing, only with fewer results (duhh :rolleyes: )
Am I missing a package somewhere?
(note : netwatch tells me that there is no eth0 device to work with, even though it still shows up in ifconfig!)
|All times are GMT -5. The time now is 10:54 AM.|