I am trying to connect to internet via cable-modem. I was able to connect to the net before I upgraded my OS from RH 8.2 to 9.0. The device is recognised and starts fine when I start Linux. I did the following:
ping -c 5 192.168.0.189
--- 192.168.0.189 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms


My network setup seems to be fine. I use DHCP for ipaddress and DNS.
ifconfig returns the following:
eth0 Link encap:192.168.XXX.XXX Bcast:192.168.XXX.XXX Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
RX packets:576 errors:0 dropped:0 overruns:0 frame:0
TX packets:3435 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:88684 (86.6 Kb) TX bytes:374292 (365.5Kb)
Interrup:9 Base address:0xd400

Thanks

*************
I am trying to connect to internet via cable-modem. I was able to connect to the net before I upgraded my OS from RH 8.2 to 9.0. The device is recognised and starts fine when I start Linux. I did the following:
ping -c 5 192.168.0.189
--- 192.168.0.189 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms
*************

The ping command is just a test, it won't help you fixing, just testing. In this case, it told you that there were 100% loss, which is the same as no connection at all.


************
My network setup seems to be fine. I use DHCP for ipaddress and DNS.
ifconfig returns the following:
eth0 Link encap:192.168.1.102 Bcast:192.168.1.225 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
RX packets:576 errors:0 dropped:0 overruns:0 frame:0
TX packets:3435 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:88684 (86.6 Kb) TX bytes:374292 (365.5Kb)
Interrup:9 Base address:0xd400
*****************

This info is quite intriguing. It seems that your setup is made with internal IP's (begining with 192.168.x.x). There's nothing wrong with that, but its the first time I see such a setup in a cable modem connection. My connection is cable and we receive regular IP's (not 192.168.x.x). It is as your connection is one large internal network managed by the cable provider.

Perhaps you want to try the commands (as root):

ifdown eth0
and
ifup eth0

The first will bring the interface down, and the second will bring it up, forcing the dhcp client to run again and try to get IP.

ping -c 5 192.168.0.189
--- 192.168.0.189 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4010ms
is your cable routers adress 192.168.0.189 ?
you need to know that obviously 100% loss means that not one ping was sucessful.

eth0's adress is : 192.168.1.102
with a subnet mask of 255.255.255.0 witch means both of them are on different networks!
if you could change the adress of your eth0 to 192.168.0.xxx xxx being an unused adress then I should think that your problem should be solved... if you added 192.168.0.189 as your default gateway :P Use neat or setup to edit your network settings (I know that works on basicly all red-hat flavours) otherwise just use ifconfig, use 255.255.255.0 as your subnet mask.


ok.. your broadcast adress is 192.168.1.225, your subnet mask needs to be changed to 255.255.255.0 so that everything just works for the moment if you want to segment your network, just get it up and owrking first.