I'm experiencing a weird problem with one of my Comcast cable modem connections. After several days of running fine, it just seems to inadvertently drop for no reason. If I do a ifconfig eth0, it still shows the interface as up with the correct IP and everything but I can't reach anything outside the local network from the box. And I can't reach the box from anywhere on the outside. If I do a simple ifdown eth0 and then try to bring the interface back up (ifup eth0) or /etc/rc.d/init.d/network restart, the interface hangs while trying to receive an IP via DHCP. However, if I simply bring the interface down and reset the cable modem by unplugging it and then bringing the interface back up it retrieves the IP address and comes up fine.

What I'm wondering is what might be making it go down and how might I correct it? I'm using RedHat 8.0 and a motorola surfboard cable modem. It receives a dynamic IP from Comcast but the IP never seems to change.
Thanks a lot.
AJ

I have exactly the same problem with Comcast. I'm running everything through a Linksys router connected to a Motorola surfboard and when that happens, my lan is fine, but I can't get outside of it. If I just release and then renew the addresses at the router, I get exactly the same IP address and DNS addresses that I had before, but now I can use the internet. Weird if you ask me. I don't think it is at all unusual to keep getting the same IP address from Comcast. I've had the same one for quite some time, even though it is assigned via DHCP. However, my router is always on, so Comcast probably doesn't have much of a chance to assign it to someone else.

At this point, I'm blaming Comcast for the connection problems since the only thing they see is my router and it doesn't change from one day to the next.

I think there were some issues with a certain modem, umm 4220 I think that needs new firmware.

I'm not positive, but if you go over to
http://www.dslreports.com/forum/comcast
you may be able to find some help.

They don't care about routers, but don't mention it if you are running servers because all you will get then is a bunch of people telling you how you are violating the TOS/AUP. Comcast does watch the forum, but is ususally quite in the background.
Good luck.

Question: Are you connecting the cable modem to your computer via USB (module 'CDCEther.o') or via ethernet? Do you see any pertninent messages in your syslog files?

I have the same problem with comcast and the moto surfboard modem. The old modem never had a problem. But this new one does. Anyone have any ideas?

Thanks

I'm still blaming Comcast. It doesn't happen nearly so often for me as it did this spring and absolutely nothing about my network has changed. I also know several other Comcast users who have the same problem from time to time and none of us have similar hardware.