on 01-08-2021 22:56
For the last month approximately, using WiFi will randomly dump the download speed from between 180 - 220 mbps down to below 20mbps, as far as single figures. This tends to be temporary and returns in about 10 seconds. I've tried everything in the book now, including the following:
- rebooting the router
- factory resetting the router
- manually choosing the wifi channels (multiple channels tested)
It's a Virgin Media 3 Hub, has stayed in the same location for 3 years, with nothing new changing in the last few months in terms of connections. Wired connection seems to be fine. Has anyone had this before? Is the WiFi dying on the router?
Thanks
Answered! Go to Answer
on 02-08-2021 11:50
Power levels look OK, there's a few downstream breakthrough post-RS (uncorrectable) errors, although significance varies depending on the time since the hub was last rebooted (?), and the upstream may have too many T3 timeouts. A few of these are normal for a cable connection, at perhaps one T3 every couple of days, and a handful of post-RS errors in the same timescale. If you're seeing more of these timeouts and post-RS errors then that points to a noisy connection that may require a technician to attend and check things out. My hub has broadly similar timeout and post-RS errors as your figures, but that's after thirteen days up time. If your data is from (say) ten days run time, then there's probably not too much to worry about on the cable side, and then focus turns to the wifi.
There's been a few oddities recently reported with some user's hub wifi, possibly due to firmware revisions. If previously you've found the hub's wifi OK, you might want to wait and see both what staff advise in response to your post, and whether the possible firmware issues are fixed. If you've had other wifi issues (coverage, reliability, speed) then you might want to start thinking about investing in your own router or mesh wifi.
on 01-08-2021 23:28
@minority-ky wrote:Is the WiFi dying on the router?
Yes but a new hub will have the same problem at some point just a better way is get your own wireless router with 1Gb ports and use hub in modem mode.
on 02-08-2021 06:44
It could be a wifi issue, but before concluding that you should exclude the possibility that it is a broadband problem.
Connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time. Then we can check for any obvious problems with power, noise or error counts.
on 02-08-2021 11:06
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | -1 | 40 | 256 qam | 25 |
2 | 203000000 | -0.2 | 40 | 256 qam | 9 |
3 | 211000000 | -0.7 | 40 | 256 qam | 10 |
4 | 219000000 | -0.7 | 40 | 256 qam | 11 |
5 | 227000000 | -1 | 40 | 256 qam | 12 |
6 | 235000000 | -1.2 | 40 | 256 qam | 13 |
7 | 243000000 | -1.2 | 40 | 256 qam | 14 |
8 | 251000000 | -1 | 40 | 256 qam | 15 |
9 | 259000000 | -0.5 | 40 | 256 qam | 16 |
10 | 267000000 | -0.2 | 40 | 256 qam | 17 |
11 | 275000000 | -0.2 | 40 | 256 qam | 18 |
12 | 283000000 | -0.2 | 40 | 256 qam | 19 |
13 | 291000000 | -0.4 | 40 | 256 qam | 20 |
14 | 299000000 | 0 | 40 | 256 qam | 21 |
15 | 307000000 | -0.4 | 40 | 256 qam | 22 |
16 | 315000000 | -0.5 | 40 | 256 qam | 23 |
17 | 323000000 | -0.7 | 40 | 256 qam | 24 |
18 | 339000000 | -0.9 | 40 | 256 qam | 26 |
19 | 347000000 | -1.2 | 40 | 256 qam | 27 |
20 | 355000000 | -1.2 | 40 | 256 qam | 28 |
21 | 363000000 | -1.5 | 40 | 256 qam | 29 |
22 | 371000000 | -1.5 | 40 | 256 qam | 30 |
23 | 379000000 | -1.4 | 40 | 256 qam | 31 |
24 | 387000000 | -1.7 | 40 | 256 qam | 32 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.9 | 105 | 0 |
2 | Locked | 40.9 | 195 | 0 |
3 | Locked | 40.9 | 209 | 0 |
4 | Locked | 40.9 | 270 | 0 |
5 | Locked | 40.3 | 194 | 0 |
6 | Locked | 40.9 | 165 | 0 |
7 | Locked | 40.9 | 157 | 4 |
8 | Locked | 40.9 | 169 | 14 |
9 | Locked | 40.9 | 240 | 0 |
10 | Locked | 40.9 | 162 | 0 |
11 | Locked | 40.9 | 131 | 0 |
12 | Locked | 40.9 | 120 | 0 |
13 | Locked | 40.9 | 198 | 0 |
14 | Locked | 40.9 | 193 | 0 |
15 | Locked | 40.9 | 132 | 0 |
16 | Locked | 40.9 | 151 | 0 |
17 | Locked | 40.3 | 171 | 0 |
18 | Locked | 40.9 | 162 | 0 |
19 | Locked | 40.9 | 182 | 0 |
20 | Locked | 40.9 | 172 | 12 |
21 | Locked | 40.9 | 138 | 0 |
22 | Locked | 40.3 | 157 | 0 |
23 | Locked | 40.9 | 137 | 0 |
24 | Locked | 40.3 | 121 | 0 |
on 02-08-2021 11:07
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 44.8 | 5120 | 64 qam | 2 |
2 | 39400000 | 43.3 | 5120 | 64 qam | 4 |
3 | 46200000 | 44.8 | 5120 | 64 qam | 3 |
4 | 60300000 | 44.8 | 5120 | 64 qam | 1 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 7 | 0 |
2 | ATDMA | 0 | 0 | 4 | 0 |
3 | ATDMA | 0 | 0 | 5 | 0 |
4 | ATDMA | 0 | 0 | 7 | 0 |
on 02-08-2021 11:07
Network Log
Time Priority Description
02/08/2021 09:58:47 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/08/2021 06:38:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/08/2021 21:25:17 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/08/2021 21:23:5 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/07/2021 14:52:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/07/2021 06:00:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/07/2021 06:00:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/07/2021 08:06:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/07/2021 18:00:14 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/07/2021 18:00:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/07/2021 18:04:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 06:00:14 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 06:00:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 19:08:52 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 18:00:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 18:00:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/07/2021 16:50:58 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/07/2021 06:33:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/07/2021 06:00:13 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/07/2021 06:00:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 02-08-2021 11:50
Power levels look OK, there's a few downstream breakthrough post-RS (uncorrectable) errors, although significance varies depending on the time since the hub was last rebooted (?), and the upstream may have too many T3 timeouts. A few of these are normal for a cable connection, at perhaps one T3 every couple of days, and a handful of post-RS errors in the same timescale. If you're seeing more of these timeouts and post-RS errors then that points to a noisy connection that may require a technician to attend and check things out. My hub has broadly similar timeout and post-RS errors as your figures, but that's after thirteen days up time. If your data is from (say) ten days run time, then there's probably not too much to worry about on the cable side, and then focus turns to the wifi.
There's been a few oddities recently reported with some user's hub wifi, possibly due to firmware revisions. If previously you've found the hub's wifi OK, you might want to wait and see both what staff advise in response to your post, and whether the possible firmware issues are fixed. If you've had other wifi issues (coverage, reliability, speed) then you might want to start thinking about investing in your own router or mesh wifi.
on 04-08-2021 09:18
Hi minority-ky,
Thanks for posting and sorry to hear you've some connection issues.
I've been able to locate your account using your forum details, everything looks to be within the specifications we would expect.
Are you able to log into the hub settings to advise if the SSIDS match? If not can you ensure they do.
Alex_Rm
on 08-08-2021 23:48
on 09-08-2021 15:48