Fibre broadband keeps dropping, router light goes orange

[#1]

I'm cursed. My desktop PC was working fine this morning when I "logged on to work" using ethernet but the wi-fi was totally dead / down. Couldn't connect my works laptop, our mobiles or tablet

Can you do some kind of test please to back me up. Router light went green / flashed then blue again, but am using that EE 4GEE mini wifi router for the moment for my works laptop as I need to get work done.

[#2]

09:13:08, 27 Jan. ( 134.880000) WAN operating mode is VDSL
09:13:08, 27 Jan. ( 134.880000) Last WAN operating mode was VDSL
09:13:06, 27 Jan. ( 133.670000) PPP IPCP Receive Configuration ACK
09:13:06, 27 Jan. ( 133.660000) PPP IPCP Send Configuration Request
09:13:06, 27 Jan. ( 133.650000) PPP IPCP Receive Configuration NAK
09:13:06, 27 Jan. ( 133.650000) PPP IPCP Send Configuration ACK
09:13:06, 27 Jan. ( 133.650000) PPP IPCP Receive Configuration Request
09:13:06, 27 Jan. ( 133.640000) PPP IPCP Send Configuration Request
09:13:05, 27 Jan. ( 132.590000) PPPoE is up -​ Down Rate=70522Kbps, Up Rate=16229Kbps; SNR Margin Down=7.1dB, Up=12.5dB
09:13:05, 27 Jan. ( 132.570000) CHAP authentication successful
09:13:05, 27 Jan. ( 132.510000) CHAP Receive Challenge
09:13:05, 27 Jan. ( 132.510000) Starting CHAP authentication with peer
09:13:05, 27 Jan. ( 132.510000) PPP LCP Receive Configuration ACK
09:13:05, 27 Jan. ( 132.500000) PPP LCP Send Configuration Request
09:13:05, 27 Jan. ( 132.500000) PPP LCP Receive Configuration Reject
09:13:05, 27 Jan. ( 132.500000) PPP LCP Send Configuration ACK
09:13:05, 27 Jan. ( 132.500000) PPP LCP Receive Configuration Request
09:13:05, 27 Jan. ( 132.490000) PPP LCP Send Configuration Request
09:12:16, 27 Jan. ( 83.620000) PTM over DSL is up
09:11:29, 27 Jan. ( 36.070000) WAN Auto-​sensing running.
03:01:05, 18 Jan. (2077089.390000) WAN operating mode is VDSL
03:01:05, 18 Jan. (2077089.390000) Last WAN operating mode was VDSL
03:01:03, 18 Jan. (2077087.700000) PPP IPCP Receive Configuration ACK
03:01:03, 18 Jan. (2077087.700000) PPP IPCP Send Configuration Request
03:01:03, 18 Jan. (2077087.690000) PPP IPCP Receive Configuration NAK
03:01:03, 18 Jan. (2077087.680000) PPP IPCP Send Configuration ACK
03:01:03, 18 Jan. (2077087.680000) PPP IPCP Receive Configuration Request
03:01:03, 18 Jan. (2077087.640000) PPP IPCP Send Configuration Request
03:01:02, 18 Jan. (2077086.130000) PPPoE is up -​ Down Rate=70522Kbps, Up Rate=16229Kbps; SNR Margin Down=7.0dB, Up=12.7dB
03:01:02, 18 Jan. (2077086.120000) CHAP authentication successful
03:01:02, 18 Jan. (2077086.080000) CHAP Receive Challenge
03:01:02, 18 Jan. (2077086.080000) Starting CHAP authentication with peer
03:01:02, 18 Jan. (2077086.070000) PPP LCP Receive Configuration ACK
03:01:02, 18 Jan. (2077086.070000) PPP LCP Send Configuration Request
03:01:02, 18 Jan. (2077086.060000) PPP LCP Receive Configuration Reject
03:01:02, 18 Jan. (2077086.060000) PPP LCP Send Configuration ACK
03:01:02, 18 Jan. (2077086.060000) PPP LCP Receive Configuration Request
03:01:02, 18 Jan. (2077086.060000) PPP LCP Send Configuration Request
03:00:11, 18 Jan. (2077035.580000) PTM over DSL is up
02:59:35, 18 Jan. (2076999.370000) PTM over DSL is down after 998 minutes uptime
02:59:35, 18 Jan. (2076999.360000) PPPoE is down after 998 minutes uptime [Waiting for Underlying Connection (WAN Ethernet 7 -​ Down)]
02:59:32, 18 Jan. (2076995.930000) PPP LCP Send Termination Request [User request]
10:21:27, 17 Jan. (2017114.430000) WAN operating mode is VDSL
10:21:27, 17 Jan. (2017114.430000) Last WAN operating mode was VDSL
10:21:25, 17 Jan. (2017112.640000) PPP IPCP Receive Configuration ACK
10:21:25, 17 Jan. (2017112.630000) PPP IPCP Send Configuration Request
10:21:25, 17 Jan. (2017112.620000) PPP IPCP Receive Configuration NAK
10:21:25, 17 Jan. (2017112.620000) PPP IPCP Send Configuration ACK
10:21:25, 17 Jan. (2017112.620000) PPP IPCP Receive Configuration Request
10:21:25, 17 Jan. (2017112.620000) PPP IPCP Send Configuration Request
10:21:24, 17 Jan. (2017111.010000) PPPoE is up -​ Down Rate=73188Kbps, Up Rate=967Kbps; SNR Margin Down=6.0dB, Up=6.6dB
10:21:24, 17 Jan. (2017111.000000) CHAP authentication successful
10:21:24, 17 Jan. (2017110.920000) CHAP Receive Challenge
10:21:24, 17 Jan. (2017110.920000) Starting CHAP authentication with peer
10:21:24, 17 Jan. (2017110.910000) PPP LCP Receive Configuration ACK
10:21:24, 17 Jan. (2017110.900000) PPP LCP Send Configuration Request
10:21:24, 17 Jan. (2017110.900000) PPP LCP Receive Configuration Reject
10:21:24, 17 Jan. (2017110.900000) PPP LCP Send Configuration ACK
10:21:24, 17 Jan. (2017110.900000) PPP LCP Receive Configuration Request
10:21:24, 17 Jan. (2017110.890000) PPP LCP Send Configuration Request
10:20:33, 17 Jan. (2017060.160000) PTM over DSL is up
10:06:12, 17 Jan. (2016198.690000) PTM over DSL is down after 1 minutes uptime
10:06:12, 17 Jan. (2016198.690000) PPPoE is down after 0 minutes uptime [Waiting for Underlying Connection (WAN Ethernet 7 -​ Down)]
10:06:08, 17 Jan. (2016195.130000) PPP LCP Send Termination Request [User request]
10:05:42, 17 Jan. (2016169.670000) WAN operating mode is VDSL
10:05:42, 17 Jan. (2016169.660000) Last WAN operating mode was VDSL
10:05:41, 17 Jan. (2016167.890000) PPP IPCP Receive Configuration ACK
10:05:41, 17 Jan. (2016167.890000) PPP IPCP Send Configuration Request
10:05:41, 17 Jan. (2016167.880000) PPP IPCP Receive Configuration NAK
10:05:40, 17 Jan. (2016167.500000) PPP IPCP Send Configuration ACK
10:05:40, 17 Jan. (2016167.490000) PPP IPCP Receive Configuration Request
10:05:40, 17 Jan. (2016167.490000) PPP IPCP Send Configuration Request
10:05:39, 17 Jan. (2016165.900000) PPPoE is up -​ Down Rate=31999Kbps, Up Rate=11530Kbps; SNR Margin Down=-​4.7dB, Up=-​10.8dB
10:05:39, 17 Jan. (2016165.890000) CHAP authentication successful
10:05:39, 17 Jan. (2016165.850000) CHAP Receive Challenge
10:05:39, 17 Jan. (2016165.850000) Starting CHAP authentication with peer
10:05:39, 17 Jan. (2016165.850000) PPP LCP Receive Configuration ACK
10:05:39, 17 Jan. (2016165.850000) PPP LCP Send Configuration Request
10:05:39, 17 Jan. (2016165.840000) PPP LCP Receive Configuration Reject
10:05:39, 17 Jan. (2016165.840000) PPP LCP Send Configuration ACK
10:05:39, 17 Jan. (2016165.840000) PPP LCP Receive Configuration Request
10:05:39, 17 Jan. (2016165.840000) PPP LCP Send Configuration Request
10:04:48, 17 Jan. (2016115.190000) PTM over DSL is up
10:04:06, 17 Jan. (2016072.870000) PTM over DSL is down after 50 minutes uptime
10:04:06, 17 Jan. (2016072.870000) PPPoE is down after 49 minutes uptime [Waiting for Underlying Connection (WAN Ethernet 7 -​ Down)]
10:04:02, 17 Jan. (2016069.360000) PPP LCP Send Termination Request [User request]
09:14:36, 17 Jan. (2013103.560000) WAN operating mode is VDSL
09:14:36, 17 Jan. (2013103.560000) Last WAN operating mode was VDSL
09:14:35, 17 Jan. (2013101.780000) PPP IPCP Receive Configuration ACK
09:14:35, 17 Jan. (2013101.780000) PPP IPCP Send Configuration Request
09:14:35, 17 Jan. (2013101.770000) PPP IPCP Receive Configuration NAK
09:14:35, 17 Jan. (2013101.770000) PPP IPCP Send Configuration ACK
09:14:35, 17 Jan. (2013101.760000) PPP IPCP Receive Configuration Request
09:14:35, 17 Jan. (2013101.760000) PPP IPCP Send Configuration Request
09:14:33, 17 Jan. (2013100.160000) PPPoE is up -​ Down Rate=74443Kbps, Up Rate=18169Kbps; SNR Margin Down=6.0dB, Up=11.1dB
09:14:33, 17 Jan. (2013100.140000) CHAP authentication successful
09:14:33, 17 Jan. (2013100.090000) CHAP Receive Challenge
09:14:33, 17 Jan. (2013100.090000) Starting CHAP authentication with peer
09:14:33, 17 Jan. (2013100.090000) PPP LCP Receive Configuration ACK
09:14:33, 17 Jan. (2013100.080000) PPP LCP Send Configuration Request

[#3]

Wi-Fi log

09:19:05, 27 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
09:16:33, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
09:12:07, 27 Jan. ath10: STA d8:f2:ca:a5:13:56 IEEE 802.11: Client disassociated
09:12:05, 27 Jan. ath10: STA d8:f2:ca:a5:13:56 IEEE 802.11: Client associated
09:11:34, 27 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
09:11:30, 27 Jan. ( 37.040000) WiFi auto selected channel 48
09:11:30, 27 Jan. ( 37.040000) 36-​93::40-​91::44-​91::48-​91::52-​91::56-​90::60-​90::64-​90::100-​92::104-​93::108-​93::112-​94::116-​95::120-​95::124-​94::128-​97
09:11:30, 27 Jan. ( 37.030000) 5 GHz Wireless: Rescan, Reason: 'Power-​up'
09:11:30, 27 Jan. ( 37.030000) WiFi auto selected channel 1
09:11:30, 27 Jan. ( 37.030000) 1-​110::2-​102::3-​107::4-​112::5-​103::6-​104::7-​99::8-​103::9-​111::10-​95::11-​108::12-​117::13-​118
09:11:30, 27 Jan. ( 37.020000) 2.4 GHz Wireless: Rescan, Reason: 'Power-​up'
09:11:22, 27 Jan. ( 29.740000) WPA2 mode selected
09:11:22, 27 Jan. ( 29.740000) WPS enabled
09:11:20, 27 Jan. ( 27.490000) WPA2 mode selected
09:11:20, 27 Jan. ( 27.490000) WPS enabled
08:02:33, 27 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
08:02:27, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client disassociated
07:04:47, 27 Jan. ath00: STA 1c:fe:2b:fd:f7:70 IEEE 802.11: Client disassociated
02:04:39, 27 Jan. ath10: STA 1c:fe:2b:fd:f7:70 IEEE 802.11: WiFi registration failed
02:04:39, 27 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: WiFi registration failed
02:04:39, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: WiFi registration failed
01:30:07, 27 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
01:28:19, 27 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
01:24:04, 27 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
01:22:15, 27 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
01:16:17, 27 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
01:04:44, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
01:01:23, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
01:01:23, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client disassociated
01:00:55, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
00:56:55, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
00:51:03, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
00:47:31, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
00:39:05, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
00:36:37, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
00:36:37, 27 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client disassociated
00:33:04, 27 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
23:23:46, 26 Jan. ath00: STA 1c:fe:2b:fd:f7:70 IEEE 802.11: Client associated
23:23:22, 26 Jan. ath10: STA 1c:fe:2b:fd:f7:70 IEEE 802.11: Client associated
22:49:49, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
19:17:44, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
19:05:52, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
18:21:47, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
18:14:20, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
17:21:31, 26 Jan. ath10: STA d8:f2:ca:a5:13:56 IEEE 802.11: Client disassociated
17:10:26, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
16:41:07, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
16:03:56, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
15:58:29, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
15:22:42, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
15:22:42, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
15:22:14, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
15:15:09, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
14:51:58, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
14:51:58, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
14:51:12, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
14:51:12, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
14:50:08, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
14:31:32, 26 Jan. ath10: STA d8:f2:ca:a5:13:56 IEEE 802.11: Client associated
14:30:40, 26 Jan. ath10: STA d8:f2:ca:a5:13:56 IEEE 802.11: Client disassociated
13:20:37, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
13:20:37, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
13:19:43, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
11:47:29, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
11:46:10, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:42:49, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:36:45, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:36:45, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
10:36:01, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:36:01, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
10:35:48, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:35:48, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
10:35:04, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:35:03, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
10:34:38, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:26:37, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:23:21, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
10:23:21, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client disassociated
10:21:04, 26 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
10:10:13, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
10:10:13, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client disassociated
10:08:50, 26 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
10:06:15, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:06:15, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
10:03:32, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:02:25, 26 Jan. ath00: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
10:02:16, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
10:00:04, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
08:56:33, 26 Jan. ath10: STA d8:f2:ca:a5:13:56 IEEE 802.11: Client associated
08:49:26, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
08:32:33, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
07:18:34, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
07:17:37, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
05:10:32, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
05:09:34, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client associated
03:31:39, 26 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
03:22:30, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
03:08:41, 26 Jan. ath10: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated
03:02:29, 26 Jan. ath10: STA 08:84:9d:5d:4d:4f IEEE 802.11: Client disassociated
02:56:40, 26 Jan. ath00: STA a0:d0:dc:f2:da:5d IEEE 802.11: Client associated

[#4]

Hey @andyt1970,

I'm sorry to hear the Wi-Fi was experiencing some issues this morning. The RADIUS graph basically looks the same as it did yesterday, save for one drop that looks to be a reboot. Was the 4GEE mini router in operation at the time you were experiencing these Wi-Fi signal issues earlier on, or did you only switch back to that in response to the drops?

[#5]

Hi, no. I only put the 4GEE mini router on as I couldn't connect using my Plusnet router and works laptop via wi-fi and needed to work at home. It was only switched on due to not being able to connect using Plusnet wi-fi

It's working now though (Plusnet) so have turned off the 4GEE one and my works laptop and other devices can connect to Plusnet wi-fi. Weird.

I didn't reboot the router btw.

[#6]

No worries then, hopefully this won't be a recurring issue. That being said, if it does seem to happen again, it might be worth observing it for a few days to see if there's any sort of pattern or consistency to the drops.