cancel
Showing results for 
Search instead for 
Did you mean: 

Hub 5 seems to not allocate IP Address

Gooders77
Tuning in

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

14 REPLIES 14

legacy1
Alessandro Volta

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 

---------------------------------------------------------------

Client62
Legend

This reads like another HUB 5 with a failed DHCP server.

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 

Client62
Legend

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.

Funnily enough I did change the SSID on 2.4 and 5mhz wifi bands

Gooders77
Tuning in

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)331000000Locked
Ranged Upstream Channel(Hz)49600000Ranged
Provisioning StateOnline

Operational

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000009.939QAM 25625
21390000008.138QAM 2561
31470000008.238QAM 2562
41550000008.238QAM 2563
51630000008.138QAM 2564
6171000000838QAM 2565
7179000000838QAM 2566
81870000008.138QAM 2567
91950000008.438QAM 2568
102030000008.338QAM 2569
112110000008.538QAM 25610
122190000008.639QAM 25611
132270000008.639QAM 25612
142350000008.839QAM 25613
152430000008.839QAM 25614
162510000008.839QAM 25615
172590000008.739QAM 25616
182670000008.639QAM 25617
192750000008.739QAM 25618
202830000008.939QAM 25619
212910000009.239QAM 25620
222990000009.439QAM 25621
233070000009.539QAM 25622
243150000009.739QAM 25623
253230000009.839QAM 25624
263390000001039QAM 25626
2734700000010.139QAM 25627
283550000001040QAM 25628
2936300000010.240QAM 25629
3037100000010.440QAM 25630
3137900000010.740QAM 25631

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked3900
2Locked3800
3Locked3800
4Locked3800
5Locked3800
6Locked3800
7Locked3800
8Locked3800
9Locked3810
10Locked3800
11Locked3810
12Locked3900
13Locked3910
14Locked3900
15Locked3900
16Locked3900
17Locked3900
18Locked3900
19Locked3900
20Locked3910
21Locked3900
22Locked3910
23Locked3900
24Locked3900
25Locked3910
26Locked3910
27Locked3900
28Locked4000
29Locked4010
30Locked4020
31Locked4000
 
 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000043.35120QAM 649
143100000435120QAM 6410
23660000042.55120QAM 6411
33010000042.35120QAM 6412
42360000042.35120QAM 6413

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
 
 

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
Allowed
1
Enabled
3.1
;kfoA,.iyewrkldJKDHSUBsgv

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
29502
575000085 bps
42600bytes
0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
26108
55000085 bps
42600bytes
0 bps
42600bytes
Best Effort

 

Network Log

Time Priority Description
26-09-2023 21:37:00warningRNG-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:00warningDynamic Range Window violation
26-09-2023 20:29:27warningRNG-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:27warningDynamic Range Window violation
26-09-2023 18:18:59warningDynamic Range Window violation
26-09-2023 18:18:59warningRNG-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:53warningDBC-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:45critical16 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:45criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-09-2023 13:48:32criticalStarted 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:52warningDynamic Range Window violation
26-09-2023 13:46:52warningRNG-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:18warningRNG-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:18warningDynamic Range Window violation
25-09-2023 21:13:07noticeCM-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:51warningUnicast DSID PSN startup error
25-09-2023 21:12:37warningDBC-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:37noticeUS 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:34noticeREGISTRATION COMPLETE - Waiting for Operational status
25-09-2023 21:12:28warningRNG-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:28warningDynamic Range Window violation
25-09-2023 21:12:27warningRNG-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:27warningDynamic Range Window violation
25-09-2023 21:12:27warningDynamic Range Window violation
25-09-2023 21:12:27warningRNG-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:27warningRNG-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:27warningDynamic Range Window violation
25-09-2023 21:12:27warningRNG-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:27warningDynamic Range Window violation
25-09-2023 21:12:27warningRNG-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:27warningREG-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:27warningDynamic Range Window violation

 

jk1990
Dialled in

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 

1.jpg

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.

2.jpg
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.

3.jpg

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. 

Client62
Legend

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.

+1 was editing my reply to say the same. Specifically these seem to be out of range:

263390000001039QAM 25626
2734700000010.139QAM 25627
283550000001040QAM 25628
2936300000010.240QAM 25629
3037100000010.440QAM 25630
3137900000010.740QAM 25631