on 09-08-2021 11:09
Because I am pretty consistently getting around 280-290Mbps. That's pretty fast and probably as fast as I need, but I was recently upsold the M500 package and it's really not going to be worth it for me if it's only slightly faster than what I was getting before.
Answered! Go to Answer
on 10-08-2021 06:58
Keep an eye on the post-RS errors. If those are increasing then you may have a problem that will affect speed, because each one is an ucorrectable data packet that is either discarded in a time-sensitive application like gaming or video calls, or re-requested for non time sensitive uses like speed tests or downloads. If discarded you see glitches, if re-requested it can hit speeds hard if there's enough of them.
Check the coax connections on the lead to the hub (and any port termination caps or other coax joints). All should be properly made and the securing nuts finger tight.
on 09-08-2021 11:59
On a 500 Mbps contract with a line that's working properly you should see a consistent speed around 530-548 Mbps (VM's expected speed range of 516-548 is usually pessimistic). You'll see those on a device connected via ethernet cable, on a wireless device things are a bit more complicated. For a high end wifi device close to the hub, connected to the 5 GHz band, you might get the full speed, although you'd probably need to check the 5 GHz channel width is set to 20/40/80. For many wifi devices they'll top out around 300 Mbps in real world situations.
on 09-08-2021 13:17
This is on a desktop computer that is connected by an ethernet cable to the Virgin Hub 3.0. It looks like I'm not getting the benefit of an M500 connection for some reason.
on 09-08-2021 13:59
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.
09-08-2021 14:10 - edited 09-08-2021 14:11
1 | 203000000 | 7.6 | 38 | 256 qam | 9 |
2 | 211000000 | 7.5 | 38 | 256 qam | 10 |
3 | 219000000 | 7.1 | 38 | 256 qam | 11 |
4 | 227000000 | 6.9 | 38 | 256 qam | 12 |
5 | 235000000 | 6.3 | 38 | 256 qam | 13 |
6 | 243000000 | 6 | 38 | 256 qam | 14 |
7 | 251000000 | 5.9 | 38 | 256 qam | 15 |
8 | 259000000 | 6 | 38 | 256 qam | 16 |
9 | 267000000 | 5.8 | 38 | 256 qam | 17 |
10 | 275000000 | 5.5 | 38 | 256 qam | 18 |
11 | 283000000 | 5 | 38 | 256 qam | 19 |
12 | 291000000 | 4.6 | 38 | 256 qam | 20 |
13 | 299000000 | 5 | 38 | 256 qam | 21 |
14 | 307000000 | 5.6 | 38 | 256 qam | 22 |
15 | 315000000 | 5.9 | 38 | 256 qam | 23 |
16 | 323000000 | 6.1 | 38 | 256 qam | 24 |
17 | 331000000 | 6.3 | 38 | 256 qam | 25 |
18 | 339000000 | 6.5 | 38 | 256 qam | 26 |
19 | 347000000 | 6.5 | 38 | 256 qam | 27 |
20 | 355000000 | 6.3 | 38 | 256 qam | 28 |
21 | 363000000 | 6.1 | 38 | 256 qam | 29 |
22 | 371000000 | 6.1 | 38 | 256 qam | 30 |
23 | 379000000 | 6.3 | 38 | 256 qam | 31 |
24 | 387000000 | 6.3 | 38 | 256 qam | 32 |
1 | Locked | 38.9 | 418 | 1 |
2 | Locked | 38.6 | 986 | 86 |
3 | Locked | 38.9 | 452 | 22 |
4 | Locked | 38.6 | 615 | 121 |
5 | Locked | 38.6 | 961 | 292 |
6 | Locked | 38.6 | 905 | 283 |
7 | Locked | 38.9 | 1065 | 52 |
8 | Locked | 38.9 | 762 | 8 |
9 | Locked | 38.9 | 571 | 229 |
10 | Locked | 38.6 | 649 | 262 |
11 | Locked | 38.9 | 665 | 110 |
12 | Locked | 38.6 | 866 | 338 |
13 | Locked | 38.6 | 860 | 339 |
14 | Locked | 38.6 | 894 | 141 |
15 | Locked | 38.9 | 655 | 253 |
16 | Locked | 38.9 | 726 | 200 |
17 | Locked | 38.9 | 690 | 16 |
18 | Locked | 38.9 | 471 | 13 |
19 | Locked | 38.9 | 532 | 15 |
20 | Locked | 38.6 | 381 | 0 |
21 | Locked | 38.9 | 472 | 14 |
22 | Locked | 38.6 | 378 | 0 |
23 | Locked | 38.9 | 328 | 0 |
24 | Locked | 38.9 | 394 | 17 |
on 09-08-2021 14:11
1 | 53700068 | 43.3 | 5120 | 64 qam | 2 |
2 | 46199957 | 42.5 | 5120 | 64 qam | 3 |
3 | 39399971 | 42.8 | 5120 | 64 qam | 4 |
4 | 60299917 | 43.8 | 5120 | 64 qam | 1 |
1 | ATDMA | 0 | 0 | 5 | 0 |
2 | ATDMA | 0 | 0 | 3 | 0 |
3 | ATDMA | 0 | 0 | 3 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
on 09-08-2021 14:12
09/08/2021 11:16:30 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 11:16:22 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 10:45:57 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 04:04:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/08/2021 10:39:31 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/08/2021 20:38:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/08/2021 22:39:31 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/08/2021 12:27:13 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/08/2021 10:39:31 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/07/2021 16:39:9 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/07/2021 01:33:10 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/07/2021 06:45:53 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 14:47:25 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 14:47:25 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 19:34:22 | 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 23:23:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/07/2021 21:41:5 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/07/2021 16:53:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 09-08-2021 14:14
on 09-08-2021 14:29
My daughter has an unhappy habit of reaching out with her feet and accidentally switching off the router at the plugboard, so it has been rebooted fairly recently. And it was of course rebooted when Virgin managed to persuade me to "upgrade" to M500 three weeks ago.
I can always reboot again, if that will make a difference, of course.
on 09-08-2021 14:57