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

Forum Discussion

timmyK's avatar
timmyK
Aspirant
Dec 04, 2021

NETGEAR c7000v2 slow speed with blinking lights

I have 200 Mbps connection and I get around 120-180 Mbps during the day. At nights, it gets slow. (20-40 Mbps).   These lights are blinking a green light on the router:  Download arrow 2.4GHz ic...
timmyK's avatar
timmyK
Aspirant
Dec 04, 2021

This is the connection page after restarting the router. Speed seems faster now but the lights are still blinking.

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel651000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)
 
Downstream Bonded Channels (Partial Service)
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25644651000000 Hz-0.3 dBmV39.7 dB00
2LockedQAM25624531000000 Hz-0.8 dBmV38.7 dB00
3LockedQAM25625537000000 Hz-0.6 dBmV40.2 dB00
4LockedQAM25626543000000 Hz-0.6 dBmV40.1 dB00
5LockedQAM25627549000000 Hz-0.7 dBmV40.1 dB00
6LockedQAM25628555000000 Hz-0.7 dBmV39.8 dB00
7LockedQAM25629561000000 Hz-0.7 dBmV39 dB00
8LockedQAM25630567000000 Hz-0.7 dBmV39.5 dB00
9LockedQAM25631573000000 Hz-0.6 dBmV39.9 dB00
10LockedQAM25632579000000 Hz-0.5 dBmV39.7 dB00
11LockedQAM25633585000000 Hz-0.4 dBmV39.8 dB00
12LockedQAM25634591000000 Hz-0.4 dBmV39.4 dB00
13LockedQAM25635597000000 Hz-0.4 dBmV38.1 dB00
14Not LockedUnknown36603000000 Hz0.0 dBmV0.0 dB00
15LockedQAM25637609000000 Hz-0.4 dBmV33.4 dB519289066
16LockedQAM25638615000000 Hz-0.4 dBmV40.1 dB00
17LockedQAM25639621000000 Hz-0.6 dBmV40.5 dB00
18LockedQAM25640627000000 Hz-0.6 dBmV38.8 dB00
19LockedQAM25641633000000 Hz-0.6 dBmV38.6 dB00
20LockedQAM25642639000000 Hz-0.4 dBmV40.2 dB00
21LockedQAM25643645000000 Hz-0.2 dBmV40.8 dB00
22LockedQAM25645657000000 Hz-0.5 dBmV40.3 dB00
23LockedQAM25646663000000 Hz-0.6 dBmV40.3 dB00
24LockedQAM25647669000000 Hz-0.4 dBmV40.3 dB00
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA65120 Ksym/sec22800000 Hz52.3 dBmV
2LockedATDMA55120 Ksym/sec16400000 Hz53.3 dBmV
3LockedATDMA75120 Ksym/sec29200000 Hz50.8 dBmV
4LockedATDMA85120 Ksym/sec35600000 Hz50 dBmV
5Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Fri Dec 03 22:14:49 2021
System Up Time:00:08:27
plemans's avatar
plemans
Guru - Experienced User
Dec 04, 2021

Are you using an amplifier? Based off the power levels that you have for your downstream, your upstream is pretty high. 

If you have any amplifiers, splitters, or signal attenuators in the line, remove them. 

 

do you also have the modem event logs? That helps us check long term. 

All rebooting does is clear out the errors. It might help the speeds short term if the modem connects on a different frequency but long term, it isn't going to fix the problem. 

  • timmyK's avatar
    timmyK
    Aspirant
    Dec 06, 2021

    plemans Thanks for the reply. I don't have any amplifier setup. I hooked up the ISP cable directly into my router

     

    Connection seems to be stable now, but the lights on the router are still blinking. (downstream arrow, 2.4ghz, 5 ghz icons). 

     

    Attaching the event logs:(Advanced > Administration > Event Logs)

    TimePriorityDescription
    2021-12-3, 22:13:04Warning (5)MDD message timeout;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.1;CM-VER=3.0;
    1970-1-1, 00:00:45Notice (6)Honoring MDD; IP provisioning mode = IPv6
    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:40Notice (6)WiFi Interface [wl0] set to Channel 2 (Side-Band Channel:N/A) - Reason:INIT
    1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-11-24, 12:22:52Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.1;CM-VER=3.0;
    2021-11-15, 12:35:58Critical (3)SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.1;CM-VER=3.0;
    1970-1-1, 00:00:37Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2021-11-8, 22:48:10Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.1;CM-VER=3.0;
    1970-1-1, 00:39:09Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:39:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:38:58Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:38:56Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:38:55Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:38:07Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:38:06Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:38:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:37:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:37:22Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:36:35Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:36:31Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:36:29Critical (3)No UCDs Received - Timeout;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:36:12Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:36:11Critical (3)No UCDs Received - Timeout;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:35:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:35:53Critical (3)No UCDs Received - Timeout;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:35:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:35:28Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:41Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:40Critical (3)No UCDs Received - Timeout;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:23Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:22Critical (3)No UCDs Received - Timeout;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:05Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:04Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:34:01Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:33:14Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:33:08Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:33:08Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;
    1970-1-1, 00:33:06Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=28:80:88:4d:0b:98;CMTS-MAC=00:01:5c:65:0e:72;CM-QOS=1.0;CM-VER=3.0;


    And here is the logs (Advanced > Administration > Logs)

     

    I was very concerned about DoS attack at first, but then read online that it's a false alarm due to iPhone or iPad devices.

    https://community.netgear.com/t5/Cable-Modems-Routers/DoS-attack-Teardrop-or-derivative-Ping-of-Death-strange-IPv6/m-p/2051922/highlight/true#M30355

    admin login failure] from source 192.168.0.211Mon Dec 06 13:01:03 20210.0.0.0:0192.168.0.21:0
    [DoS attack: Ping Of Death] from 73.1.0.80, port 03Mon Dec 06 12:49:22 2021232.215.176.155:073.1.0.80:0
    [DoS attack: Teardrop or derivative] from 73.1.0.80, port 01Mon Dec 06 12:49:20 2021232.215.176.155:073.1.0.80:0
    [DoS attack: Ping Of Death] from 73.1.0.80, port 02Mon Dec 06 12:48:36 2021232.215.176.155:073.1.0.80:0
    [DoS attack: Teardrop or derivative] from 73.1.0.80, port 02Mon Dec 06 12:48:35 2021232.215.176.155:073.1.0.80:0
    [DoS attack: Ping Of Death] from 73.1.0.80, port 08Mon Dec 06 12:46:33 2021232.215.176.155:073.1.0.80:0

     

    • plemans's avatar
      plemans
      Guru - Experienced User
      Dec 07, 2021

      The 2.4ghz/5ghz lights will blink. That just indicates data transfer. 

      the downstream icon should be locked. 

      You are having error and not locked channels. 

      And while your power is technically in spec, somethings causing issues. That can be told by how high your upstream power levels are in relation to your downstream. Add in the errors and not locked channels and I'd be checking the cable/wires/connectors. 

      If that doesn't help, then the ISP would need to check the line.