on 10-01-2024 15:14
Hi all
My Wifi has been up and down all day today and yesterday. I ran a diognostic and got this:
And logs are showing this error:
10-01-2024 14:50:22 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:50:21 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:50:21 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:49:55 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:49:55 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:49:52 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:51 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:50 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:49 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:49 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:49:47 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:49:47 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:49:44 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <4>
10-01-2024 14:49:44 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:43 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:42 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:41 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:41 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:49:39 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:49:39 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:49:36 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:35 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:34 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:33 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:33 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:49:31 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:49:31 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:49:28 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:27 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:26 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:25 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:25 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:49:21 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:49:21 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:49:18 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:17 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:16 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:15 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:15 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:49:13 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:49:13 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:49:10 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:09 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:08 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:07 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:49:07 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: associated
10-01-2024 14:48:57 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <15>
10-01-2024 14:48:57 debug [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: disassociated <15>
10-01-2024 14:48:54 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:48:53 information [**:**:**:**:**:**][WiFi] **:**:**:**:**:**: EAPOL failure <14>
10-01-2024 14:48:18 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:47:41 notice GUI Login Status - Login Sucess from LAN interface; client ip=[192.168.0.17];CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:45:57 notice MDD Recovery following MDD Loss;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:45:56 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:45:27 notice MDD Recovery following MDD Loss;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:45:26 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:44:36 notice MDD Recovery following MDD Loss;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:44:34 warning Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:44:33 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:30:55 notice Illegal - Dropped FORWARD packet: src=2606:2800:0233:8173:898f:63b3:95c3:79d2 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:25:16 notice GUI Login Status - Login Sucess from LAN interface; client ip=[192.168.0.17];CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:23:21 notice Illegal - Dropped FORWARD packet: src=2a03:2880:f132:0080:face:b00c:0000:1ea0 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:21:27 notice TR069 start;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:21:24 notice Illegal - Dropped FORWARD packet: src=192.168.0.38 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:20:04 notice REGISTRATION COMPLETE - Waiting for Operational status;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:20:03 notice Illegal - Dropped FORWARD packet: src=192.168.0.38 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:19:58 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:19:25 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10-01-2024 14:06:31 notice GUI Login Status - Login Sucess from LAN interface; client ip=[192.168.0.80];CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 00:01:23 notice Cable Modem Reboot - due to power reset;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Any ideas?
Thanks in advance
on 10-01-2024 15:47
Have you checked first for any “known network faults in your location - Look in 2 places
1) Try the “check service,”Area status webpage (https://www.virginmedia.com/help/service-status)
2) Then also Try the “free & automated” Service Status number - 0800 561 0061 - which usually gives the most up to date info. and tells you of more local issues and fix estimates, down to street cab/ postcode level.
on 10-01-2024 16:03
Hih there
Thanks for the respose.
I (eventually) got on to an amazing customer service person who fixed it.
Turns out 2.6 and 5G were having a fight about who runs the network.
on 10-01-2024 17:18
Hi i have for a while been just using the 2.5 one but am now thinking of putting the 5 one back online.
you can if u want to control ur router setting on the website
on 12-01-2024 17:51
Hi Raytoe,
Thank you for your post and welcome to the community.
I'm very sorry to hear about the issue you've been having with your WiFi.
We're glad to hear you were able to speak with the team regarding this and get this resolved.
^Martin