on 10-12-2023 19:59
Hi All;
I am on M350 fibre and have the Hub 3.0 which is in Modem Mode and I have an ASUS RT-AX82U Wi-Fi 6 gaming router acting as my Wi-Fi / cable router for all household appliances. This works great although was still having bouts of slow / intermittent drops in internet at times. I am a gamer and have no issues with cable or Wi-Fi gaming until recently. I play Day-Z and when on the server loading screen it absolutely kills the internet, dropping a speed test to 1.15Mbps down and a few Mbps up (until I stop server refreshes). It settles when I join an actual game. This is the only game doing this?
Anyway, on looking at the Hub 3.0 I am getting these errors on the log:
No Ranging Response received - T3 time-out; CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
I have also noted when doing a trace-rt in CMD it drops the 3rd, 5th route (hits my router immediately, then the Hub and dies when out, re-establishes and then drops around 7 or 8th trace-rt path.
I have noted, also mainly in DayZ I have lag and dropped connections for moments. I am wondering if my router or the line is faulty? I quite regularly have to restart the Hub 3.0.
I don't understand why this specific issue with this game as it was fine for years. I am sure its probably something they have updated however with the sporadic issues with connection throughout the house (solid Wi-Fi connections) I am wondering if router / line? I carried out speed tests with the server loader in DayZ and in Task Manager it only showed 0.1 Mbps usage however I couldn't even run a speed test 80% of the time (when I could Edge showed the speed rate) - very strange.
I removed the Forward Path Equaliser from back of router to test and things have improved - Jitter varies from 0.6 to 10, however mostly around 0.6 - 3.6 with this device removed. Router still has the errors. I have never liked the Hub 3.0. Should I request a new router or engineer to check line? I have just asked for an upgrade to 500Mbps fibre through my account upgrades.
on 10-12-2023 22:30
Ignore the tracert problem, it’s just routers not processing ICMP datagrams. Please post full set of stats as per:
How to get stats from a VM hub (no need to logon to the hub)
Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode
on 11-12-2023 14:41
Are you somewhere near Notts or Lincoln?
There are problems with VM since yesterday. And not only for me.
Intermittent connection.
Dropping for few secs few times a minute.
on 11-12-2023 16:35
We can only expect a Public DNS to always respond to nslookup
Try this, the packet loss test is intended for the purpose : https://speed.cloudflare.com/
on 11-12-2023 17:36
Why if your circuit is so poor are you upgrading to a higher speed? You really need to get it sorted first. Get a BQM up and running soonest. www.thinkbroadband.com/ping
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 12-12-2023 11:50
Hi there, I will get this posted on Friday when I return home. Thanks for your reply
on 12-12-2023 11:50
Hi there,
No I’m up in Scotland
on 12-12-2023 11:51
Hi there,
I guessnim clutching at straws lol. What is a BQM?
Thanks
on 14-12-2023 13:08
Hi @T3nshipb,
Thank you for your posts and welcome to our community forums. We're here to help.
I'm so sorry to hear that you're having a little bit of trouble with your broadband connection recently. Are these ongoing today? If so, are you able to provide the hub stats and also a live BQM as requested as that'll show your connection quality in real-time for us?
To answer your other question, a BQM is essentially a graph that displays your connection quality and can help to identify certain issues. You'll find more information on what they do, display, and how to set one up here.
Keep us posted.
Thanks,
on 15-12-2023 15:37
Hi There
Please find below the Virgin Hub 3.0 network logs:
5/12/2023 15:02:57 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/12/2023 14:55:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/12/2023 09:19:32 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/12/2023 15:33:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/12/2023 19:36:0 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/12/2023 01:13:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/12/2023 21:19:31 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2023 07:00:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/12/2023 23:32:45 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/12/2023 22:32:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/12/2023 21:33:22 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/12/2023 20:08:15 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/12/2023 17:01:30 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/12/2023 06:06:18 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/11/2023 01:48:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/11/2023 18:06:18 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/11/2023 09:32:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/11/2023 15:26:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/11/2023 14:05:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/11/2023 07:46:27 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
|