WRT54G + Comcast = random cutouts?
|
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
|||||||||||||
|
Posted by Justin on December 2, 2009, 1:23 am
Please log in for more thread options
Two days ago my WRT54G V6 started cutting out the internet connection for no reason. I updated the firmware and that didn't help. Per Google I changed the MTU from auto to 1492, I thought that worked until just now it cut out on me. The cable modem is a Linksys BEFCMU10 version 4. When I go to its diagnostic page http://192.168.100.1/ this is what I get: Modem Standard Specification Compliant DOCSIS 2.0 Hardware Version v2.0 Software Version 2.0.3.4.2-1212 Cable Modem MAC Address <removed> Cable Modem Serial Number <removed> CM certificate Installed CONNECTION: Startup Procedure Status Comment Acquire Downstream Channel 723000000 Hz Locked Connectivity State Operational Operational Boot State OK Operational Security Enabled BPI+ Downstream Channel Lock Status Operational Modulation 256QAM Channel ID 45 Provisioned Rate 6600 kbps Symbol Rate 5360.537 Ksym/sec Downstream Power 1.2 dBmV SNR 38.2 dB Upstream Channel Lock Status Operational Modulation 16QAM Channel ID 2 Provisioned Rate 1100 kbps Symbol Rate 5120 Ksym/sec Upstream Power 37.2 dBmV and the log Time Priority Description 2009-12-02 01:13:12 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-02 01:13:08 critical No Ranging Response received - T3 time-out 2009-12-02 01:13:03 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 2009-12-02 01:12:30 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 22:56:19 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 2009-12-01 22:55:47 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 20:57:49 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 2009-12-01 20:57:16 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:58:03 critical No Ranging Response received - T3 time-out 2009-12-01 00:57:58 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout 2009-12-01 00:57:57 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:26 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:24 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:23 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:21 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:21 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:18 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:16 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:15 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:14 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:12 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:11 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:09 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:07 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:06 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:04 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:03 critical DHCP FAILED - Request sent, No response 2009-12-01 00:57:02 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:57:00 critical DHCP FAILED - Request sent, No response 2009-12-01 00:56:59 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out 2009-12-01 00:56:57 critical DHCP FAILED - Request sent, No response 1970-01-01 00:00:06 critical No Ranging Response received - T3 time-out | |||||||||||||
|
Posted by f/fgeorge on December 2, 2009, 5:51 am
Please log in for more thread options On Wed, 02 Dec 2009 01:23:10 -0500, Justin  same router and it works just fine. Have you tried an alternative software for the router? | |||||||||||||
|
Posted by Justin on December 2, 2009, 5:00 pm
Please log in for more thread options f/fgeorge wrote: Its not getting hot, it has been sitting in the same place for the last year without a problem. There's no dust. I heard about alternative firmwares for the Linksys... Which one should I try? | |||||||||||||
|
Posted by f/fgeorge on December 2, 2009, 6:19 pm
Please log in for more thread options On Wed, 02 Dec 2009 17:00:50 -0500, Justin All the reviewers like Tomato, I use HyperWrt 2.0, it works fine for me. | |||||||||||||
|
Posted by Justin on December 2, 2009, 11:16 pm
Please log in for more thread options f/fgeorge wrote: Both of which I can't use due to version 6.0. | |||||||||||||
|
Home Cabling Guide
Finally, an instantly downloadable book that saves you thousands in home improvement dollars! Enjoy living in 21st century technology-advanced home while increasing its selling value and competitive advantage on the real estate market. Whether your cabling is for home office or high-tech leisure, you can wire your home yourself or learn "wirish" to speak with your cabling contractors in their language! Click Here to learn more |
>for no reason.
>I updated the firmware and that didn't help. Per Google I changed the
>MTU from auto to 1492, I thought that worked until just now it cut out
>on me.
>The cable modem is a Linksys BEFCMU10 version 4.
>When I go to its diagnostic page http://192.168.100.1/ this is what I get:
>Modem