on 04-07-2021 22:10
The network log on my hub 3 only goes back to 23/05/2021, but has been reporting various issues.
critical No Ranging Response received - T3 time-out
Error DHCP RENEW WARNING - Field invalid in response v4
Just wondering if this related to the poor wifi signal through the house?
I would be grateful if someone could advise please.
If more information is required then please let me know.
Thanks.
Paddy O'Brien.
on 04-07-2021 22:33
on 04-07-2021 22:53
How many T3 timeouts does it show over that period? It would help if you posted the logs here.
The timeouts affect the broadband connection, not directly the WiFi. But if the broadband is slow then the WiFi will follow.
Post all the logs, as text not screenshots.
on 07-07-2021 11:22
Hi @pobrien31
Thank you for making a post regarding the issues reported on your network log.
Are you able to post the full network logs as a response on here so we can see what errors are occuring?
Regarding your WiFi coverage around the house, I've taken a look at your account and can see that a device is located too close to the Hub. This could be affecting the overall performance of your WiFi. Are you able to move the device closest to your Hub slightly further away and let me know if that improves things.
As you have a Hub 3, have you downloaded our Connect App virg.in/connectapp to scan for black spots in your home and order an Intelligent WiFi Pod to improve signal?
Best wishes,
Serena
on 20-07-2021 09:28
Hi Serena,
Apologies for the late response.
Network log as requested:
20/07/2021 08:20:39 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 02:57:24 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 01:11:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 14:57:24 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/07/2021 08:51:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/07/2021 02:57:23 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:44 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:39 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:38 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:38 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 09:46:38 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/07/2021 20:34:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/07/2021 20:48:20 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/07/2021 12:52:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/07/2021 20:20:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/07/2021 13:36:34 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/06/2021 20:20:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/06/2021 22:44:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 20-07-2021 10:31
Hi Pobrien,
Thanks for your reply and your network log, I have checked your account and everything is fine, I have checked your power levels and all is fine.
Could you set up a BQM graph so we can see if there are any dropouts?
You can do so here.
Zoie
on 20-07-2021 15:06
<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/a4e1a84fc4df0cc5fd4403748a3bc2a878d83e8a"><img alt="My Broadband Ping - POBRIENVM" src="https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/a4e1a84fc4df0cc5fd4403748a3bc2a878d83e8a.png" /></a>
on 20-07-2021 15:19
Thanks, Pobrien31,
Please keep this running for 48 hours so we can get a reading as to what is going on
Zoie
on 25-07-2021 18:09
25-07-2021 18:22 - edited 25-07-2021 18:23
I can see the image now.
The BQM all looks good apart from ~01.30-03.30 - did you have it switched off then? Or perhaps VM were doing some network changes at that time - its their "favourite" time to do it.
What do the Logs say for that period?