Have you turn off your cable modem for few minutes when switch from Windows machine to Linux machine? That is very common problem that I have seen and happened to me before. Leon Do doug waud wrote:
I was wondering if someone can help me configure a cable modem to use in linux.
I think the issue is configuring your computer. The cable modem is probably configured by the cable company (I bet they came in, ran Windows and got that working and then left. At that point the cable modem was "doing its thing" and you were left to fend for yourself on the linux side. That was my experience here in Shrewsbury. Incidentally, this is not all that unreasonable. After all they are a business and cannot afford to go far off the beaten path.)
I setup my ethernet card eth0 this seems to have taken because I can ping localhost. However I cannot ping past it.
Hi
As one responder has already noted, we really need more information. However, I would suggest you start by typing ifconfig (You will probably have to be root to do this; just type su and enter your root password. Type exit to get out later) This should show an eth0 entry in addition to the lo entry. If you have no eth0 entry get back to us (we have to backtrack). If you have an eth0 entry, look to see what the "inet address" is. For example, on the computer I have connected to the cable modem (Shrewsbury cable, but the general approach should be the same) give 216.195.16.123 which tells me I am on a network not in the local 192.168.m.n class so I read this as an address assigned by the cable company (dhcp, as an earlier responder indicated is likely for you too).
Next try route -n
Here I get three lines of interest, something like
216.195.16.0 0.0.0.0 255.255.248.0 U eth0 0.0.0.0 216.195.16.1 0.0.0.0 UG eth0 127.0.0.0 0.0.0.0 255.0.0.0 U lo
The last line is your loopback address (as already noted by an earlier responder, a side issue).
The first line meshes nicely with the ethernet address we saw above for eth0. This line says that, to get to anything in the network 216.195.16.0 with netmask 255.255.248.0, go out eth0. That makes sense. That card is on that network.
The next line, says that, to go anywhere in general (that's what the 0.0.0.0 means) go through 216.195.16.1. That is another machine on that same network, and represents the "gateway" machine sitting somewhere in the cable company's office.
Note that now my machine knows how to go anywhere. First it can use the first line to get to that 216.195.16.0 network and second, if it wants to go further, it can go to that specific gateway box at 216.195.16.1, which it can find since it is on that 216.195.16.0 network the first line tells us how to reach.
(The U and UG says "up" (and running) and "up" as a "gateway".)
Poke around now and see whether you can find any of these pieces for starters and, for security/safety exit su when done :-)
doug
-- Douglas R Waud 17 Lantern Lane, Shrewsbury, MA, 01545-2006 http://www.ummed.edu/pub/d/drw/ _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug