Broadband dropping intermittently

Fortyfoot

Hi there, we have been away for two weeks and while away the modem was disconnected.

On return when reconnected it dropped intermittently. The same sequence showed on the modem each time it dropped.

https://photos.app.goo.gl/YNYRmQbMszthrvJv7

I was watching streamed football so it was easy to see when it was down, mail and FB would not connect. The EE engineer is calling tomorrow morning and I and asking if there is a simple app which I can put on my laptop which will record when it is dropped. I will not be streaming today, just checking mail & MSE etc.

Intermittent faults never appear when the engineer comes!

Thanks,

Fortyfoot

oldernonethewiser

You could try logging into your router. It should be able to show you when the broadband is connected and when it drops off.


I could certainly do this with a Sky router when I was with them, have had no need since moving.
Sky were also able to tell me that they could see the connection had been failing several times.


The end result of the above was that it was a line fault and a new line was installed by Openreach (no cost to me)

Fortyfoot

Just logged into router, it shows lots of things, it says "connected" but I cannot see any historical info. Thanks,

Fortyfoot

Heedtheadvice

As above.
You normally need to log into your router and access the network or broadband parts ofthe menu to find connection stats which will show current connection quality and then also the event log. That usually shows recent historical status and time on and off line.


Once located if you do not understand the data post on here to get help.


If you struggle to do any of that post on here with the make and model of the router as access procedures and menu selections differ between models but most access is started by typing in the routers IP address into your browser then working your way through the routers resulting internal web page. You will likely need your routers admin username and password often printed on the routers rear (unless it has been changed by someone!) It is not the wireless name/password.

Heedtheadvice

Note you have already logged in so you just need to get access to the deeper levels of data....

Heedtheadvice

Looks like you have a similar router to mine.
When logged in select advanced, left hand menu select system and then system log.



Take care not to select wrong menu items change setting and save or you may upset the works!

Fortyfoot

Yes, very wary about making errors!!!

12:04:20, 28 Oct. PPP: CHAP authentication succeeded
12:04:20, 28 Oct. PPP: LCP up
12:04:16, 28 Oct. PPP: Starting PPP daemon
12:04:14, 28 Oct. WAN link up (ADSL)
12:03:44, 28 Oct. WAN link down (ADSL)
12:03:42, 28 Oct. PPP connection down (ADSL)
12:03:32, 28 Oct. PPP: Stopped PPP daemon(0,1,5)
12:03:26, 28 Oct. PPP: IPCP down
12:03:26, 28 Oct. PPP: LCP down
11:53:33, 28 Oct. Intelligent Wireless Channel Change to 11 (2.4 GHz) Auto Scan - Low Traffic Mode
11:23:21, 28 Oct. Intelligent Wireless Channel Change to 1 (2.4 GHz) Auto Scan - Low Traffic Mode
11:19:47, 28 Oct. Time is synced to NTP server
11:19:33, 28 Oct. PPP connection up (ADSL)
11:19:32, 28 Oct. PPP: IPCP up
11:19:31, 28 Oct. PPP: CHAP authentication succeeded
11:19:31, 28 Oct. PPP: LCP up
11:19:30, 28 Oct. PPP: Starting PPP daemon
11:19:29, 28 Oct. WAN link up (ADSL)
11:18:56, 28 Oct. WAN link down (ADSL)
11:18:55, 28 Oct. PPP connection down (ADSL)
11:18:46, 28 Oct. PPP: Stopped PPP daemon(0,1,5)
11:18:40, 28 Oct. PPP: IPCP down
11:18:40, 28 Oct. PPP: LCP down
11:18:28, 28 Oct. PPP connection up (ADSL)
11:18:28, 28 Oct. PPP: IPCP up
11:18:27, 28 Oct. PPP: CHAP authentication succeeded
11:18:26, 28 Oct. PPP: LCP up
11:18:23, 28 Oct. PPP: Starting PPP daemon
11:18:21, 28 Oct. WAN link up (ADSL)
11:17:50, 28 Oct. WAN link down (ADSL)
11:17:48, 28 Oct. PPP connection down (ADSL)
11:17:38, 28 Oct. PPP: Stopped PPP daemon(0,1,5)
11:17:31, 28 Oct. PPP: IPCP down
11:17:31, 28 Oct. PPP: LCP down
11:09:43, 28 Oct. Time is synced to NTP server
11:08:11, 28 Oct. Intelligent Wireless Channel Change to 6 (2.4 GHz) Auto Scan - Low Traffic Mode
10:09:26, 28 Oct. Time is synced to NTP server
09:13:44, 28 Oct. admin login success from 192.168.1.49
09:09:09, 28 Oct. Time is synced to NTP server
08:08:51, 28 Oct. Time is synced to NTP server
07:08:34, 28 Oct. Time is synced to NTP server
06:08:16, 28 Oct. Time is synced to NTP server
05:07:59, 28 Oct. Time is synced to NTP server
04:07:42, 28 Oct. Time is synced to NTP server
03:07:25, 28 Oct. Time is synced to NTP server
02:07:07, 28 Oct. Time is synced to NTP server
01:06:50, 28 Oct. Time is synced to NTP server
00:06:33, 28 Oct. Time is synced to NTP server
23:06:15, 27 Oct. Time is synced to NTP server
22:05:58, 27 Oct. Time is synced to NTP server
21:05:40, 27 Oct. Time is synced to NTP server
20:24:32, 27 Oct. Device connected: 192.168.1.49, 18:cf:5e:83:32:31, bobacer, lease time is 172800 seconds
20:05:23, 27 Oct. Time is synced to NTP server
19:05:05, 27 Oct. Time is synced to NTP server
18:04:38, 27 Oct. Time is synced to NTP server
17:04:00, 27 Oct. Time is synced to NTP server
16:03:19, 27 Oct. Time is synced to NTP server
16:03:05, 27 Oct. PPP connection up (ADSL)
16:03:04, 27 Oct. PPP: IPCP up
16:03:03, 27 Oct. PPP: CHAP authentication succeeded
16:03:03, 27 Oct. PPP: LCP up
16:02:59, 27 Oct. PPP: Starting PPP daemon
16:02:58, 27 Oct. WAN link up (ADSL)
16:02:16, 27 Oct. WAN link down (ADSL)
16:02:14, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
16:01:57, 27 Oct. PPP: Starting PPP daemon
16:01:56, 27 Oct. WAN link up (ADSL)
16:01:22, 27 Oct. WAN link down (ADSL)
16:01:21, 27 Oct. PPP connection down (ADSL)
16:01:12, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
16:01:06, 27 Oct. PPP: IPCP down
16:01:06, 27 Oct. PPP: LCP down
16:00:55, 27 Oct. PPP connection up (ADSL)
16:00:54, 27 Oct. PPP: IPCP up
16:00:53, 27 Oct. PPP: CHAP authentication succeeded
16:00:53, 27 Oct. PPP: LCP up
16:00:49, 27 Oct. PPP: Starting PPP daemon
16:00:47, 27 Oct. WAN link up (ADSL)
16:00:18, 27 Oct. WAN link down (ADSL)
16:00:16, 27 Oct. PPP connection down (ADSL)
16:00:05, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
15:59:59, 27 Oct. PPP: IPCP down
15:59:59, 27 Oct. PPP: LCP down
15:55:56, 27 Oct. Time is synced to NTP server
15:55:42, 27 Oct. PPP connection up (ADSL)
15:55:42, 27 Oct. PPP: IPCP up
15:55:41, 27 Oct. PPP: CHAP authentication succeeded
15:55:41, 27 Oct. PPP: LCP up
15:55:40, 27 Oct. PPP: Starting PPP daemon
15:55:39, 27 Oct. WAN link up (ADSL)
15:55:05, 27 Oct. WAN link down (ADSL)
15:55:04, 27 Oct. PPP connection down (ADSL)
15:54:55, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
15:54:49, 27 Oct. PPP: IPCP down
15:54:49, 27 Oct. PPP: LCP down
15:43:09, 27 Oct. Time is synced to NTP server
15:42:55, 27 Oct. PPP connection up (ADSL)
15:42:55, 27 Oct. PPP: IPCP up
15:42:54, 27 Oct. PPP: CHAP authentication succeeded
15:42:54, 27 Oct. PPP: LCP up
15:42:52, 27 Oct. PPP: Starting PPP daemon
15:42:51, 27 Oct. WAN link up (ADSL)
15:42:18, 27 Oct. WAN link down (ADSL)
15:42:17, 27 Oct. PPP connection down (ADSL)
15:42:08, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
15:42:02, 27 Oct. PPP: IPCP down
15:42:02, 27 Oct. PPP: LCP down
15:36:52, 27 Oct. Time is synced to NTP server
15:36:38, 27 Oct. PPP connection up (ADSL)
15:36:38, 27 Oct. PPP: IPCP up
15:36:37, 27 Oct. PPP: CHAP authentication succeeded
15:36:37, 27 Oct. PPP: LCP up
15:36:32, 27 Oct. PPP: Starting PPP daemon
15:36:31, 27 Oct. WAN link up (ADSL)
15:35:58, 27 Oct. WAN link down (ADSL)
15:35:57, 27 Oct. PPP connection down (ADSL)
15:35:48, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
15:35:42, 27 Oct. PPP: IPCP down
15:35:42, 27 Oct. PPP: LCP down
15:26:40, 27 Oct. Time is synced to NTP server
15:26:26, 27 Oct. PPP connection up (ADSL)
15:26:25, 27 Oct. PPP: IPCP up
15:26:24, 27 Oct. PPP: CHAP authentication succeeded
15:26:24, 27 Oct. PPP: LCP up
15:26:23, 27 Oct. PPP: Starting PPP daemon
15:26:21, 27 Oct. WAN link up (ADSL)
15:25:51, 27 Oct. WAN link down (ADSL)
15:25:49, 27 Oct. PPP connection down (ADSL)
15:25:39, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
15:25:32, 27 Oct. PPP: IPCP down
15:25:32, 27 Oct. PPP: LCP down
15:04:29, 27 Oct. Time is synced to NTP server
14:04:12, 27 Oct. Time is synced to NTP server
13:59:31, 27 Oct. Device connected: 192.168.1.49, 18:cf:5e:83:32:31, bobacer, lease time is 172800 seconds
13:03:54, 27 Oct. Time is synced to NTP server
12:02:49, 27 Oct. Time is synced to NTP server
12:02:34, 27 Oct. PPP connection up (ADSL)
12:02:34, 27 Oct. PPP: IPCP up
12:02:33, 27 Oct. PPP: CHAP authentication succeeded
12:02:32, 27 Oct. PPP: LCP up
12:02:31, 27 Oct. PPP: Starting PPP daemon
12:02:30, 27 Oct. WAN link up (ADSL)
12:02:00, 27 Oct. WAN link down (ADSL)
12:01:58, 27 Oct. PPP connection down (ADSL)
12:01:48, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
12:01:41, 27 Oct. PPP: IPCP down
12:01:41, 27 Oct. PPP: LCP down
11:34:54, 27 Oct. Time is synced to NTP server
11:34:40, 27 Oct. PPP connection up (ADSL)
11:34:40, 27 Oct. PPP: IPCP up
11:34:39, 27 Oct. PPP: CHAP authentication succeeded
11:34:38, 27 Oct. PPP: LCP up
11:34:37, 27 Oct. PPP: Starting PPP daemon
11:34:36, 27 Oct. WAN link up (ADSL)
11:34:03, 27 Oct. WAN link down (ADSL)
11:34:02, 27 Oct. PPP connection down (ADSL)
11:33:53, 27 Oct. PPP: Stopped PPP daemon(0,1,5)
11:33:46, 27 Oct. PPP: IPCP down
11:33:46, 27 Oct. PPP: LCP down
11:24:25, 27 Oct. Device connected: 192.168.1.49, 18:cf:5e:83:32:31, bobacer, lease time is 172800 seconds
11:12:54, 27 Oct. Time is synced to NTP server
11:12:49, 27 Oct. Device connected: 192.168.1.75, 38:78:62:53:99:67, Unknown Device, lease time is 172800 seconds
11:12:39, 27 Oct. PPP connection up (ADSL)
11:12:38, 27 Oct. PPP: IPCP up
11:12:37, 27 Oct. PPP: CHAP authentication succeeded
11:12:37, 27 Oct. PPP: LCP up
11:12:36, 27 Oct. PPP: Starting PPP daemon
11:12:33, 27 Oct. WAN link up (ADSL)
11:12:13, 27 Oct. System up, firmware version: v0.01.09.0001-OT (Wed Sep 26 16:32:07 2018)
11:11:14, 27 Oct. System start

Reads like a sea saw, up down, up down!

Thanks Heedtheadvice, I have what I need.

Fortyfoot

Heedtheadvice

As you saw that shows lots of 'dropouts' but it does not tell you why.
It would be very worth it, if you have a master socket capable of disconnecting your property and giving access to the test socket, plus if you have a microfilter, plugging your router into the test socket and repeat the exercise looking at the log over time from when connected to the test socket.


Using the service providers side of that demarkation point shows if it is their equipment that is at fault and the cause is not any house wiring etc. Their equipment being the master socket, line to and upstream of exchange equipment and including the filter, cable and router.


Further adding a telephone into circuit and listening for noise would be further info. Line noise is a common cause of what you experience...if I could only remember the silent noise test tel number.......... ah yes Zen have a useful guide at https://support.zen.co.uk/kb/Knowledgebase/Performing-a-Quiet-Line-Test
but of course it works with EE too....

Neil_Jones

Change your filter(s) if you haven't done so already.

hareng

Fortyfoot wrote: »

12:04:20, 28 Oct. PPP: CHAP authentication succeeded
12:04:20, 28 Oct. PPP: LCP up
12:04:16, 28 Oct. PPP: Starting PPP daemon
12:04:14, 28 Oct. WAN link up (ADSL)
12:03:44, 28 Oct. WAN link down (ADSL)
12:03:42, 28 Oct. PPP connection down (ADSL)
12:03:32, 28 Oct. PPP: Stopped PPP daemon(0,1,5)
12:03:26, 28 Oct. PPP: IPCP down
12:03:26, 28 Oct. PPP: LCP down
11:53:33, 28 Oct. Intelligent Wireless Channel Change to 11 (2.4 GHz) Auto Scan - Low Traffic Mode
11:23:21, 28 Oct. Intelligent Wireless Channel Change to 1 (2.4

How far are you from the exchange?
I had much worse than that on ADSL measured dropouts by the thousand a day at 5.5km from exchange. ADSL2+ (LLU) was much better average 1.5meg on a good day. Seemed a lot worse when it rained or snowed.
The other thing due to the dropouts your speed will have significantly been reduced.

As above power off router and leave off for about 10 mins, try router direct in to master no wireless use ethernet.

that

Remove your filter, of the the line that goes from your wall socket to the phone will also connect directly to the modem.

that modem is only used to filter out whistling noises going to your phone. Yes, it maybe impossible to hear what the other side is saying, but for a shortish test it should be ok.

At home i have been running filterless for so many years that I have lost count, and it takes another potential problem out of the loop, but I also do not use my home phone