NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

BossinSauce's avatar
BossinSauce
Aspirant
Nov 15, 2016

Netgear C7000 Nighthawk Modem/Router Combo losing connection

 

    I recently looked into logs and event logs and maybe have found the issue but I don't know how to resolve them. I'm in need of help and what i can do to fix it. My product is out of warranty and really cant afford to buy a new one even though its working fine. I will post logs below and please help me. Event Logs and Logs Below!

 

Event Logs:

1970-1-1, 00:00:38Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:46Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:42Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:42Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-10-15, 02:04:58Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
2016-10-19, 00:51:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
2016-10-20, 18:16:05Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
2016-10-23, 02:29:20Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
2016-10-25, 04:09:06Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
2016-10-31, 17:56:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
2016-11-1, 20:31:55Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-11-6, 02:47:17Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:43Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:02:04Critical (3)TFTP failed - Request sent - No Response;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:02:04Critical (3)TFTP Request Retries exceeded, CM unable to register
1970-1-1, 00:02:16Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:40Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:40Notice (6)WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:43Critical (3)No Ranging Response received - T3 time-out;CM-MAC=40:5d:82:38:d3:20;CMTS-MAC=00:01:5c:88:04:49;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:47Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-11-15, 06:11:06Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 06:26:14Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 07:14:05Notice (6)WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 07:29:22Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 08:50:48Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 09:05:55Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 09:23:13Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 10:11:56Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 10:28:40Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 10:43:54Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 12:01:24Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 12:16:30Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 13:01:44Notice (6)WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
2016-11-15, 16:04:29Notice (6)WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE

 

Firmware
Hardware
Security
Troubleshooting

4 Replies

  • BossinSauce's avatar
    BossinSauce
    Aspirant
    Nov 15, 2016

    Logs: (goes on and on but had to resize due to restrictions

     

    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:51:15 20160.0.0.0:00.0.0.0:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Tue Nov 15 17:51:12 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 03Tue Nov 15 17:51:08 201673.75.242.34:0130.0.3.176:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:50:37 20160.0.0.0:00.0.0.0:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 02Tue Nov 15 17:50:36 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Tue Nov 15 17:49:49 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 02Tue Nov 15 17:49:02 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 17:47:49 201673.75.242.34:0130.0.3.176:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:33:46 20160.0.0.0:00.0.0.0:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 02Tue Nov 15 17:32:57 201673.75.242.34:0130.0.3.176:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:31:41 20160.0.0.0:00.0.0.0:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:26:00 20160.0.0.0:00.0.0.0:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Tue Nov 15 17:25:30 201673.75.242.34:0130.0.3.176:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:24:55 20160.0.0.0:00.0.0.0:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 17:09:39 20160.0.0.0:00.0.0.0:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 07Tue Nov 15 17:07:10 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 02Tue Nov 15 16:57:04 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 05Tue Nov 15 16:55:53 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Tue Nov 15 16:49:15 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 08Tue Nov 15 16:49:08 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 16:46:34 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 03Tue Nov 15 16:46:34 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 16:45:43 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 01Tue Nov 15 16:45:43 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 16:45:43 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Tue Nov 15 16:45:43 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 16:45:42 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 05Tue Nov 15 16:45:42 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 02Tue Nov 15 16:45:41 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 02Tue Nov 15 16:45:41 201673.75.242.34:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 16:45:02 201673.75.242.34:0130.0.3.176:0
    [DHCP IP: 192.168.0.14] to MAC address a4:b8:05:67:73:121Tue Nov 15 16:39:41 20160.0.0.0:00.0.0.0:0
    [DHCP IP: 192.168.0.17] to MAC address 88:71:e5:a6:e5:631Tue Nov 15 07:56:03 20160.0.0.0:00.0.0.0:0
    [DHCP IP: 192.168.0.13] to MAC address 48:5d:60:3c:c3:431Tue Nov 15 05:26:14 20160.0.0.0:00.0.0.0:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 03Tue Nov 15 05:25:10 2016120.234.61.162:0130.0.3.176:0
    [DHCP IP: 192.168.0.15] to MAC address 5c:dc:96:ba:7d:461Tue Nov 15 04:19:57 20160.0.0.0:00.0.0.0:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 01Tue Nov 15 01:21:45 2016120.234.61.162:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 01Tue Nov 15 00:51:59 201664.48.155.244:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Tue Nov 15 00:09:04 2016120.234.61.162:0130.0.3.176:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Mon Nov 14 22:02:44 201664.48.155.244:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Mon Nov 14 22:02:43 201664.48.155.244:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 02Mon Nov 14 22:02:43 201664.48.155.244:0130.0.3.176:0
    [DoS attack: Illegal Fragments] from 130.0.3.176, port 01Mon Nov 14 22:02:43 201664.48.155.244:0130.0.3.176:0
    [DoS attack: Teardrop or derivative] from 130.0.3.176, port 01Mon Nov 14 22:02:43 201664.48.155.244:0130.0.3.176:0
    [DoS attack: Ping Of Death] from 130.0.3.176, port 01Mon Nov 14 22:02:43 201664.48.155.244:0130.0.3.176:0
    • DarrenM's avatar
      DarrenM
      Sr. NETGEAR Moderator
      Nov 17, 2016

      Hello BossinSauce

       

      Sometimes DOS attacks are not always a DOS attack it could be some site you use or program you use that looks like a DOS attack you would have to look up the 130.0.3.176 address and find where it is coming from to see if its bad or not.

       

      DarrenM

  • BossinSauce's avatar
    BossinSauce
    Aspirant
    Nov 18, 2016
    I've had some issues today and not seeing any event logs but still seeing these DOS attempts the target up address isn't even mine it points to another country and the source is also another country. Not sure on why/how this could be happening. Could it be the router malfunctioning? It happens when no one is here and all devices are shut down so I don't think it's a program and no Ethernet is plugged in.
    • DarrenM's avatar
      DarrenM
      Sr. NETGEAR Moderator
      Nov 21, 2016

      Hello BossinSauce 

       

      It could be the modem I would contact your ISP and see if they are able to switch your IP address and then if its still happening we will know its something going on the local network not someone attacking your Ip address.

       

      DarrenM