on 06-07-2022 14:21
Hi All first post on the community 😃.
Ive browse thru a few posts and it seems my BB signal issue is quite common, so I'll give you a quick brief of where I am at.
We've e had Virgin BB for around 2 years on M100 with booster always had issues with signal dropping off and speeds fluctuating, we have made contact with virgin customer services and technical without any real resolution. Things came to a head about a month ago when we called every day for about a week to try and get the BB signal issue resolved, we were fed bull$hit being fobbed off time and time again each operator contradicting the other, promises of call backs in 24hrs time and time again without a single callback.... enough was enough so we cancelled on 30th June 2022. After speaking to neighbours in the estate they advised that VBB was infact the best of a bad bunch so again we have signed back up for another 12 month but this time I've found this community and been reading some of the posts from people in the same boat as us.
The property: Stone built brick walled bungalow (booster required in bedroom)
Usage: 2 PS4's gamers, light streaming, 4 alexa's, 4 firesticks, 4 mobile phones, 1 laptop.
Virgins conclusion: Too many devices for the M100 package that we would need to upgrade to the M350 in order to have an uninterupted signal with that many devices connected (although only probably 4 are actually being used at any 1 time) virgin also advised that we should disconnect devices when not in use!!! That didn't go down too well 🙂
HELP: reading similar posts they have been advised to check the line firstly before going down the route of purchasing an alternative router, so could someone please decipher my router status which I'll post below. Many thanks in advance.
Account has only been reactivated for about 5 hours maybe to early for submitting router status?
on 06-07-2022 14:22
Downstream bonded channels
Channel | Frequency (Hz) | Power (dBmV) | SNR (dB) | Modulation | Channel ID |
1 | 299000000 | 5.5 | 38 | 256 qam | 21 |
2 | 139000000 | 7 | 40 | 256 qam | 1 |
3 | 147000000 | 6.9 | 40 | 256 qam | 2 |
4 | 155000000 | 7 | 40 | 256 qam | 3 |
5 | 163000000 | 6.9 | 40 | 256 qam | 4 |
6 | 171000000 | 6.9 | 40 | 256 qam | 5 |
7 | 179000000 | 6.8 | 38 | 256 qam | 6 |
8 | 187000000 | 6.8 | 38 | 256 qam | 7 |
9 | 195000000 | 6.5 | 38 | 256 qam | 8 |
10 | 203000000 | 6.5 | 40 | 256 qam | 9 |
11 | 211000000 | 6.4 | 38 | 256 qam | 10 |
12 | 219000000 | 6.1 | 40 | 256 qam | 11 |
13 | 227000000 | 6 | 40 | 256 qam | 12 |
14 | 235000000 | 6 | 40 | 256 qam | 13 |
15 | 243000000 | 5.9 | 40 | 256 qam | 14 |
16 | 251000000 | 5.6 | 40 | 256 qam | 15 |
17 | 259000000 | 5.5 | 40 | 256 qam | 16 |
18 | 267000000 | 5.6 | 38 | 256 qam | 17 |
19 | 275000000 | 5.6 | 40 | 256 qam | 18 |
20 | 283000000 | 5.5 | 40 | 256 qam | 19 |
21 | 291000000 | 5.1 | 38 | 256 qam | 20 |
22 | 307000000 | 5.8 | 40 | 256 qam | 22 |
23 | 315000000 | 5.9 | 40 | 256 qam | 23 |
24 | 323000000 | 5.6 | 40 | 256 qam | 24 |
Downstream bonded channels
Channel | Locked Status | RxMER (dB) | Pre RS Errors | Post RS Errors |
1 | Locked | 38.9 | 6 | 0 |
2 | Locked | 40.3 | 6 | 0 |
3 | Locked | 40.3 | 6 | 0 |
4 | Locked | 40.3 | 5 | 0 |
5 | Locked | 40.3 | 19 | 0 |
6 | Locked | 40.3 | 15 | 0 |
7 | Locked | 38.9 | 19 | 0 |
8 | Locked | 38.9 | 20 | 0 |
9 | Locked | 38.9 | 18 | 0 |
10 | Locked | 40.3 | 6 | 0 |
11 | Locked | 38.9 | 5 | 0 |
12 | Locked | 40.3 | 9 | 0 |
13 | Locked | 40.3 | 5 | 0 |
14 | Locked | 40.3 | 4 | 0 |
15 | Locked | 40.9 | 7 | 0 |
16 | Locked | 40.3 | 5 | 0 |
17 | Locked | 40.3 | 6 | 0 |
18 | Locked | 38.9 | 6 | 0 |
19 | Locked | 40.3 | 3 | 0 |
20 | Locked | 40.3 | 5 | 0 |
21 | Locked | 38.9 | 5 | 0 |
22 | Locked | 40.3 | 5 | 0 |
23 | Locked | 40.3 | 4 | 0 |
24 | Locked | 40.3 | 6 | 0 |
on 06-07-2022 14:23
Upstream bonded channels
Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
1 | 39400017 | 35.5 | 5120 | 64 qam | 12 |
2 | 46200053 | 35.5 | 5120 | 64 qam | 11 |
3 | 53700014 | 35.5 | 5120 | 64 qam | 10 |
4 | 60300036 | 35.5 | 5120 | 64 qam | 9 |
Upstream bonded channels
Channel | Channel Type | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
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 access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | ncxv9873254k;fg87dsfd;kfo |
Primary Downstream Service Flow
SFID | 416 |
Max Traffic Rate | 117000047 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 415 |
Max Traffic Rate | 10500047 |
Max Traffic Burst | 16320 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
Network Log
Time | Priority | Description |
06/07/2022 12:42:7 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/07/2022 02:39:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/07/2022 04:17:36 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-cancel-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/07/2022 04:17:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/06/2022 09:29:42 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/06/2022 09:29:42 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/06/2022 09:22:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/06/2022 21:29:41 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/06/2022 21:29:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 22:09:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 15:15:31 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 09:29:43 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 09:29:43 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/06/2022 23:58:16 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/06/2022 19:18:42 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/06/2022 03:01:52 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2022 21:29:41 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
|
on 06-07-2022 14:32
on 06-07-2022 14:47
Thanks for the reply John, previously when we had the drop off and fluctuating signal issues we didnt have any devices hard wired by ethernet cables and currently still dont but i would like to run a single ethernet cable to each bedroom going forward. If you know of any good simple wiring schematics available on the net please post a link thanks.
The hub we are using currently is a VM 3.0
With the property having brick walls we struggled to stream in the bedroom so were given a booster which did help but was also effected by the signal drop off. The hub is quite central in the property.
What we found when the signal dropped out was to either do a speedcheck which somehow gave it a nudge and it kicked back in or we would reset the router in order to get th signal back.
06-07-2022 15:06 - edited 06-07-2022 15:08
Running good Cat6a cable (better shielding) is the best solution. Re wiring schemetics - thats a bridge too far for me! I would just plug the cables into my router and run the cables either internally, under floorboards, between carpet and skirting board etc. Or external cable, outside the house after exiting either underneath floorboards or through airbricks and then back in again.
I would then connect a wireless access point on each one in the chosen areas.
Something like this
https://www.amazon.co.uk/NETGEAR-Wireless-Access-Business-WAC104-100UKS/dp/B01LWUJU8H/
Others may offer more sophisticated solutions 🙂
on 08-07-2022 16:06
Hello G231G,
Thanks for your first post and welcome to our Community.
Sorry to hear you are having an issue with reconnected hub and the drops outs
Id like to take a look into this for you.
If you don't mind, I will need to send you a private message to pass security.
If you can check the purple envelope top right of your screen that would be great.
Regards
Gareth_L