cancel
Showing results for 
Search instead for 
Did you mean: 

Having to swtich wifi off & on multiple times

Pidge22
On our wavelength

We had Virgin Broadband (Oomph) installed late June & whilst we are seeing speeds at times around the 630 mbs stated my Macbook Pro will show 30mbs & this is only rectified by switching the WIFI on & off then it shows the higher speed and this is something I have to repeat at least daily ,I have tried rebooting the hub but this still continues.

11 REPLIES 11

Andrew-G
Alessandro Volta

Potentially a power/noise problem on the broadband side of things.  Connect to the hub by clicking on this link http://192.168.0.1/  That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.  Then we can check for any obvious problems with power, noise or error counts, if there's obvious problems the staff can book a technician. 

If all that sounds too difficult, then there's always the on-line help, and VM's world famous telephone support.

Pidge22
On our wavelength

Unfortunately I cannt get into the hub settings with the settings password underneath the Hub 4

Pidge22
On our wavelength

managed to get required information

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

253310000005.19999740.366287QAM25625
11390000006.80000340.366287QAM2561
51710000005.40000240.366287QAM2565
61790000005.30000340.366287QAM2566
81950000005.19999740.366287QAM2568
92030000005.00000040.366287QAM2569
102110000004.59999840.366287QAM25610
132350000003.90000240.366287QAM25613
142430000004.19999740.366287QAM25614
152510000004.30000340.366287QAM25615
162590000004.69999740.366287QAM25616
172670000004.80000340.366287QAM25617
182750000005.00000040.946209QAM25618
192830000004.80000340.946209QAM25619
202910000004.69999740.946209QAM25620
212990000004.69999740.366287QAM25621
223070000005.00000040.366287QAM25622
233150000005.19999740.366287QAM25623
243230000005.40000240.366287QAM25624
263710000004.69999740.366287QAM25626
273790000004.69999740.366287QAM25627
283870000004.59999840.366287QAM25628
293950000004.69999740.366287QAM25629
304030000004.69999740.366287QAM25630
314110000004.69999740.366287QAM25631
324190000004.69999740.366287QAM25632
334270000004.80000340.366287QAM25633
344350000004.90000240.366287QAM25634
354430000005.00000040.366287QAM25635
364510000005.09999840.366287QAM25636
374590000005.09999840.366287QAM25637
384670000005.00000040.366287QAM25638



3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

25Locked40.36628700
1Locked40.36628700
5Locked40.36628700
6Locked40.36628700
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
13Locked40.36628700
14Locked40.36628700
15Locked40.36628700
16Locked40.36628700
17Locked40.36628700
18Locked40.94620900
19Locked40.94620900
20Locked40.94620900
21Locked40.36628700
22Locked40.36628700
23Locked40.36628700
24Locked40.36628700
26Locked40.36628700
27Locked40.36628700
28Locked40.36628700
29Locked40.36628700
30Locked40.36628700
31Locked40.36628700
32Locked40.36628700
33Locked40.36628700
34Locked40.36628700
35Locked40.36628700
36Locked40.36628700
37Locked40.36628700
38Locked40.36628700

 

 

Pidge22
On our wavelength

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13260000047.0000005120 KSym/sec64QAM3
24620000047.0000005120 KSym/sec64QAM1
32580000047.2500005120 KSym/sec64QAM4
43940000047.0000005120 KSym/sec64QAM2



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

 

Network Log

Time Priority Description

Tue Jul 13 17:40:01 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 14 01:58:36 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 14 14:42:23 20214DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 14 14:42:25 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 14 18:08:45 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 14 19:34:52 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 16 17:24:38 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 16 17:25:03 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 18 13:45:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 24 03:31:53 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 24 18:26:33 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 25 01:33:38 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 25 06:12:48 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 28 06:26:33 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 29 19:29:22 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 31 18:26:34 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 3 07:22:33 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 4 06:26:34 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 5 09:40:54 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 7 18:26:34 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 9 18:39:35 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 11 06:26:35 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 11 22:03:19 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 12 18:31:59 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 12 20:50:39 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 12 20:51:04 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 13 16:41:16 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 13 18:56:36 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:19 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 14 08:18:59 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 14 08:19:24 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:19 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 14 08:38:48 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 14 08:39:14 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:20 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 14 09:04:05 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 14 09:04:31 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 15 20:00:31 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 15 22:28:12 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 16 07:45:27 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 23 02:41:03 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:22 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 24 14:47:27 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 24 14:47:53 20215RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Andrew-G
Alessandro Volta

Due to a firmware fail by VM, the downstream errors are not reporting, that may hide something, but you also appear to be missing the DOCSIS 3.1 channel, and the network log has a number of messages with the sinister sounding "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW" - not that I can tell you what that means in English.

I'll mark this for forum staff to take a look and advise.

Pidge22
On our wavelength

thanks very much for your help with this

Hayley_S
Forum Team (Retired)
Forum Team (Retired)

Hello @Pidge22,

 

Welcome back to the community page, thank you for posting on here.

 

I am sorry to see that your Wi-Fi is not working.

 

I would love to try and help you with this, I will send you a private message so I can investigate this.

 

Please look out for a plum envelope at the top right or your page.

 

Many thanks,

Hayley
Forum Team



New around here? To find out more about the Community check out our Getting Started guide


Pidge22
On our wavelength

Have replied to PM thanks

Hayley_S
Forum Team (Retired)
Forum Team (Retired)

Hello @Pidge22,

 

I have just seen this now thank you 🙂

 

I have booked an engineer visit for you, you can check this on your online account.

 

Please let me know if this date and time is okay for you, this was the earliest booking I could book for you.

 

Many thanks,

Hayley
Forum Team



New around here? To find out more about the Community check out our Getting Started guide