No DHCP-No internet

[trevallion]

I am trying to connect to the Internet directly through a cable modem. However, even when I configured my ethernet card for DHCP in the system tools>networking when I go to 'activate' it, then screen returns "Determining ip information for eth0...{pause} failed". In the /etc/sysconfig/networking/devices folder the ifcfg-eth0 shows it to be in DHCP. dhclient shows no dhcp offers received. Thanks for any help. Running Fedora Core 1, kernel is 2.4.22, I believe.

Related to this thread here (http://www.fedoraforum.org/forum/showthread.php?s=&threadid=289) but I resolved my hardware (i think) so I put the DHCP question where it needed to be.

[djf_jeff]

Ok, I think the easiest way to debug that is to go to a terminal, login with root.

After that, type "ifconfig eth0" and check if you have a card that is there. If yes, your card is supported and detected by Fedora.

After that, type "dhclient eth0" to require a dhcp adress. After that, redo the ifconfig check to see if dhclient has got an adress for you.

Check the message and post it here.

[yoyoned]

A very common problem with cable modems is they "learn" the mac address of th ethernet catd they're attached to, and will not work if a different card is used. Try unplugging the power from the modem for at least 10 seconds and let it "re-learn". A less common problem is some cable ISP's require a hostname be sent with the DHCP request. There is a ton of info on both of these troubles all over the internet. Good Luck

[trevallion]

My MAC address should be fine; it works on the windows boot. There is a response from 'ifconfig eth0', but dhclient shows no offers. Perhaps it is that my cable company requires a hostname, how could I verify this (I'll give it a google, but a site would be nice).

[mhelios]

I used to have to set a hostname given by the ISP in order to connect. Maybe you could call them to get the details if you don't have them?

[Bana]

Yes, definitely call them as I have found that some of the most boogling problems are solved by a simple call. They often know exactly the problem (due to past experience) and help you with an easy solution.

[trevallion]

I called, but to no avail. They said a)I dont need a hostname or password and b)it should work fine. Well it doesnt! Does anyone know the basics on how the request is sent out? Usually there is a broadcast on 255.255.255.255 right? then the Nic listens for responses. On the plus side, all my messing around in the /etc/sysconfig/networking/devices ifcfg-eth0 seem to have netted me something, when i reboot into windows to get on the internet, I have to reset the modem, otherwise windows can't find the server. w00t.

[Jman]

Originally posted by Bana
the most boogling problems
Those are the kind of problems solved by Googling.

Did you mean: boggling? :D

On topic: What modem? In the other thread you mentioned you have Charter cable.

[Bana]

Originally posted by Jman
Those are the kind of problems solved by Googling.

Did you mean: boggling? :D

Grr.. My native language fails me again, or me it, I'm not quite sure...

On Topic:
DHCP Mini-howto Troubleshooting (http://www.tldp.org/HOWTO/DHCP/x74.html#TROUBLESHOOTING) That seems to have quite a few juicy tidbits. Perhaps you could try some/all of the things that are listed there?

On my own, have you tried:

Resetting (unpluging, waiting, pluging back in) the cable modem while your computer is in linux and then running dhcp?
Statically assigning your IP address to something common like 192.168.0.1 and 192.168.1.1?

HTH

[joking]

I've got charter with their supplied cable. It was originally installed on a Win2K server box but frustration levels esculated and I moved on to greener pastures. I'm running FC1 with all the current updates.

With two nics: eth0 Static ip 192.168.0.1 is my lan and eth1 is DHCP to connection to the modem. The modem get's its address from Charter. My eth1 get's it from the modem.

eth1
Broadcast address: 255.255.255.255
Netmask address: 255.255.248.0

eth0
Broadcast address: 192.168.0.255
Netmask address: 255.255.255.0

what you do need is the server addresses...DNS's...
you can gather those from windows "ipconfig" or "winipcfg" and add those to the network configuration parameters use both Primary and Secondary, there may be a third which isn't required.

Once that is set up you may have to configure your Internet Browser to NOT use a proxy setting. If you change the setting close and reopen the browser.

Good Luck!

PS: Also set up a firewall as soon as possible .

[sigusr]

I had a similar problem with my cable modem. The "guy in the back" at my cable provider said an additional script needs to be run on the server for linux connections. When the discussion ended so did my problem. All I can tell is what I saw and heard. I hope this helps.

[wshawn]

I run cable modems via routers. Best case scenerio is leave everything automatic. I have never seen broadband needing someone to hardcode domain name to work as that is the purpose of DHCP.

Another point you may want to consider is this...

Unplug cable modem for about a minute (cable company says 15 minutes) shut computer down and off.

Turn cable modem on.

Once it locks on, turn your system on.


Make sure your network is active. It should instantly work (if you are hooked up ethernet and not usb)

[wshawn]

This might help you. I wrote a howto

HOW TO: Static IP (http://www.fedoraforum.org/forum/showthread.php?s=&threadid=1144)

[sigusr]

I agree with wshawn. Unless you WANT this to be more of a learning experience than it HAS to be let let DHCP do the work.

The problem you describe is exactly the problem I experienced before the cable guy did whatever he did. Windows never faltered. Linux said the ethernet was working but no data. Dual booting Win98 and FC1 on the same machine made me suspect FC1. Always suspect the last change first works most of the time but sometimes it is not your fault.

continuing my saga. I added a second workstation to my home. My cable provider enabled the router in the cable modem. I no longer have to reset the modem every time I reboot into another OS.



I hope this is of some small use to someone.