I upgraded to the 200mb VM package around 2 months ago and have been experiencing unplayable lag online.
My PS is hardwired. I have checked if there are capacity issues on the network e.g any rogue devices. I've also check cabling and completed resets on the router. No joy.
I'm getting some errors in the logs which look to be something with the DHCP server.
Time Priority Description
| 12/04/2020 22:36:26 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 12/04/2020 22:35:30 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 12/04/2020 10:09:2 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 11/04/2020 21:40:42 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxl20016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 11/04/2020 21:40:42 | Error | DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 11/04/2020 14:27:17 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 11/04/2020 08:06:52 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 10/04/2020 16:47:10 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 06/04/2020 06:51:12 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxl20016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 06/04/2020 06:51:12 | Error | DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 06/04/2020 06:11:49 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 06/04/2020 05:45:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 05/04/2020 09:52:16 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 02/04/2020 08:48:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 02/04/2020 04:56:20 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxl20016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 02/04/2020 04:56:20 | Error | DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 31/03/2020 22:55:2 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 29/03/2020 20:57:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 27/03/2020 08:50:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxl20016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
| 27/03/2020 08:50:29 | Error | DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Downstream:
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
| 1 | 315000000 | 8.5 | 40 | 256 qam | 23 |
| 2 | 139000000 | 7.5 | 40 | 256 qam | 1 |
| 3 | 147000000 | 7.4 | 40 | 256 qam | 2 |
| 4 | 155000000 | 7.6 | 40 | 256 qam | 3 |
| 5 | 163000000 | 8 | 40 | 256 qam | 4 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
| 1 | 39400000 | 3.9 | 5120 | 64 qam | 4 |
| 2 | 46199991 | 3.9 | 5120 | 64 qam | 3 |
| 3 | 53700014 | 4.05 | 5120 | 64 qam | 2 |
| 4 | 60300031 | 4.1 | 5120 | 64 qam | 1 |
Ping test:
PING 192.168.0.1 (192.168.0.1): 64 data bytes
72 bytes from 192.168.0.1: seq=0 ttl=64 time=110.000 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 1 packets received, 66% packet loss
round-trip min/avg/max = 110.000/110.000/110.000 ms
My ping test is showing 66% packet which is literally insane and everyone I have spoken to has agreed this makes my internet unusable.
Can anyone give me some advice on how to fix this?
I could try getting a better router as I know the superhub 3 has chip issues, not sure this will help if its virgin servers or something?
