Welp, this is my first post on this forum :) I've always been using Windows, and now I've decided to try Linux, but I have a problem.

I'm running Mandrake 7.2 and I cannot figure out how to get my cable modem working. My cable provider is @Home, and something seems to be wrong with the DHCP client. My ethernet seems to be working fine (I'm using Mandrake and when I go to DrakConf and Interent Settings it automaticly selects the "VIA Rhine" module. My ethernet card is a D-Link DFE530TX Rev. A). However when I boot into Mandrake it says:

Bringing up interface eth0: determining IP information for eth0 via dhcpcd... failed.

Does anyone know how to fix this? I've asked about 3 people on irc.openprojects.net and nobody has been able to help me yet. Please Help! I'm very new to this :(

Oh yes and I have set my hostname to the number @Home gave me (cr71431-a). At least I think I have maybe I didn't set it up right. But when I type hostname in the console it DOES say cr71431-a so it should be working.. right?

Let's see
 

I had a similar problem the other day, couldn't get a IP via a @home derivative...
What finally worked for me was installing the dhcpcd package (was on the RH CD, I am sure it's on Mandrake as well) and a simple dhcpcd -B got the job done! The Howto's at linuxdocs.org didn't help that much til I started fooling around w/the switches myself...
Same goes for the adaptations of the ifup and ifdown scripts.
Though my routing still doesn't work but I already made it to the dynamic IP. so I am still doing something wrong. I just don't have much time right now to keep trying.

Just got AT&T @Home in California. I'm running slackware 7.0 with dhcpcd 1.3. I found that I had to use the -I switch to get the @Home dhcp server to recognize me. The command was something like:

/sbin/dhcpcd -d -I a123456-b

I originally used the -h switch but it didn't work. -d is for debug messages.

Thanks xcskwng

Could I have the same problem?
 

I'm using Telstra Big Pond Advance, and actually had it working OK until I rebooted the Linux box. I changed nothing between when it was working and the reboot.

After that I couldn't connect to anything, even ping or ftp;
a ping would return:
10.1.12.0 (or something, can't remember exactly): Packet Filtered.
10.1.12.0: Packet Filtered
10.1.12.0: Packet Filtered
etc.

And an ftp would return :
no route to host

I did notice this morning before I had to come to work (bummer) that the DHCPCD process is bound to my internal NIC and not the one which is connected to nmy cable modem.

Do you think a DHCPCD -B or whatever would fix it?

This is somewhat off the subject, but ditch @Home. They have been sending out cease and disest letters like mad because of the RIAA. Never used @Home, never will. End of sermon.