on 12-09-2022 14:06
Hi there,
About 2 years ago I was constantly losing connection to internet. It was showing conneceted to router but no internet connection. I had a couple of engineer visits and was then sent a new router which cured the issue. And now It's started again. I stream a lot of films and sports.(Legal streams, Netflix, Disney, sky etc). IT was the occasional programme but now its far worse. Even when just working on line. Could this be a router issue again? Or is there some other issue with cabling to the house?
I've tried calling customer services but they always seem to be busy.
Any help would be appreciated..
Steve
Answered! Go to Answer
on 12-09-2022 14:59
on 12-09-2022 14:59
on 12-09-2022 16:07
Hi John and thanks for your reply.
The answer to your 2 questions is No, there are known issues.
It happens on both ethernet and WiFi. Although it does seem worse on WiFi over all devices.
It is a Hub3 and there seems to be a lot of flasing lights at rear and the base light at the front stays on. The router is positioned on a table in the living room, nothing on front of it or near that could affect it.
I have done a couple of resets, which seem to work for a couple of hours, but then it all goes wrong again. blooming annoying too.
Steve
on 12-09-2022 16:10
@StephenO wrote:
The answer to your 2 questions is No, there are known issues.
So if there are known issues - nothing can be done until VM fix them.
on 12-09-2022 16:19
Sorry, meant to write there are 'NO' known issues.
I apologise for the confusion.
Steve
on 12-09-2022 16:26
on 14-09-2022 09:13
Here goes....Does this help?
1 | 371000000 | 8.9 | 40 | 256 qam | 30 |
2 | 203000000 | 6 | 40 | 256 qam | 9 |
3 | 211000000 | 6.1 | 40 | 256 qam | 10 |
4 | 219000000 | 5.9 | 40 | 256 qam | 11 |
5 | 227000000 | 5.6 | 40 | 256 qam | 12 |
6 | 235000000 | 5.4 | 38 | 256 qam | 13 |
7 | 243000000 | 5.8 | 40 | 256 qam | 14 |
8 | 251000000 | 6 | 40 | 256 qam | 15 |
9 | 259000000 | 6.3 | 40 | 256 qam | 16 |
10 | 267000000 | 6.3 | 40 | 256 qam | 17 |
11 | 275000000 | 6 | 40 | 256 qam | 18 |
12 | 283000000 | 6.1 | 40 | 256 qam | 19 |
13 | 291000000 | 6.5 | 40 | 256 qam | 20 |
14 | 299000000 | 7.5 | 40 | 256 qam | 21 |
15 | 307000000 | 7.9 | 40 | 256 qam | 22 |
16 | 315000000 | 8 | 38 | 256 qam | 23 |
17 | 323000000 | 7.8 | 40 | 256 qam | 24 |
18 | 331000000 | 7.5 | 40 | 256 qam | 25 |
19 | 339000000 | 7 | 38 | 256 qam | 26 |
20 | 347000000 | 7.5 | 40 | 256 qam | 27 |
21 | 355000000 | 8.1 | 40 | 256 qam | 28 |
22 | 363000000 | 8.5 | 40 | 256 qam | 29 |
23 | 379000000 | 8.5 | 40 | 256 qam | 31 |
24 | 387000000 | 8 | 40 | 256 qam | 32 |
1 | 371000000 | 8.9 | 40 | 256 qam | 30 |
2 | 203000000 | 6 | 40 | 256 qam | 9 |
3 | 211000000 | 6.1 | 40 | 256 qam | 10 |
4 | 219000000 | 5.9 | 40 | 256 qam | 11 |
5 | 227000000 | 5.8 | 40 | 256 qam | 12 |
6 | 235000000 | 5.4 | 38 | 256 qam | 13 |
7 | 243000000 | 5.8 | 40 | 256 qam | 14 |
8 | 251000000 | 6 | 40 | 256 qam | 15 |
9 | 259000000 | 6.3 | 40 | 256 qam | 16 |
10 | 267000000 | 6.3 | 40 | 256 qam | 17 |
11 | 275000000 | 6 | 40 | 256 qam | 18 |
12 | 283000000 | 6.1 | 40 | 256 qam | 19 |
13 | 291000000 | 6.5 | 40 | 256 qam | 20 |
14 | 299000000 | 7.5 | 40 | 256 qam | 21 |
15 | 307000000 | 7.9 | 40 | 256 qam | 22 |
16 | 315000000 | 8 | 38 | 256 qam | 23 |
17 | 323000000 | 7.8 | 40 | 256 qam | 24 |
18 | 331000000 | 7.5 | 40 | 256 qam | 25 |
19 | 339000000 | 7 | 38 | 256 qam | 26 |
20 | 347000000 | 7.5 | 40 | 256 qam | 27 |
21 | 355000000 | 8 | 40 | 256 qam | 28 |
22 | 363000000 | 8.5 | 40 | 256 qam | 29 |
23 | 379000000 | 8.5 | 40 | 256 qam | 31 |
24 | 387000000 | 8 | 40 | 256 qam | 32 |
on 14-09-2022 09:14
Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
1 | 60300004 | 46 | 5120 | 64 qam | 1 |
2 | 39399993 | 44 | 5120 | 64 qam | 4 |
3 | 46200009 | 44 | 5120 | 64 qam | 3 |
4 | 53700009 | 44.5 | 5120 | 64 qam | 2 |
Upstream bonded channels
Channel | Channel Type | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
1 | 60300004 | 46 | 5120 | 64 qam | 1 |
2 | 39399993 | 44 | 5120 | 64 qam | 4 |
3 | 46200009 | 44 | 5120 | 64 qam | 3 |
4 | 53700009 | 44.5 | 5120 | 64 qam | 2 |
Upstream bonded channels
Channel | Channel Type | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 14-09-2022 09:15
Last set
Network log
Time | Priority | Description |
14/09/2022 06:39:34 | critical | No Ranging Response received - T3 time-out;CM- |
13/09/2022 10:48:34 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified; |
13/09/2022 10:48:34 | Error | DHCP RENEW WARNING - Field invalid in response v4 option; |
09/09/2022 16:18:54 | critical | No Ranging Response received - T3 time-out;CM- |
09/09/2022 07:07:24 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM- |
09/09/2022 07:07:24 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM- |
06/09/2022 05:09:31 | critical | No Ranging Response received - T3 time-out;CM- |
05/09/2022 19:07:23 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;; |
05/09/2022 19:07:23 | Error | DHCP RENEW WARNING - Field invalid in response v4 option; |
04/09/2022 16:21:1 | critical | No Ranging Response received - T3 time-out;CM- |
03/09/2022 11:36:5 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM- |
02/09/2022 11:21:45 | critical | No Ranging Response received - T3 time-out;CM- |
02/09/2022 07:07:23 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified; |
02/09/2022 07:07:23 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM- |
30/08/2022 17:53:40 | critical | No Ranging Response received - T3 time-out;CM- |
30/08/2022 12:41:59 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified; |
30/08/2022 12:41:59 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM- |
25/08/2022 16:04:59 | critical | No Ranging Response received - T3 time-out;CM-MAC= |
25/08/2022 12:32:49 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified; |
25/08/2022 12:32:49 | Error | DHCP RENEW WARNING - Field invalid in response v4 option; |
on 15-09-2022 17:49
I have put the figures on here as requested. But have not had any further responses.
Have I not put the correct details? Or are they showing no issues? It's all complete gobbledegook to me.
Any help at all?
Steve