on 27-04-2022 14:15
Hi All,
I've been having some issues lately with the Wi-Fi connection dropping.
The signal has never been the best in the bedroom but never had so many dropouts as I have recently.
I've checked the logs and found some critical issues - I'm not sure what exactly the logs show but hoping someone can see if there are any issues they can spot?
Thanks in advance
Answered! Go to Answer
29-04-2022 16:16 - edited 29-04-2022 16:17
BQM not great - can you try this. Overnight remove the ethernet cable for the PS4 and TV. Next morning look at the overnight BQM and see if it has "cleaned up". If it has, plug the TV in and switch it on and connect to some online content. Then after an hour or two check the BQM again. If its still clear, plug the PS4 in and switch it on and see what happens then.
Meanwhile if you are having wifi issues whilst ethernet connections remain solid... see this.
_____________________________
If it is a wifi only issue, then on a Hub3/4/5, you can try separating the SSID's of the 2.4 and 5 GHz wifi bands by renaming them in the settings and at the same time switch off "channel optimisation/Smart wifi” “ apply and save the settings. All wifi devices will need reconnecting to the best SSID at each location. Also use a wifi scanning App to find the best wifi channels to use (just select and use channels 1,6,11 on 2.4GHz) - this often helps Hub users get better wifi performance - but its still no substitute for getting better kit 🙂
To address the wifi issues, VM now supply “wifi Pods” (no longer doing cheap and cheerless “boosters”). However, their Pods are only free to customers on the 1GB, Ultimate Oomph or Volt packages - is that you? If so they are worth trying - they should work for you.
You do have to call in to order them (cant do it online) - or just wait here for a VM person to respond in a day or two and they will sort the first one for you .
If not… you will be charged £5/month (note - BT charge £10/mo for their whole home wifi solution). It’s a simple solution and should work for you. However, you would soon pay off that cost by buying your own wireless solution that will be yours to own and use forever, but it isn’t the simple plug and play option of the Pod(s).
You would need to get either a… (1) Mesh System, (2) Wireless router, (3) Wireless access point (4) Powerline adapters (+/- inbuilt Wifi,) (5) A combination of (2,3,4).
on 27-04-2022 14:16
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 234750000 | 0 | 38 | 256 qam | 13 |
2 | 138750000 | 1.7 | 38 | 256 qam | 1 |
3 | 146750000 | 1.2 | 38 | 256 qam | 2 |
4 | 154750000 | 1.2 | 38 | 256 qam | 3 |
5 | 162750000 | 1 | 38 | 256 qam | 4 |
6 | 170750000 | 0.4 | 38 | 256 qam | 5 |
7 | 178750000 | 0.2 | 38 | 256 qam | 6 |
8 | 186750000 | 0 | 38 | 256 qam | 7 |
9 | 194750000 | -0.4 | 38 | 256 qam | 8 |
10 | 202750000 | 0.2 | 38 | 256 qam | 9 |
11 | 210750000 | 0.2 | 38 | 256 qam | 10 |
12 | 218750000 | 0.2 | 38 | 256 qam | 11 |
13 | 226750000 | 0.7 | 38 | 256 qam | 12 |
14 | 242750000 | 0.2 | 40 | 256 qam | 14 |
15 | 250750000 | 0.7 | 38 | 256 qam | 15 |
16 | 258750000 | 0.4 | 40 | 256 qam | 16 |
17 | 266750000 | 0.9 | 38 | 256 qam | 17 |
18 | 274750000 | 0.9 | 40 | 256 qam | 18 |
19 | 282750000 | 0.7 | 40 | 256 qam | 19 |
20 | 290750000 | 1 | 40 | 256 qam | 20 |
21 | 298750000 | 1.2 | 40 | 256 qam | 21 |
22 | 306750000 | 1 | 38 | 256 qam | 22 |
23 | 314750000 | 1.2 | 40 | 256 qam | 23 |
24 | 322750000 | 1 | 38 | 256 qam | 24 |
on 27-04-2022 14:16
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 21 | 0 |
2 | Locked | 38.6 | 58 | 0 |
3 | Locked | 38.9 | 42 | 0 |
4 | Locked | 38.9 | 32 | 0 |
5 | Locked | 38.6 | 54 | 7754 |
6 | Locked | 38.9 | 36 | 0 |
7 | Locked | 38.6 | 19 | 0 |
8 | Locked | 38.9 | 23 | 0 |
9 | Locked | 38.6 | 23 | 0 |
10 | Locked | 38.9 | 15 | 0 |
11 | Locked | 38.6 | 15 | 0 |
12 | Locked | 38.9 | 15 | 0 |
13 | Locked | 38.9 | 12 | 0 |
14 | Locked | 38.9 | 15 | 0 |
15 | Locked | 38.6 | 9 | 0 |
16 | Locked | 38.9 | 8 | 0 |
17 | Locked | 38.9 | 15 | 0 |
18 | Locked | 39.8 | 9 | 0 |
19 | Locked | 40.3 | 20 | 0 |
20 | Locked | 40.3 | 11 | 0 |
21 | Locked | 40.3 | 14 | 0 |
22 | Locked | 38.9 | 12 | 0 |
23 | Locked | 40.3 | 17 | 0 |
24 | Locked | 38.9 | 13 | 0 |
on 27-04-2022 14:17
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 25800004 | 43.5 | 5120 | 64 qam | 14 |
2 | 32600039 | 44.5 | 5120 | 64 qam | 13 |
3 | 39399991 | 45.5 | 5120 | 64 qam | 12 |
4 | 46200000 | 46 | 5120 | 64 qam | 11 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 27-04-2022 14:17
Time Priority Description
27/04/2022 11:35:46 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/04/2022 08:52:21 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 11:30:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 09:53:57 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 09:53:57 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/04/2022 21:13:5 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/04/2022 08:48:36 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/04/2022 08:48:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/04/2022 05:47:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/04/2022 05:37:24 | 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; |
15/04/2022 20:48:36 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/04/2022 20:48:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/04/2022 18:26:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/04/2022 03:26:33 | 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; |
13/04/2022 04:22:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/04/2022 21:56:0 | 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; |
12/04/2022 11:57:0 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/04/2022 08:48:36 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/04/2022 08:48:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/04/2022 12:33:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27-04-2022 14:34 - edited 27-04-2022 14:35
Not too much wrong there, although down channel 5 looks odd can you do this...
_________________________________
Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables. Then switch the Hub back on and leave ~5 minutes
When all done, check back in the settings and ensure that the RS error counts and any T3 errors have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the postRS ones in channel 5) you have a problem (noise) that may need a Tech visit will sort.
Also,
If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK
https://www.thinkbroadband.com/broadband/monitoring/quality
on 27-04-2022 14:56
on 28-04-2022 08:43
Here's a link to the BQM 🙂
on 28-04-2022 15:36
on 29-04-2022 08:55
Here is the latest downstream data from just now - not showing any post RD errors
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 2 | 0 |
2 | Locked | 38.6 | 26 | 0 |
3 | Locked | 38.9 | 20 | 0 |
4 | Locked | 38.9 | 20 | 0 |
5 | Locked | 38.6 | 21 | 0 |
6 | Locked | 38.6 | 16 | 0 |
7 | Locked | 38.6 | 8 | 0 |
8 | Locked | 38.6 | 7 | 0 |
9 | Locked | 38.6 | 6 | 0 |
10 | Locked | 38.9 | 6 | 0 |
11 | Locked | 38.9 | 7 | 0 |
12 | Locked | 38.6 | 7 | 0 |
13 | Locked | 38.9 | 8 | 0 |
14 | Locked | 40.3 | 9 | 0 |
15 | Locked | 38.9 | 8 | 0 |
16 | Locked | 40.3 | 0 | 0 |
17 | Locked | 38.9 | 8 | 0 |
18 | Locked | 40.3 | 9 | 0 |
19 | Locked | 40.3 | 10 | 0 |
20 | Locked | 40.9 | 7 | 0 |
21 | Locked | 40.3 | 6 | 0 |
22 | Locked | 40.3 | 6 | 0 |
23 | Locked | 40.3 | 6 | 0 |
24 | Locked | 38.9 | 6 | 0 |