Menu
Reply
JazzyK
  • 2
  • 0
  • 0
Joining in
743 Views
Message 1 of 6
Flag for a moderator

Hub 3 DHCP RENEW WARNING and No Ranging Response received

I've been having constant drops in WiFi connectivity. This only occurs on WiFi and not when connected via ethernet. Video-calls on WiFi are near impossible due to the constant packet loss. This has only started happening since mid-December 2021 (I initially thought this was due to a Christmas tree near the Hub 3..but no.)

I've done all the usual steps to no avail. 

  • Turning the hub off for 5 minutes
  • Changing 2.4Ghz and 5Ghz channel bands
  • Pinhole resets
  • Updating the hub

After checking the logs I found these Critical and Error warnings which coincide with the time I first started noticing the issue. I've found other threads with the same log entries, though the suggested solutions didn't work for me. 

Network Log

Time Priority Description

11/01/2022 14:28:53noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2022 18:09:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2022 09:25:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2022 04:27:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 21:25:53ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 15:54:2criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 15:06:16noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/01/2022 11:55:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/01/2022 22:23:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2021 21:17:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2021 13:39:51noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 07:28:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 20:30:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 19:28:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/12/2021 12:27:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2021 07:28:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/12/2021 23:02:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/12/2021 07:28:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2021 19:02:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2021 06:15:37ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

133075000012.338256 qam25
223475000012.138256 qam13
324275000012.340256 qam14
42507500001238256 qam15
525875000011.838256 qam16
626675000011.838256 qam17
727475000011.838256 qam18
82827500001240256 qam19
92907500001240256 qam20
1029875000012.538256 qam21
113067500001238256 qam22
123147500001238256 qam23
1332275000012.338256 qam24
1433875000012.538256 qam26
1534675000012.538256 qam27
1635475000012.540256 qam28
1736275000012.140256 qam29
183707500001240256 qam30
193787500001238256 qam31
2038675000011.538256 qam32
2139475000011.540256 qam33
2240275000011.538256 qam34
2341075000011.538256 qam35
2441875000011.638256 qam36

 

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.9140
2Locked38.9100
3Locked40.3160
4Locked38.9110
5Locked38.9190
6Locked38.9220
7Locked38.9140
8Locked40.3140
9Locked40.3140
10Locked38.6110
11Locked38.9100
12Locked38.9170
13Locked38.6160
14Locked38.6140
15Locked38.9110
16Locked40.3130
17Locked40.3180
18Locked40.3210
19Locked38.9130
20Locked38.9180
21Locked40.3150
22Locked38.6150
23Locked38.9150
24Locked38.9190
0 Kudos
Reply
JazzyK
  • 2
  • 0
  • 0
Joining in
736 Views
Message 2 of 6
Flag for a moderator

Re: Hub 3 DHCP RENEW WARNING and No Ranging Response received

Here is a 60 Ping test:

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=5.728 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=3.897 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=2.864 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=3.182 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=2.664 ms

64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=2.695 ms

64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=4.176 ms

64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=2.848 ms

64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3.846 ms

64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=3.070 ms

64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=3.998 ms

64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=118.318 ms

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=116.690 ms

64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=2.471 ms

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

Request timeout for icmp_seq 18

Request timeout for icmp_seq 19

Request timeout for icmp_seq 20

Request timeout for icmp_seq 21

Request timeout for icmp_seq 22

Request timeout for icmp_seq 23

Request timeout for icmp_seq 24

64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=7.328 ms

Request timeout for icmp_seq 26

Request timeout for icmp_seq 27

Request timeout for icmp_seq 28

Request timeout for icmp_seq 29

Request timeout for icmp_seq 30

Request timeout for icmp_seq 31

Request timeout for icmp_seq 32

Request timeout for icmp_seq 33

64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=163.678 ms

64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=76.570 ms

Request timeout for icmp_seq 36

Request timeout for icmp_seq 37

Request timeout for icmp_seq 38

Request timeout for icmp_seq 39

Request timeout for icmp_seq 40

64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=42.492 ms

Request timeout for icmp_seq 42

Request timeout for icmp_seq 43

Request timeout for icmp_seq 44

Request timeout for icmp_seq 45

Request timeout for icmp_seq 46

Request timeout for icmp_seq 47

Request timeout for icmp_seq 48

Request timeout for icmp_seq 49

64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=4.177 ms

64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=114.860 ms

Request timeout for icmp_seq 52

64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=31.299 ms

64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=3.821 ms

64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=4.125 ms

64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=3.758 ms

64 bytes from 192.168.0.1: icmp_seq=57 ttl=64 time=23.137 ms

64 bytes from 192.168.0.1: icmp_seq=58 ttl=64 time=3.665 ms

64 bytes from 192.168.0.1: icmp_seq=59 ttl=64 time=4.076 ms

64 bytes from 192.168.0.1: icmp_seq=60 ttl=64 time=4.288 ms

^C

--- 192.168.0.1 ping statistics ---

61 packets transmitted, 28 packets received, 54.1% packet loss

round-trip min/avg/max/stddev = 2.471/27.276/163.678/44.829 ms
0 Kudos
Reply
Adduxi
  • 6.09K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
722 Views
Message 3 of 6
Flag for a moderator

Re: Hub 3 DHCP RENEW WARNING and No Ranging Response received

You can ignore those DHCP RENEW WARNING and No Ranging Response received errors as this is normal for VM Hubs.  It is to do with the way they request a DHCP WAN IP address.

However, your Downstream power levels are too hign, range should be -6 to +10.   A VM technician will be needed to fix this.  Either phone in or wait here a day or two for a VM Mod to pick this up.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
Serena_C
  • 2.19K
  • 91
  • 215
Forum Team (Retired)
Forum Team (Retired)
667 Views
Message 4 of 6
Flag for a moderator

Re: Hub 3 DHCP RENEW WARNING and No Ranging Response received

Hi @JazzyK

Welcome to our Community Help Forum 🙂

Sorry to see that your Downstream Levels are out of spec and that your connection keeps dropping, I understand this must be frustrating for you. I would like to book a technician visit for you to get this fixed 🙂 I shall send you a private message to obtain the details required now. Please look out for the purple envelope in the top right corner and get back to me when you can.

Best wishes,

Serena

0 Kudos
Reply
ravenstar68
  • 19.64K
  • 1.15K
  • 8.64K
Very Insightful Person
Very Insightful Person
649 Views
Message 5 of 6
Flag for a moderator

Re: Hub 3 DHCP RENEW WARNING and No Ranging Response received


@Adduxi wrote:

You can ignore those DHCP RENEW WARNING  - Correct

and No Ranging Response received errors as this is normal for VM Hubs. IIncorrect 

It is to do with the way they request a DHCP WAN IP address.- Half right.

However, your Downstream power levels are too hign, range should be -6 to +10.   A VM technician will be needed to fix this.  Either phone in or wait here a day or two for a VM Mod to pick this up.

T3 errors (No ranging response) Usually indicate issues on the upstream side of the connection - Although they can also occur when the hub is first connecting to the DOCSIS network as well.


The DHCP renew ignores the invalid field and carries on.  Typically Virgin Media ignores RENEW messages anyway until the DHCP client switched to rebind mode at about 87.5% of the lease time.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
legacy1
  • 19.56K
  • 800
  • 2.07K
Alessandro Volta
635 Views
Message 6 of 6
Flag for a moderator

Re: Hub 3 DHCP RENEW WARNING and No Ranging Response received


@JazzyK wrote:

--- 192.168.0.1 ping statistics ---

61 packets transmitted, 28 packets received, 54.1% packet loss

round-trip min/avg/max/stddev = 2.471/27.276/163.678/44.829 ms

This by wireless?

---------------------------------------------------------------
0 Kudos
Reply