cancel
Showing results for 
Search instead for 
Did you mean: 

Hub 5 ethernet ports dropped out (router mode) but WiFi fine

inf
On our wavelength

I just wanted to share my experience with a new Hub 5 that arrived six days ago.

Modifications made: changed wifi SSID and password, turned off wifi smart optimisation and manually set wifi channels, turned off DHCP (because I use Pi-Hole), added one port forward.

Everything has been rock solid for those six days, downloading at 940 MBps and uploading over 100 MBps consistently. Pings have been lower compared to the Hub 4 as well.

Then tonight at 19:45 every ethernet connection broke. All devices reported "media disconnected". Unplugging, replugging made no difference. I rebooted the ethernet devices (Windows 10 PCs, Raspberry Pis, XBox, smart TV) but none would connect. I set a static IP on my phone and it connected to the WiFi and internet fine.

The Hub 5 could ping all WiFi devices, but none via ethernet. I tried swapping cables and ports, but no combinations worked.

Finally at my wits end after an hour of debugging I did a factory reset. This solved the issue - ethernet devices appeared connected again. So to me this is clearly a software issue, not a hardware one.

It's taken 2 hours to get back to normal, which is not how I'd planned to spend my evening. I hope this cautionary tale is a helpful datapoint to people looking at the forums when their Hub 5 suddenly refuses to make ethernet connections.

3 REPLIES 3

inf
On our wavelength

As an addition to my post above, here are the network stats. They look worrying, but the internet seems fine. Maybe someone with experience can tell me if I should be worried or not - or if they could possibly cause an ethernet malfunction.

 

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159944K1840QAM 40961108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
159Locked40-2.8642973440

 

Network Log

Time Priority Description
24-10-2023 20:51:30warningDBC-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;
24-10-2023 20:51:30noticeUS 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;
24-10-2023 20:51:25noticeREGISTRATION COMPLETE - Waiting for Operational status
24-10-2023 20:51:19warningRNG-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;
24-10-2023 20:51:19warningREG-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;
24-10-2023 20:51:19warningDynamic Range Window violation
24-10-2023 20:51:19warningRNG-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;
24-10-2023 20:51:19warningDynamic Range Window violation
24-10-2023 20:51:19warningDynamic Range Window violation
24-10-2023 20:51:19warningRNG-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;
24-10-2023 20:51:19warningDynamic Range Window violation
24-10-2023 20:51:19warningRNG-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;
24-10-2023 20:51:14noticeDS 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;
24-10-2023 20:51:06warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-10-2023 20:51:04noticeHonoring MDD; IP provisioning mode = IPv4
24-10-2023 20:50:53criticalCable Modem Reboot because of - Reboot Timezone Change
24-10-2023 20:50:53criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-10-2023 20:47:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-10-2023 20:47:44criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-10-2023 20:47:43criticalCable Modem Reboot because of - Reboot Factory reset UI

TableTop
Up to speed

No the network stats you have posted are all fine, but, they only are concerned with the cable connection itself, they don’t register anything to do with ‘your’ side of the connection, ie WiFi or Ethernet.

OK, you’ve had the equivalent of the good old ‘turn it off and on again’ scenario - sometimes odd stuff does just happen.

But if this occurs too often, then it would hint at faulty hardware and the hub would need to be replaced.

Client62
Hero

Changing both SSID on a Hub 5 has very problematic for customers with the issues varying from the Hub 5 Wi-Fi quickly failing to the Hub needing to be replaced.   I suspect you will end up with the Hub 5 in Modem mode as the only way to have a stable system.