Wi-Fi & Pod is flashing

[neoanderson]

My internet is constantly dropping connections for a few weeks now, and progressively getting worse! The Pod lights keep flashing white, blue etc. The engineer came today and replaced the router. Worked for a few hours then kept dropping the connection. I work from home and the 500mb just doesn’t get much faster than 20mb through the day, although  seen it hot over 500mb on Wi-Fi. I’ve spoken in the phone, the online chat, Twitter etc and not getting anywhere. They said the forums should be able to fix it! The connect app is struggling to find the hub! Help!

•  

   

  

   

[g0akc]

What do you mean by this bit “although  seen it hot over 500mb on Wi-Fi”.

Are wired connections okay?  

What does the hub status data show?  It’s available at 192.168.0.1

[neoanderson]

I meant the speed can hit over 500MB on Wi-Fi.

It's currently working. Scrap that, it's just gone off on all devices and the Wifi light on the router is flashing green

The Hub status is green for both 2.4 (channel 6) and 5Ghz (channel 108) and channel optimisation is enabled.

[bitsandpcs]

If you have a hub 4 make sure you are running the latest update of the app, I had a similar issue with the hub4 and the engineer swapped it for a 5.

Move the pods closer to the hub and see what happens, else you will have to get VM to re add the pods to the system. (My pods worked fine with a new hub no issues). 

[neoanderson]

I’ve got a Hub 3 that was replaced yesterday. The drop in connection continued into last night. I had to hotspot of my mobile data, as I was at work yesterday! The pod has been reallocated to the hub as the engineer called and got this done.

I’ve logged out and deleted the connect app, restarted my iPhone and still have the same issue. The internet has been pretty stable this morning, with only one dropout I had noticed. I’m worried about WFH as the connection isn’t reliable, with the dropouts! 

[neoanderson]

So are these figures normal or can you see anything unusual?

They guys on the chat said you could fix it all on here, including the Virgin connect app issues!

Router status

• Status
• Downstream
• Upstream
• Configuration
• Network Log

Refresh data

Network Log

Time Priority Description

25/07/2022 14:29:31	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 13:01:6	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 12:22:59	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;
25/07/2022 12:06:48	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:01:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:01:8	Warning!	B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:00:14	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:00:13	Warning!	B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:58:44	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:53	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:8	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:4	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:4	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:4	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:4	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:29:21	Warning!	B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:28:23	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:27:52	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:27:46	critical	DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:25:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[neoanderson]

Did a quick Speedtest, and it does vary! Managed to get the Virgin connect to work. Again it works sometimes and other times it can’t find the router. Or comes back with an error saying something wrong on our end. 

 

[Nathan_B]

Hi there @neoanderson, welcome back to our forum and thanks for your post.

I'm sorry to see that you have been having issues with your hub and the pods. I have checked our system and am unable to see any reason as to why you are getting these issues. In regards to the pods, have you tried moving locations to see if this helps then connect to the hub?

Regards

Nathan

[neoanderson]

I have tried moving them around. Not sure if they're supposed to have green and white flashing lights. One of them is within direct line to the Hub 3.0. These are very intermittent issues. The Wi-Fi can be great sometimes or can constantly drop connection and speed at other times. I don't have a telephone line. 

[neoanderson]

This is the network status

Network Log

Time Priority Description

31/07/2022 11:01:28	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/07/2022 19:28:7	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/07/2022 11:56:16	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/07/2022 11:56:16	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/07/2022 14:58:45	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/07/2022 14:30:53	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 19:50:47	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 19:48:41	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 19:46:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 14:29:31	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 13:01:6	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 12:22:59	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;
25/07/2022 12:06:48	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:01:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:01:8	Warning!	B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:00:14	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/07/2022 00:00:13	Warning!	B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:58:44	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:53	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/07/2022 23:31:8	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;