Hub 3 DHCP RENEW WARNING and No Ranging Response received

[JazzyK]

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:53	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2022 18:09:55	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2022 09:25:53	Error	DHCP 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:23	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 21:25:53	Error	DHCP 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:2	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/01/2022 15:06:16	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/01/2022 11:55:17	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/01/2022 22:23:26	Error	DHCP 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:20	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2021 13:39:51	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2021 07:28:35	Error	DHCP 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:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2021 19:28:35	Error	DHCP 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:14	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2021 07:28:35	Error	DHCP 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:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/12/2021 07:28:34	Error	DHCP 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:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2021 06:15:37	Error	DHCP 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

1	330750000	12.3	38	256 qam	25
2	234750000	12.1	38	256 qam	13
3	242750000	12.3	40	256 qam	14
4	250750000	12	38	256 qam	15
5	258750000	11.8	38	256 qam	16
6	266750000	11.8	38	256 qam	17
7	274750000	11.8	38	256 qam	18
8	282750000	12	40	256 qam	19
9	290750000	12	40	256 qam	20
10	298750000	12.5	38	256 qam	21
11	306750000	12	38	256 qam	22
12	314750000	12	38	256 qam	23
13	322750000	12.3	38	256 qam	24
14	338750000	12.5	38	256 qam	26
15	346750000	12.5	38	256 qam	27
16	354750000	12.5	40	256 qam	28
17	362750000	12.1	40	256 qam	29
18	370750000	12	40	256 qam	30
19	378750000	12	38	256 qam	31
20	386750000	11.5	38	256 qam	32
21	394750000	11.5	40	256 qam	33
22	402750000	11.5	38	256 qam	34
23	410750000	11.5	38	256 qam	35
24	418750000	11.6	38	256 qam	36

Downstream bonded channels

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

1	Locked	38.9	14	0
2	Locked	38.9	10	0
3	Locked	40.3	16	0
4	Locked	38.9	11	0
5	Locked	38.9	19	0
6	Locked	38.9	22	0
7	Locked	38.9	14	0
8	Locked	40.3	14	0
9	Locked	40.3	14	0
10	Locked	38.6	11	0
11	Locked	38.9	10	0
12	Locked	38.9	17	0
13	Locked	38.6	16	0
14	Locked	38.6	14	0
15	Locked	38.9	11	0
16	Locked	40.3	13	0
17	Locked	40.3	18	0
18	Locked	40.3	21	0
19	Locked	38.9	13	0
20	Locked	38.9	18	0
21	Locked	40.3	15	0
22	Locked	38.6	15	0
23	Locked	38.9	15	0
24	Locked	38.9	19	0

[JazzyK]

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

[Adduxi]

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.

[Serena_C]

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

[ravenstar68]

---

@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.

[legacy1]

---

@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?