on 06-07-2022 08:43
Due to simply not having the will or strength to do so, I gave up contacting VM, as they have made it clear they do not care and will not help me.
Now, it is intolerable. Constant disconnections and endless, continuous, relentless ping spikes.
I know you won't do anything, and I am not gonna play the 'Send an Engineer' game. I just need a statement from VM that they have done all they can/are willing to, so I can get a deadlock letter and get away form this criminally arrogant and malicious company.
So: Here is my BQM and the crap from the router. Have at it.
-----------------------
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 2.2 | 37 | 256 qam | 25 |
2 | 203000000 | 4.8 | 37 | 256 qam | 9 |
3 | 211000000 | 4.5 | 37 | 256 qam | 10 |
4 | 219000000 | 4 | 37 | 256 qam | 11 |
5 | 227000000 | 4 | 37 | 256 qam | 12 |
6 | 235000000 | 3.7 | 37 | 256 qam | 13 |
7 | 243000000 | 3.2 | 37 | 256 qam | 14 |
8 | 251000000 | 3 | 37 | 256 qam | 15 |
9 | 259000000 | 3.2 | 37 | 256 qam | 16 |
10 | 267000000 | 2.7 | 37 | 256 qam | 17 |
11 | 275000000 | 3 | 37 | 256 qam | 18 |
12 | 283000000 | 3 | 37 | 256 qam | 19 |
13 | 291000000 | 2.4 | 37 | 256 qam | 20 |
14 | 299000000 | 1.7 | 36 | 256 qam | 21 |
15 | 307000000 | 2.2 | 37 | 256 qam | 22 |
16 | 315000000 | 2.2 | 37 | 256 qam | 23 |
17 | 323000000 | 1.7 | 37 | 256 qam | 24 |
18 | 339000000 | 2 | 36 | 256 qam | 26 |
19 | 347000000 | 1.5 | 37 | 256 qam | 27 |
20 | 355000000 | 1.2 | 37 | 256 qam | 28 |
21 | 363000000 | 2 | 37 | 256 qam | 29 |
22 | 371000000 | 2.2 | 37 | 256 qam | 30 |
23 | 379000000 | 2.2 | 37 | 256 qam | 31 |
24 | 387000000 | 2 | 37 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.3 | 8 | 0 |
2 | Locked | 37.3 | 19 | 0 |
3 | Locked | 37.3 | 5 | 0 |
4 | Locked | 37.3 | 5 | 0 |
5 | Locked | 37.3 | 5 | 0 |
6 | Locked | 37.3 | 9 | 0 |
7 | Locked | 37.6 | 2 | 0 |
8 | Locked | 37.3 | 9 | 0 |
9 | Locked | 37.6 | 6 | 0 |
10 | Locked | 37.3 | 5 | 0 |
11 | Locked | 37.3 | 7 | 0 |
12 | Locked | 37.3 | 7 | 0 |
13 | Locked | 37.6 | 8 | 0 |
14 | Locked | 36.3 | 10 | 0 |
15 | Locked | 37.3 | 6 | 0 |
16 | Locked | 37.3 | 12 | 0 |
17 | Locked | 37.3 | 9 | 0 |
18 | Locked | 36.6 | 11 | 0 |
19 | Locked | 37.6 | 5 | 0 |
20 | Locked | 37.3 | 4 | 0 |
21 | Locked | 37.6 | 5 | 0 |
22 | Locked | 37.6 | 6 | 0 |
23 | Locked | 37.6 | 3 | 0 |
24 | Locked | 37.6 | 2 | 0 |
----------
TimePriorityDescription05/07/2022 16:27:17noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;05/07/2022 15:47:28noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;05/07/2022 15:47:27ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;04/07/2022 05:38:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;03/07/2022 18:47:30noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/07/2022 19:32:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/07/2022 19:32:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/07/2022 19:32:24ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;28/06/2022 01:59:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;28/06/2022 00:02:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;28/06/2022 00:02:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;24/06/2022 22:24:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;24/06/2022 12:02:25noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;24/06/2022 12:02:25ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;21/06/2022 17:18:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;21/06/2022 15:14:12noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;21/06/2022 15:14:12ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;17/06/2022 03:32:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;16/06/2022 19:50:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;16/06/2022 19:50:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Answered! Go to Answer
on 08-07-2022 12:52
So, in the spirit of 'I have no other god damn choice', I disconnected my gigabit switch, my Pi and my NAS. I removed ALL wiring, and connected just my PC via a brand new CAT5e (well, mac and phone on wifi, but I don't care about that)
Service shows exactly zero improvement, and if anything, is actually a fair bit worse.
So, it's not me (which I already knew), it is not the cabling, Router or wall sockets from VM (all were replaced very recently) and there is no 'work' (giggle!) being carried out by VM.
So, in short, I am screwed. My service is unusable for its main purpose, but VM simply have no interest in doing anything, as it would require them doing their job and being competent.
Another VM customer, stuck with **bleep** service until I leave, with no chance of respite.
How is this company still operating? They were a degenerate bag or lying morons when I worked for them, 2 decades ago, and things have clearly gotten worse.
Good luck to you all. Gonna need it.
on 08-07-2022 14:51
on 08-07-2022 16:51
Hello @HCA
Thanks for posting. Sorry to hear of the issues with the services. I've done a system check and nothing showing, no area issues and all levels are fine. Also checked for SNR and congestion, nothing showing for them either. On a further test, as I went back a month, the only issue I did see was on the 29th June, when the speed dropped and the latency and packet loss spiked, other than that all fine.
I shall send you a PM as you wish to raise this further however.
Best,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill