Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Ethernet dropping out consistently on my hub 5

sullyzk
Joining in

‎22-05-2024 08:32 - edited ‎22-05-2024 08:32

Hi All,

 

I'm having this issue where I keep getting major disconnects during gameplay on an ethernet cable and when streaming on the TV/ipad at night the Wi-Fi just completely drops. I have tried to Power the router on and off, factory reset and I have scheduled an engineer to come today. Below I have attatched my network monitor to show you some of the spikes I get although I gamed from about 5 til a bout 8:30 yesterday. The ethernet is connected to a port which I then plug in upstairs. I have changed the ethernet cables atleast 3-4 times as I thought this could be the problem on that side. Any advice is appreciated I am at wits end with it all now. Any information I could also pass to the engineer that you guys thing would help him would be awesome also.

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fbd531d559bb202cf648cd88635930d965...

 

Thanks 

SK

0 Kudos
8 REPLIES 8

sullyzk
Joining in

on ‎22-05-2024 11:17

22-05-2024 09:33:08
notice
GUI Login Status - Login Success from LAN interface
21-05-2024 17:51:12
critical
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-05-2024 17:51:12
critical
16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-05-2024 17:50:05
critical
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-05-2024 17:17:17
notice
GUI Login Status - Login Success from LAN interface
21-05-2024 17:16:42
notice
GUI Login Status - Login Fail from LAN interface
21-05-2024 14:06:44
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-05-2024 13:02:57
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-05-2024 02:24:48
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
21-05-2024 01:21:00
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
20-05-2024 13:39:04
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
20-05-2024 04:04:45
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 20:40:07
error
DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 13:11:25
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 11:03:48
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 10:00:00
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 08:56:11
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 06:48:33
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-05-2024 05:44:45
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-05-2024 13:47:35
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-05-2024 12:43:46
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-05-2024 10:36:07
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-05-2024 09:32:19
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-05-2024 06:20:53
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18-05-2024 04:13:16
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 22:54:13
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 21:50:24
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 20:46:35
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 18:38:58
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 14:23:43
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 04:49:25
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 00:42:14
notice
REGISTRATION COMPLETE - Waiting for Operational status
17-05-2024 00:42:10
notice
US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 00:42:05
notice
DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
17-05-2024 00:41:57
warning
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos

sullyzk
Joining in
In response to sullyzk

on ‎22-05-2024 11:19

downstream
1
330000000
6.4
41
QAM 256
25
2
138000000
6.8
41
QAM 256
1
3
146000000
6.6
41
QAM 256
2
4
154000000
6.5
41
QAM 256
3
5
162000000
6.4
41
QAM 256
4
6
170000000
6.1
41
QAM 256
5
7
178000000
6
41
QAM 256
6
8
186000000
6.1
41
QAM 256
7
9
194000000
6.2
41
QAM 256
8
10
202000000
6.2
41
QAM 256
9
11
210000000
6.3
41
QAM 256
10
12
218000000
6.3
41
QAM 256
11
13
226000000
6.2
41
QAM 256
12
14
234000000
6.2
41
QAM 256
13
15
242000000
6.1
41
QAM 256
14
16
250000000
5.8
41
QAM 256
15
17
258000000
6
41
QAM 256
16
18
266000000
6.3
41
QAM 256
17
19
274000000
6.7
41
QAM 256
18
20
282000000
6.8
41
QAM 256
19
21
290000000
7
41
QAM 256
20
22
298000000
6.9
41
QAM 256
21
23
306000000
6.8
41
QAM 256
22
24
314000000
6.6
41
QAM 256
23
25
322000000
6.6
41
QAM 256
24
26
338000000
6.3
41
QAM 256
26
27
346000000
5.8
41
QAM 256
27
28
354000000
5.4
41
QAM 256
28
29
362000000
5.4
41
QAM 256
29
30
370000000
5.4
41
QAM 256
30
31
378000000
5.5
41
QAM 256
31

         

1
 
41
30
198
2
 
41
67
164
3
 
41
84
148
4
 
41
98
135
5
 
41
4
0
6
 
41
107
125
7
 
41
91
130
8
 
41
123
105
9
 
41
120
110
10
 
41
116
117
11
 
41
114
116
12
 
41
114
118
13
 
41
104
127
14
 
41
85
147
15
 
41
86
150
16
 
41
84
144
17
 
41
74
159
18
 
41
62
172
19
 
41
48
184
20
 
41
34
197
21
 
41
40
189
22
 
41
40
194
23
 
41
26
207
24
 
41
26
210
25
 
41
25
207
26
 
41
35
195
27
 
41
21
208
28
 
41
49
184
29
 
41
65
168
30
 
41
67
169
31
 
41
73
165

           

37
94
4K
1840
QAM 4096
1108

           

37
 
42
7.4
339981329
42
0 Kudos

sullyzk
Joining in

on ‎22-05-2024 11:20

upstream
0
49600000
47.3
5120
QAM 64
1
1
43100000
47
5120
QAM 64
2
2
36600000
47
5120
QAM 64
3
3
30100000
47
5120
QAM 64
4
4
23600000
47
5120
QAM 64
5

           

0
ATDMA
0
0
0
0
1
ATDMA
0
0
0
0
2
ATDMA
0
0
0
0
3
ATDMA
0
0
0
0
4
ATDMA
0
0
0
0

         

6
10.4
42.5
2K
QAM 256

           

6
OFDMA
208
74000000
18
0
0 Kudos

RT123
Up to speed
In response to sullyzk

on ‎22-05-2024 11:22

Let the engineer know about the PostRS errors on the downstream (this is particularly important as the BQM shows significant packet loss at one point)

I do not work for VM, just trying to help!
0 Kudos

sullyzk
Joining in
In response to RT123

on ‎22-05-2024 11:39

Thank you, I will note that down and when he arrives mention it to him. Does it look likely to be a problem on there end due to that?

0 Kudos

sullyzk
Joining in

on ‎22-05-2024 15:59

UPDATE: Engineer hasn't come at 12-4 time slot allocated. Sat here for 4 miserable hours. It appears I had another lag spike and the packet loss is still there. Frusturated because I've now wasted a day sat in, when I could have done my other errands. Is it possible that they come after the 4 o'clock allocated slot? Who knows? We will find out shortly. 

0 Kudos

jbrennand
Very Insightful Person
Very Insightful Person
In response to sullyzk

on ‎22-05-2024 16:13

Be sure to get compensation for the missed appointment.

https://www.ofcom.org.uk/phones-telecoms-and-internet/advice-for-consumers/costs-and-billing/automat...
https://www.virginmedia.com/help/automatic-compensation
https://store.virginmedia.com/the-legal-stuff/terms-and-conditions-for-fibre-optic-services/automati...


--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & TNT sport), x3 V6 boxes (1 wired, 2 on WiFi), Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos

sullyzk
Joining in

on ‎23-05-2024 08:41

UPDATE 2: Engineer tuned up at 6 for what was meant to be a 12-4 appointment. To be fair, they're probably really busy and I can't be mad at them being overloaded. He asked me what had gone on I mentioned the PostRS errors and the sudden packet loss every 5-10 times a day and he said its likely you have a dodgy refurb Hub so he's swapped that for a brand new hub 5 and so far all seems to be working well. He did check all my cabling and he said that appears to be looking fine and theres no visible signs of damage in my house, to the cabinet. I have updated the thinkbroadband monitor to reflect the change and now only time will tell. I will check the logs in a few days to see whether the pre/post rs errors have gone away. All in all looks good. 

0 Kudos
Top