on 25-09-2023 20:52
Been with virgin broadband for a good 10 years. Been using a hub2 in modem mode and mown Asus Router.
got a new contract with VM and they supplied a new router due to speed increase. I originally set it up in modem mode and noticed we kept losing internet connection10-15 times a day turning everything off seemed to resolve it for a day but then occured again. Changed router to a TP link but similar thing happened.
Called support who basically wanted to take my router out the equation and turned the Hub 5 back to router mode for a few days which i did and things seemed ok for 6 days they Sunday afternoon got back home and no internet. power reset several times but not all devices would connect to the wifi. My iPhone could see the wifi SSID but when connecting just kept spinning. Xbox X would not connect to wired connection or wifi, iMac wouldn't connect over wifi, laptop hard wired to router would not connect etc.
When looking at the ifconfig my laptop was not being issued an IP Address, the xbox has a ip address of all 0.0.0.0 but the random flashes to an ip address i don't recognised 169.254.XX.XXX for about 0 seconds then jumps back to the 0.0.0.0 then al of a sudden the laptop connects and gains an IP address after about 1hr of not connecting via hard wire. Under no circumstances does the xbox connect so I used the hotspot on my phone to connect the xbox to the internet and it worked so i could rule out the xbox at fault.
Called support again tonight and they say can't see a problem with the router but there is an internet issue in the area but it just doesn't see right as to why it won't allocate an ip address correctly. they said they are going to monitor the internet to our house over the next 24hrs and see what happens but it seems more of a router issue to me.
could we connect the old hub 2 again to see if thats more stable?
Any advise or how do i progress this?
Thanks in advance
25-09-2023 21:26 - edited 25-09-2023 21:29
faulty hub or just that more downstream and upstream channels with the new hub are a problem not that it would cause the DHCP problem but the other problem.
at some point test modem mode with a PC no router if stable copy its MAC to your router
on 26-09-2023 07:29
This reads like another HUB 5 with a failed DHCP server.
on 26-09-2023 09:10
Well that is my thoughts on it - it’s so random how devices work or don’t work.
I do have a Sinologist NAS drive which can run as a DHCP server so could use this an an option but don’t really want to mess around.
I literally returned the TP link router Sunday morning so don’t have anything to switch back to modem mode
on 26-09-2023 09:27
If we are issued with a Hub 5 it will be operated in model mode from the off.
We just do not have the time / inclination to deal with ...
Hub 5 Router mode, current reported issues:
1. Wi-Fi & DHCP Fail when both SSIDs are changed. (in the Wizard and in the Menu)
2. Wi-Fi SSID changed in the setup Wizard reverts to factory settings after a few weeks.
3. DHCP Fails with multiple DHCP devices.
4. DHCP Reserved IP list may fail to accept entries.
5. DNS All queries are being intercepted by the Hub 5.
6. DNS Queries for AWS hosts time out with both VM DNS & Public DNS.
7. DNS DNSSEC queries fail.
8. Port Forwarding may not work.
9. RTSP stream / VRChat crashes & reboots Hub 5. (Sonos via Wi-Fi may be a trigger)
10. Wi-Fi 6 / 802.11ax Fails to be visible to many 2.4GHz only devices.
11. (Suspected) A laptop / mobile / tablet connected via 5GHz Wi-Fi may be unable to access a printer connected by 2.4GHz. May also mean mobile on 5GHz is unable to detect / manage IoTs on 2.4GHz.
on 26-09-2023 11:47
Funnily enough I did change the SSID on 2.4 and 5mhz wifi bands
on 27-09-2023 07:43
Can anyone who knows what they are looking at advise on any issues with the below?
Cable Modem StatusItem Status Comments
Acquired Downstream Channel(Hz) | 331000000 | Locked |
Ranged Upstream Channel(Hz) | 49600000 | Ranged |
Provisioning State | Online | Operational |
Downstream bonded channels
1 | 331000000 | 9.9 | 39 | QAM 256 | 25 |
2 | 139000000 | 8.1 | 38 | QAM 256 | 1 |
3 | 147000000 | 8.2 | 38 | QAM 256 | 2 |
4 | 155000000 | 8.2 | 38 | QAM 256 | 3 |
5 | 163000000 | 8.1 | 38 | QAM 256 | 4 |
6 | 171000000 | 8 | 38 | QAM 256 | 5 |
7 | 179000000 | 8 | 38 | QAM 256 | 6 |
8 | 187000000 | 8.1 | 38 | QAM 256 | 7 |
9 | 195000000 | 8.4 | 38 | QAM 256 | 8 |
10 | 203000000 | 8.3 | 38 | QAM 256 | 9 |
11 | 211000000 | 8.5 | 38 | QAM 256 | 10 |
12 | 219000000 | 8.6 | 39 | QAM 256 | 11 |
13 | 227000000 | 8.6 | 39 | QAM 256 | 12 |
14 | 235000000 | 8.8 | 39 | QAM 256 | 13 |
15 | 243000000 | 8.8 | 39 | QAM 256 | 14 |
16 | 251000000 | 8.8 | 39 | QAM 256 | 15 |
17 | 259000000 | 8.7 | 39 | QAM 256 | 16 |
18 | 267000000 | 8.6 | 39 | QAM 256 | 17 |
19 | 275000000 | 8.7 | 39 | QAM 256 | 18 |
20 | 283000000 | 8.9 | 39 | QAM 256 | 19 |
21 | 291000000 | 9.2 | 39 | QAM 256 | 20 |
22 | 299000000 | 9.4 | 39 | QAM 256 | 21 |
23 | 307000000 | 9.5 | 39 | QAM 256 | 22 |
24 | 315000000 | 9.7 | 39 | QAM 256 | 23 |
25 | 323000000 | 9.8 | 39 | QAM 256 | 24 |
26 | 339000000 | 10 | 39 | QAM 256 | 26 |
27 | 347000000 | 10.1 | 39 | QAM 256 | 27 |
28 | 355000000 | 10 | 40 | QAM 256 | 28 |
29 | 363000000 | 10.2 | 40 | QAM 256 | 29 |
30 | 371000000 | 10.4 | 40 | QAM 256 | 30 |
31 | 379000000 | 10.7 | 40 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 39 | 0 | 0 |
2 | Locked | 38 | 0 | 0 |
3 | Locked | 38 | 0 | 0 |
4 | Locked | 38 | 0 | 0 |
5 | Locked | 38 | 0 | 0 |
6 | Locked | 38 | 0 | 0 |
7 | Locked | 38 | 0 | 0 |
8 | Locked | 38 | 0 | 0 |
9 | Locked | 38 | 1 | 0 |
10 | Locked | 38 | 0 | 0 |
11 | Locked | 38 | 1 | 0 |
12 | Locked | 39 | 0 | 0 |
13 | Locked | 39 | 1 | 0 |
14 | Locked | 39 | 0 | 0 |
15 | Locked | 39 | 0 | 0 |
16 | Locked | 39 | 0 | 0 |
17 | Locked | 39 | 0 | 0 |
18 | Locked | 39 | 0 | 0 |
19 | Locked | 39 | 0 | 0 |
20 | Locked | 39 | 1 | 0 |
21 | Locked | 39 | 0 | 0 |
22 | Locked | 39 | 1 | 0 |
23 | Locked | 39 | 0 | 0 |
24 | Locked | 39 | 0 | 0 |
25 | Locked | 39 | 1 | 0 |
26 | Locked | 39 | 1 | 0 |
27 | Locked | 39 | 0 | 0 |
28 | Locked | 40 | 0 | 0 |
29 | Locked | 40 | 1 | 0 |
30 | Locked | 40 | 2 | 0 |
31 | Locked | 40 | 0 | 0 |
Upstream bonded channels
0 | 49600000 | 43.3 | 5120 | QAM 64 | 9 |
1 | 43100000 | 43 | 5120 | QAM 64 | 10 |
2 | 36600000 | 42.5 | 5120 | QAM 64 | 11 |
3 | 30100000 | 42.3 | 5120 | QAM 64 | 12 |
4 | 23600000 | 42.3 | 5120 | QAM 64 | 13 |
Upstream bonded channels
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 |
General Configuration
Allowed |
1 |
Enabled |
3.1 |
;kfoA,.iyewrkldJKDHSUBsgv |
Primary Downstream Service Flow
29502 |
575000085 bps |
42600bytes |
0 bps |
Primary Upstream Service Flow
26108 |
55000085 bps |
42600bytes |
0 bps |
42600bytes |
Best Effort |
Network Log
26-09-2023 21:37:00 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 21:37:00 | warning | Dynamic Range Window violation |
26-09-2023 20:29:27 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 20:29:27 | warning | Dynamic Range Window violation |
26-09-2023 18:18:59 | warning | Dynamic Range Window violation |
26-09-2023 18:18:59 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 13:52:53 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 13:52:45 | 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; |
26-09-2023 13:52:45 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 13:48:32 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 13:46:52 | warning | Dynamic Range Window violation |
26-09-2023 13:46:52 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 12:40:18 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
26-09-2023 12:40:18 | warning | Dynamic Range Window violation |
25-09-2023 21:13:07 | notice | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 709050; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:51 | warning | Unicast DSID PSN startup error |
25-09-2023 21:12:37 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:37 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:34 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
25-09-2023 21:12:28 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:28 | warning | Dynamic Range Window violation |
25-09-2023 21:12:27 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:27 | warning | Dynamic Range Window violation |
25-09-2023 21:12:27 | warning | Dynamic Range Window violation |
25-09-2023 21:12:27 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:27 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:27 | warning | Dynamic Range Window violation |
25-09-2023 21:12:27 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:27 | warning | Dynamic Range Window violation |
25-09-2023 21:12:27 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:27 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-09-2023 21:12:27 | warning | Dynamic Range Window violation |
27-09-2023 07:51 - edited 27-09-2023 07:52
This has been a problem for over a year and nobody seems to be admitting the issue for whatever reason.
I do have a fix that works for me, probably not "officially supported" but I disagree that the number of devices is too much for a isp provided router to handle. BT, and Sky's kit worked fine same number. Anyway here goes.
1. Wi-Fi Challenges:
A. WPA3: Whilst the hub allows selection of WPA3, in the source code "utilities.js" there is indeed only a mapping of WPA and WPA2 modes to the relevant security settings for the API to pickup. Hence, WPA3 mode seems to be a repeated failure. No surprise here given the coding.
Avoid using WPA3 as it will not work.
B. There is also an issue of "the disappearing Wi-Fi" - where some devices do not see the WiFi at all (e.g. my HP desktop) . Remedy seems to be setting wireless mode to 802.11b/g/n/ax from 802.11g/n/ax.
2. DHCP Challenges:
Whilst the hub can support 200+ devices per the DHCP range, the DHCP server seems to crash with more than 15 or so (approximate) devices connected. Remedy:
a. Allocate devices as reserved under http://192.168.0.1/?page=settings%2Fdhcp
Once you hit 32 it will say you can no longer add any more.
So delete one, meaning there are 31 reserved.
Then I used BURP suite (free download) to add the rest.
Once downloaded, go to Proxy - Intercept - and click Open Browser
Go to http://192.168.0.1/?page=settings%2Fdhcp
Add 1 more device, bringing your total to 32.#
Apply this.
In the BURP tool click on HTTP History and you will see there is one line item with a method "PUT" at URL /rest/v1/network/reservedipaddresses.
Right click it and send to repeater
Modify the MAC here to be the new devices MAC, and the IP to be the desired IP reservation.
Hit Send.
Refresh http://192.168.0.1/?page=settings%2Fdhcp - does it show the extra devices reserved above 32?
If so, keep going!
With this set, you can get 60+ devices working on the Hub 5 in router mode with no crashing. For homes with a large number of devices, this is the only way I have found to ensure stability.
I keep everything in the reservation excluding roaming stuff such as a friend visiting.
Good luck, I personally would struggle to buy an AX router myself right now. I have a rpi for something else and they are also a pretty penny due to stock limitations so I do not want to use one for DHCP.
on 27-09-2023 07:56
The Downstream Power Levels have some channels over the 10 dBmV maximum.
HUB Signal Level Checks
Via http://192.168.0.1/ connect to the Hub in Router mode, do not login in, scroll down to "Check router status" Use http://192.168.100.1/ for a Hub in Modem mode
Using the Hub's "Check router status" tabs check the Downstream and Upstream power levels are in spec.
Downstream Power Levels of -7 to +7 dBmV are preferred, +10dBmV is the max acceptable, with a SNR of 33dB or higher across all DOCSIS 3.0 channels. Rising error counts across many channels is a current service noise fault.
Upstream Power Levels of 35 to 49 dBmV are preferred, with QAM 64 Modulation mode across all four to six DOCSIS 3.0 channels. Seeing QAM 32/16 is a current service noise fault.
on 27-09-2023 08:06
+1 was editing my reply to say the same. Specifically these seem to be out of range:
26 | 339000000 | 10 | 39 | QAM 256 | 26 |
27 | 347000000 | 10.1 | 39 | QAM 256 | 27 |
28 | 355000000 | 10 | 40 | QAM 256 | 28 |
29 | 363000000 | 10.2 | 40 | QAM 256 | 29 |
30 | 371000000 | 10.4 | 40 | QAM 256 | 30 |
31 | 379000000 | 10.7 | 40 | QAM 256 | 31 |