Upgraded to Gig1 from M350 slow speeds

[mauley]

I upgraded to Gig1 Fibre from M350 recently and got given a new Hub5 router to replace my Hub3. With Hub3 and M350 I was maxing out my connection over WiFi with the stock Hub3 in modem mode and a Netgear R6260 router for Wifi. Without that Netgar router I was not getting good WiFi throughout my house.

I upgraded to Gig1 and was getting around 450 - 500mbps with the Hub5 but thought this should be faster. I bought an Asus ZenWifi XT8 and put the Hub5 in router mode. Still, I am only getting the same speed.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	306000000	10.1	42	QAM 256	22
2	138000000	9.7	41	QAM 256	1
3	146000000	9.7	41	QAM 256	2
4	154000000	9.6	41	QAM 256	3
5	162000000	9.5	41	QAM 256	4
6	170000000	9.5	41	QAM 256	5
7	178000000	9.4	42	QAM 256	6
8	186000000	9.6	42	QAM 256	7
9	194000000	9.7	42	QAM 256	8
10	202000000	10	42	QAM 256	9
11	210000000	10	42	QAM 256	10
12	218000000	10.2	42	QAM 256	11
13	226000000	10	42	QAM 256	12
14	234000000	10.3	42	QAM 256	13
15	242000000	10.1	42	QAM 256	14
16	250000000	10.2	42	QAM 256	15
17	258000000	10.2	42	QAM 256	16
18	266000000	10.2	42	QAM 256	17
19	274000000	10.3	42	QAM 256	18
20	282000000	10.1	42	QAM 256	19
21	290000000	10.4	42	QAM 256	20
22	298000000	10.1	42	QAM 256	21
23	314000000	9.9	41	QAM 256	23
24	322000000	9.8	41	QAM 256	24
25	330000000	9.9	41	QAM 256	25
26	338000000	9.9	41	QAM 256	26
27	346000000	9.9	42	QAM 256	27
28	354000000	9.6	42	QAM 256	28
29	362000000	9.9	42	QAM 256	29
30	370000000	9.4	42	QAM 256	30
31	378000000	9.6	42	QAM 256	31

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	42	0	0
2	Locked	41	0	0
3	Locked	41	0	0
4	Locked	41	0	0
5	Locked	41	0	0
6	Locked	41	0	0
7	Locked	42	0	0
8	Locked	42	0	0
9	Locked	42	0	0
10	Locked	42	0	0
11	Locked	42	0	0
12	Locked	42	0	0
13	Locked	42	0	0
14	Locked	42	0	0
15	Locked	42	0	0
16	Locked	42	0	0
17	Locked	42	0	0
18	Locked	42	0	0
19	Locked	42	0	0
20	Locked	42	0	0
21	Locked	42	0	0
22	Locked	42	0	0
23	Locked	41	0	0
24	Locked	41	0	0
25	Locked	41	0	0
26	Locked	41	0	0
27	Locked	42	0	0
28	Locked	42	0	0
29	Locked	42	0	0
30	Locked	42	0	0
31	Locked	42	0	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

0	49600000	42.8	5120	QAM 64	1
1	43100000	42.8	5120	QAM 64	2
2	36600000	42.8	5120	QAM 64	3
3	30100000	42.8	5120	QAM 64	4
4	23600000	42.5	5120	QAM 64	9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

3

Enabled

3.1

cmreg-vmdg660-bbt076+voc-b.cm

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

110298

1200000450 bps

42600bytes

0 bps

110300

128000 bps

3044bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

110297

55000270 bps

42600bytes

0 bps

42600bytes

Best Effort

110299

128000 bps

3044bytes

0 bps

1522bytes

Best Effort

Network Log

Time Priority Description

03-12-2022 23:03:11	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:56	critical	DHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:56	notice	REGISTRATION COMPLETE - Waiting for Operational status
03-12-2022 23:02:55	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:52	notice	US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:48	critical	DHCP FAILED - Critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:46	notice	DS 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;
03-12-2022 23:02:43	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:40	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:38	notice	Honoring MDD; IP provisioning mode = IPv4
03-12-2022 23:02:22	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:17	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 23:02:04	critical	Cable Modem Reboot due to master console reset
03-12-2022 23:02:04	critical	Cable Modem Reboot due to master console reset
03-12-2022 23:02:04	critical	Cable Modem Reboot due to master console reset
03-12-2022 22:53:50	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:53:16	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:52:27	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:52:21	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:35	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:33	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:30	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:30	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:29	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:27	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:23	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:20	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:20	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
03-12-2022 22:48:19	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-12-2022 20:28:35	critical	Cable Modem Reboot from SNMP

[jb66]

Have you checked to see if the thing your doing the test with is capable of faster WiFi speeds?

[mauley]

Yes, my computer has an Intel AX WiFi 6 AX201 card which is capable of 2.4gbps

[jb66]

I think you need to take it back to basics and run a wired speedtest to rule the VM network out being the bottleneck.  The fact the hub 5 and the router you've purchased have made no difference tells me its not the WiFi transmitting that's the issue, it's either the feed in, the speedtest site your using or your own equipment receiving the data that is the bottleneck.

Anyone in your household got a decent smartphone like a s22 ultra to visit fast.com?

[mauley]

I just ordered an ethernet dongle and a cat8 cable so I can test from my Macbook Pro but it won't arrive until tomorrow. Bit a slog bringing my computer downstairs you see.

In the meantime, I ran that test from fast.com from my Pixel 7 Pro 3 times, which I know has Wifi 6E capability and got the following;

Test 1 - 770mbps

Test 2 - 660mbps

Test 3 - 620mbps

So higher than when I ran from speedtest.net. I only have 3 devices on the network and was not strewaming anything at the time.

[jb66]

The only other test you can do if you don't have a wired capability at the moment is 

https://www.samknows.com/realspeed/

With the hub 5 in router mode

[mauley]

[mauley]

This can be closed as there is no issue with the VM service

[Chris_W1]

Hi mauley, thanks for the message and welcome back to the forums. 

I am happy to hear that things have become resolved and do let us know if anything changes? 

Have a good weekend. 

Chris.