topic Re: brightbox 2 router keeps dropping out and have to reset in Archived Posts

brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 10:41:51 GMT

My brightbox2 router system log states possible DoS attacks and I keep having to switch router on and off

Re: brightbox 2 router keeps dropping out and have to reset

Mustrum — Thu, 20 May 2021 12:42:06 GMT

@Sangs are they causing you any issues?

If not, just ignore them, the router firewall will be doing its job and stopping them getting through.

Re: brightbox 2 router keeps dropping out and have to reset

XRaySpeX — Thu, 20 May 2021 13:19:51 GMT

Welcome to EE's Home Broadband Forum.

Is it the BB as a whole dropping or just the WiFi connections? What colours are the light sequence when it happens?

If you would like help with your BB speed or connection issues, please would you carry out the following steps for starters, which will enable us to diagnose the problem and advise you further. Do not restart your router to do these tests:

1. Post your full router stats:

For a BrightBox: login and go to Advanced Settings/ System/ DSL Status. Also post 'System Uptime' from top of System Log page.
For a SmartHub: login and go to Advanced Settings/ Technical Log/ Information. Obscure your names & any numbers in the BB Username & also the SSIDs.

Full router stats are key to any speed & connection issues.

2. Try a wired speedtest, using an Ethernet cable supplied with the router, here http://www.thinkbroadband.com/speedtest.html . Click on the "Results Page" button at the bottom of the graph you first see and then copy to here just the "Link to this result:" link that you see below the next main graph.

3. What does BT Wholesale Broadband Availability Checker estimate for your phone number? Post just the whole table and the line above it, blanking out your phone number. If it doesn't recognise your phone number or you don't have one, use the Address Checker, not the Postcode Checker.

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 13:43:04 GMT

The green lights are all on but no internet access is available on our phones or PC or Smart Tvs. I then have to switch the router off and then on again to regain internet access. I thought I may have a faulty router but then looking at the system logs see the message about DoS, although they may be a red herring. Hope you can be of help.

The info you require is:-

System Uptime is: 18:18:36

Current Time/Date is: 14:36:35 20 May

14:36:16, 20 May. admin login success from 192.168.1.116
14:30:33, 20 May. Device connected: 192.168.1.116, a8:5e:45:17:e6:d8, DESKTOP-J2F5T5K, lease time is 172800 seconds
14:29:21, 20 May. Device connected: 192.168.1.201, c6:cc:e7:35:e3:62, Unknown Device, lease time is 172800 seconds
14:06:21, 20 May. Device connected: 192.168.1.244, 1c:12:b0:7d:8f:d6, amazon-df0013e9b, lease time is 172800 seconds
13:40:39, 20 May. Time is synced to NTP server
13:33:58, 20 May. Possible DoS attack detected from 87.237.17.201
13:33:48, 20 May. Possible DoS attack detected from 87.237.17.169
12:40:21, 20 May. Time is synced to NTP server
11:40:04, 20 May. Time is synced to NTP server
11:27:19, 20 May. admin timeout from 192.168.1.116
11:27:19, 20 May. admin logout from 192.168.1.116
11:23:28, 20 May. admin login success from 192.168.1.116
10:39:45, 20 May. Time is synced to NTP server
10:13:07, 20 May. Device connected: 192.168.1.116, a8:5e:45:17:e6:d8, DESKTOP-J2F5T5K, lease time is 172800 seconds
09:55:32, 20 May. Possible DoS attack detected from 184.105.139.81
09:43:06, 20 May. Possible DoS attack detected from 122.228.19.80
09:39:28, 20 May. Time is synced to NTP server
08:56:25, 20 May. Device connected: 192.168.1.201, c6:cc:e7:35:e3:62, Unknown Device, lease time is 172800 seconds
08:39:11, 20 May. Time is synced to NTP server
07:38:55, 20 May. Time is synced to NTP server
07:23:55, 20 May. Device connected: 192.168.1.96, f4:fe:fb:23:4c:39, Samsung, lease time is 172800 seconds
06:38:38, 20 May. Time is synced to NTP server
05:38:22, 20 May. Time is synced to NTP server
04:38:06, 20 May. Time is synced to NTP server
03:57:01, 20 May. Device connected: 192.168.1.96, f4:fe:fb:23:4c:39, Samsung, lease time is 172800 seconds
03:37:50, 20 May. Time is synced to NTP server
03:30:29, 20 May. Possible DoS attack detected from 194.165.16.14
02:37:34, 20 May. Time is synced to NTP server
01:45:41, 20 May. Device connected: 192.168.1.96, f4:fe:fb:23:4c:39, Samsung, lease time is 172800 seconds
01:45:40, 20 May. Device connected: 192.168.1.89, 70:2a:d5:8f:9d:b1, Samsung, lease time is 172800 seconds
01:39:15, 20 May. Possible DoS attack detected from 146.88.240.4
01:37:45, 20 May. Possible DoS attack detected from 194.165.16.10
01:37:17, 20 May. Time is synced to NTP server
00:37:01, 20 May. Time is synced to NTP server
00:36:48, 20 May. PPP connection up (FIBRE)
00:36:48, 20 May. PPP: IPCP up
00:36:47, 20 May. PPP: CHAP authentication succeeded
00:36:47, 20 May. PPP: LCP up
00:36:47, 20 May. PPP: Received PADS
00:36:47, 20 May. PPP: Sending PADR
00:36:47, 20 May. PPP: Received PADO
00:36:47, 20 May. PPP: Sending PADI
00:36:42, 20 May. PPP: Sending PADI
00:36:37, 20 May. PPP: Sending PADI
00:36:32, 20 May. PPP: Sending PADI
00:36:27, 20 May. PPP: Sending PADI
00:36:22, 20 May. PPP: Sending PADI
00:36:17, 20 May. PPP: Sending PADI
00:36:17, 20 May. PPP: Starting PPP daemon
00:36:16, 20 May. WAN link up (FIBRE)
00:36:04, 20 May. WAN link down (FIBRE)
00:36:03, 20 May. PPP connection down (FIBRE)
00:35:52, 20 May. PPP: Stopped PPP daemon(0,1,5)
00:35:46, 20 May. PPP: IPCP down
00:35:46, 20 May. PPP: LCP down
00:20:54, 20 May. Time is synced to NTP server
23:59:58, 19 May. Device connected: 192.168.1.89, 70:2a:d5:8f:9d:b1, Samsung, lease time is 172800 seconds
23:55:45, 19 May. Possible DoS attack detected from 122.228.19.80
23:55:27, 19 May. Device connected: 192.168.1.89, 70:2a:d5:8f:9d:b1, Samsung, lease time is 172800 seconds
23:55:26, 19 May. Device connected: 192.168.1.96, f4:fe:fb:23:4c:39, Samsung, lease time is 172800 seconds
23:52:23, 19 May. Possible DoS attack detected from 219.147.112.250
23:52:23, 19 May. Possible DoS attack detected from 219.147.112.250
23:40:58, 19 May. Possible DoS attack detected from 194.165.16.14
23:32:25, 19 May. Possible DoS attack detected from 194.165.16.10
23:20:37, 19 May. Time is synced to NTP server
22:20:20, 19 May. Time is synced to NTP server
22:06:28, 19 May. Device connected: 192.168.1.116, a8:5e:45:17:e6:d8, DESKTOP-J2F5T5K, lease time is 172800 seconds
22:03:18, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:18, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:18, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:18, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:18, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:18, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:08, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:08, 19 May. Possible DoS attack detected from 89.248.165.97
22:03:08, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:57, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:57, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:57, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:47, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:47, 19 May. Possible DoS attack det
22:02:47, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:47, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:47, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:47, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:44, 19 May. Device connected: 192.168.1.201, c6:cc:e7:35:e3:62, Unknown Device, lease time is 172800 seconds
22:02:37, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:37, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:37, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:37, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:37, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:27, 19 May. Possible DoS attack det
22:02:27, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:27, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:27, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:27, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:27, 19 May. Possible DoS attack detected from 89.248.165.97
22:02:17, 19 May. Possible DoS attack detected from 89.248.165.97
21:20:03, 19 May. Time is synced to NTP server
20:44:59, 19 May. Device connected: 192.168.1.96, f4:fe:fb:23:4c:39, Samsung, lease time is 172800 seconds
20:40:33, 19 May. admin logout from 192.168.1.116
20:29:42, 19 May. admin login success from 192.168.1.116
20:23:50, 19 May. Device connected: 192.168.1.116, a8:5e:45:17:e6:d8, DESKTOP-J2F5T5K, lease time is 172800 seconds
20:23:48, 19 May. Device connected: 192.168.1.31, b4:7c:9c:6f:99:39, amazon-d5593538f, lease time is 172800 seconds
20:21:54, 19 May. Device connected: 192.168.1.191, cc:61:e5:cf:0f:5e, android-9198d4a0bc52e069, lease time is 172800 seconds
20:20:57, 19 May. Device connected: 192.168.1.201, c6:cc:e7:35:e3:62, Unknown Device, lease time is 172800 seconds
20:20:07, 19 May. Device connected: 192.168.1.31, b4:7c:9c:6f:99:39, amazon-d5593538f, lease time is 172800 seconds
20:19:49, 19 May. Device connected: 192.168.1.244, 1c:12:b0:7d:8f:d6, amazon-df0013e9b, lease time is 172800 seconds
20:19:47, 19 May. Time is synced to NTP server
20:19:44, 19 May. Device connected: 192.168.1.191, cc:61:e5:cf:0f:5e, android-9198d4a0bc52e069, lease time is 172800 seconds
20:19:33, 19 May. PPP connection up (FIBRE)
20:19:33, 19 May. PPP: IPCP up
20:19:32, 19 May. PPP: CHAP authentication succeeded
20:19:32, 19 May. PPP: LCP up
20:19:32, 19 May. PPP: Received PADS
20:19:32, 19 May. PPP: Sending PADR
20:19:32, 19 May. PPP: Received PADO
20:19:32, 19 May. PPP: Sending PADI
20:19:27, 19 May. PPP: Sending PADI
20:19:22, 19 May. PPP: Sending PADI
20:19:17, 19 May. PPP: Sending PADI
20:19:12, 19 May. PPP: Sending PADI
20:19:12, 19 May. PPP: Starting PPP daemon
20:19:09, 19 May. WAN link up (FIBRE)
20:19:06, 19 May. System up, firmware version: v0.06.00.0001-OT (Tue May 19 15:34:07 2020)
20:18:24, 19 May. System start
00:21:47, 01 Jan. Device connected: 192.168.1.79, 00:bb:3a:a3:a9:9e, Unknown Device, lease time is 172800 seconds
00:21:36, 01 Jan. Device connected: 192.168.1.79, 00:bb:3a:a3:a9:9e, Unknown Device, lease time is 172800 seconds
00:21:25, 01 Jan. Device connected: 192.168.1.79, 00:bb:3a:a3:a9:9e, Unknown Device, lease time is 172800 seconds
00:21:14, 01 Jan. Device connected: 192.168.1.79, 00:bb:3a:a3:a9:9e, Unknown Device, lease time is 172800 seconds
00:21:04, 01 Jan. Device connected: 192.168.1.79, 00:bb:3a:a3:a9:9e, Unknown Device, lease time is 172800 seconds
00:20:53, 01 Jan. Device connected: 192.168.1.79, 00:bb:3a:a3:a9:9e, Unknown Device, lease time is 172800 seconds
00:02:14, 01 Jan. Device connected: 192.168.1.201, c6:cc:e7:35:e3:62, Unknown Device, lease time is 172800 seconds
00:02:03, 01 Jan. Device connected: 192.168.1.31, b4:7c:9c:6f:99:39, amazon-d5593538f, lease time is 172800 seconds
00:01:46, 01 Jan. Device connected: 192.168.1.191, cc:61:e5:cf:0f:5e, android-9198d4a0bc52e069, lease time is 172800 seconds
00:01:17, 01 Jan. Device connected: 192.168.1.89, 70:2a:d5:8f:9d:b1, Samsung, lease time is 172800 seconds
00:01:15, 01 Jan. Device connected: 192.168.1.244, 1c:12:b0:7d:8f:d6, amazon-df0013e9b, lease time is 172800 seconds
00:01:07, 01 Jan. System up, firmware version: v0.06.00.0001-OT (Tue May 19 15:34:07 2020)
00:00:26, 01 Jan. System start
19:09:58, 19 May. WAN link down (FIBRE)
19:09:57, 19 May. PPP connection down (FIBRE)
19:09:47, 19 May. PPP: Stopped PPP daemon(0,1,5)
19:09:41, 19 May. PPP: IPCP down
19:09:41, 19 May. PPP: LCP down

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 13:47:51 GMT

no issues with the Dos messages, but the router drops out despite all the lights being green, I then have to reboot the router.

Re: brightbox 2 router keeps dropping out and have to reset

XRaySpeX — Thu, 20 May 2021 14:00:48 GMT

Sorry, that's not the info I requested. The System Log is of no use.

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 14:34:02 GMT

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 14:36:44 GMT

Is this what you mean?

System Uptime is: 19:18:28 Current Time/Date is: 15:36:26 20 May

Re: brightbox 2 router keeps dropping out and have to reset

Mustrum — Thu, 20 May 2021 14:39:12 GMT

@Sangs you need to wait for a mod to approve the pics before they can be seen.

Re: brightbox 2 router keeps dropping out and have to reset

XRaySpeX — Thu, 20 May 2021 14:45:50 GMT

Yes, thanks, that's 1 out of 3. I'll await the rest.

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 14:53:36 GMT

https://www.thinkbroadband.com/speedtest/1621522263466538255

Re: brightbox 2 router keeps dropping out and have to reset

XRaySpeX — Thu, 20 May 2021 15:30:33 GMT

Locate the hidden test socket that is revealed when you remove the bottom half of the split faceplate (2 screws or press tabs) of your master socket. Only do this if you have a split faceplate. Do you have any extension sockets in the home even if unused? Are there any wires connected to back of faceplate of master socket?

Try the BT Quiet Line Test (QLT), dial 17070 Opt 2, preferably with a corded phone, in the test socket with the router disconnected. If there is any noise, report it to your landline provider as a voice fault (don't mention Broadband). Often sorting out voice faults will fix the Broadband as well.

Reboot the router & plug it into the test socket. Post the full router stats & System Uptime when plugged into test socket.

Is the issue any better?

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 16:43:42 GMT

Thanks for your help, about 5 minutes after your last reply my router went off with a solid red broadband light. I tried the quiet line test and there wasn't a sound so I think that is OK. I tried plugging the router into the test socket but the red broadband light persisted. I've let the router cool down and plugged it back into it's normal position and everything is back to normal. I think I have a faulty router and will give EE a call to see if they can send me a new one. The problems have only started in the last two weeks and the router is at least six years old. Once again thanks for your help and I'll let you know what happens with a new router.

Re: brightbox 2 router keeps dropping out and have to reset

XRaySpeX — Thu, 20 May 2021 16:46:33 GMT

What are the router stats now?

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 20:36:33 GMT

Sorry for the delay, it dropped out again and I had to wait before connecting.

https://www.thinkbroadband.com/speedtest/1621542633463328555

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Thu, 20 May 2021 20:37:29 GMT

Sorry forgot this.

System Uptime is: 00:16:29

Current Time/Date is: 21:36:55 20 May

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Sat, 22 May 2021 12:59:15 GMT

Have spoken to EE and it looks like there may be a fault on the line. An engineer has been booked for Monday to investigate. EE are also talking about replacing my router as I have have had it for so long. Thanks again for all your help in this matter. I'll let you know the outcome of the engineers visit.

Re: brightbox 2 router keeps dropping out and have to reset

Sangs — Mon, 24 May 2021 16:18:33 GMT

Just to finish off, there was a fault on the line which BT have repaired and the BT engineer is going to recommend a new router due to the age of my Brightbox 2 and the fact that it appears to be overheating. Thank you all for your advice.

Re: brightbox 2 router keeps dropping out and have to reset

XRaySpeX — Mon, 24 May 2021 16:46:40 GMT

Thanks! You're welcome 🙂 ! Glad I could be of assistance & it is now sorted.