Re: Broadband Dropping Out Approx Every 24hrs

pscraven · ‎22-02-2023

Hello, I have a repeating issue with my Broadband and I'm struggling to get a satisfactory resolution via normal BT support routes so coming here for help (pretty please).

I've had reliable BT Fibre 2 for a couple of years approx 70Mb (Down), 20Mb (UP). At Christmas I was cut off by BT in error and service restored by BT on 6th Jan 2023. The new service is the same Fibre 2 under a new account but this time BB only service (ie no telephone).

Since 6th Jan, my broadband now drops every day for about 5 mins, usually around the same time 12:15- 12:30. I have tried several things and had several BT visits to look at the router and the line. The line checks out OK and I have removed a couple of devices from ethernet ports as the OpenReach engineer suggested doing so (not entirely sure why?).

Night before last night at 11pm reset my router to factory default to see if the problem reoccurred at either the same time or after 24hrs. Result was it went down again today at the same time (12:05:26 to be precise).

BT seem a little reluctant to investigate the router logs which surprises me and instead are suggesting it may be electrical interference or something they refer to as 'RAIN'. My suspicion is the problem is either in the home with a rogue device or with the switch in the street. Please can anyone interrogate the logs to see what's going on and provide any simple advice on what to look at next? I will add the logs to the post shortly. Thanks in advance!

pscraven · ‎22-02-2023

12:13:22 22 Feb. WHW INFO A station STA(1A:99:41:26:32:F8) leave WHW infrastructure
12:08:57 22 Feb. ARP [add] br0(wds0.4.9) 192.168.1.116 1a:99:41:26:32:f8
12:08:46 22 Feb. DHCP device Connected: 192.168.1.116
12:08:46 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:08:45 22 Feb. LAN [ADD] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0(wds0.4.9)
12:08:45 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:08:45 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:08:45 22 Feb. WHW INFO A station (Upstairs)IF[5G](4C:1B:86:CE:40:04):STA(1A:99:41:26:32:F8) join WHW infrastructure
12:08:45 22 Feb. Receive a DHCP request
12:06:47 22 Feb. NTP synchronization success
12:06:47 22 Feb. NTP Server: ntp.homehub.btopenworld.com
12:06:41 22 Feb. LTE Modem owl_tx_lte_set_rate_shaper_script command sent
12:06:39 22 Feb. LTE Modem owl_tx_lte_set_rate_shaper_script command sent
12:06:39 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:06:36 22 Feb. DHCP device Disconnected: 192.168.1.116
12:06:36 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:06:36 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:06:36 22 Feb. LAN [DEL] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0
12:06:36 22 Feb. WAN Sensing Auto sensing Complete
12:06:36 22 Feb. WAN Sensing Auto sensing Running
12:06:34 22 Feb. NTP synchronization start
12:06:34 22 Feb. WAN IPv6 Global unicast prefix / length: 2a00:23c6:bb25:b500::/56
12:06:34 22 Feb. WAN IPv6 Global unicast address allocated: 2a00:23c6:bb25:b500::1/64
12:06:34 22 Feb. WAN DHCPv6 events: BOUND
12:06:33 22 Feb. WAN DHCPv6 events: INIT
12:06:33 22 Feb. WAN Sensing Auto sensing Complete
12:06:33 22 Feb. WAN Sensing Auto sensing Running
12:06:33 22 Feb. Success - secondary DNS servers
12:06:33 22 Feb. Success - primary DNS servers
12:06:33 22 Feb. WAN connection WAN2_INTERNET_PTM connected
12:06:32 22 Feb. PPP: IPCP up
12:06:32 22 Feb. PPP IPCP Receive Configuration ACK
12:06:32 22 Feb. PPP IPV6CP Receive Configuration ACK
12:06:32 22 Feb. PPP IPCP Send Configuration Request
12:06:32 22 Feb. PPP IPCP Receive Configuration NAK
12:06:32 22 Feb. PPP IPCP Send Configuration ACK
12:06:32 22 Feb. PPP IPCP Receive Configuration Request
12:06:32 22 Feb. PPP IPV6CP Send Configuration ACK
12:06:32 22 Feb. PPP IPV6CP Receive Configuration Request
12:06:32 22 Feb. PPP IPV6CP Send Configuration Request
12:06:32 22 Feb. PPP IPCP Send Configuration Request
12:06:32 22 Feb. PPP: CHAP authentication succeeded
12:06:32 22 Feb. PPP CHAP Receive success : authentication successful
12:06:32 22 Feb. PPP CHAP Receive Challenge
12:06:32 22 Feb. PPP: LCP up
12:06:32 22 Feb. PPP LCP Receive Configuration ACK
12:06:32 22 Feb. PPP LCP Send Configuration ACK
12:06:31 22 Feb. ARP [del] br0 192.168.1.116 1a:99:41:26:32:f8
12:06:31 22 Feb. PPP LCP Receive Configuration Request
12:06:31 22 Feb. PPP LCP Send Configuration Request
12:06:31 22 Feb. PPP: Received PADS
12:06:31 22 Feb. PPP: Sending PADR
12:06:31 22 Feb. PPP: Received PADO
12:06:31 22 Feb. PPP: Sending PADI
12:06:26 22 Feb. PPP: Sending PADI
12:06:21 22 Feb. PPP: Sending PADI
12:06:16 22 Feb. PPP: Sending PADI
12:06:13 22 Feb. DSL Link Up: Down Rate=69426kbps
12:06:13 22 Feb. WHW INFO A station (Upstairs)IF[5G](4C:1B:86:CE:40:04):STA(8C:17:59:4C:81:82) join WHW infrastructure
12:06:13 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:06:13 22 Feb. Receive a DHCP request
12:06:11 22 Feb. PPP: Sending PADI
12:06:08 22 Feb. WHW INFO A station STA(8C:17:59:4C:81:82) leave WHW infrastructure
12:06:06 22 Feb. PPP: Starting PPP daemon
12:06:05 22 Feb. WAN Auto-sensing detected port DSL WAN
12:05:57 22 Feb. WHW INFO A station STA(1A:99:41:26:32:F8) leave WHW infrastructure
12:05:53 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:05:53 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:05:53 22 Feb. WHW INFO A station (Upstairs)IF[5G](4C:1B:86:CE:40:04):STA(8C:17:59:4C:81:82) join WHW infrastructure
12:05:53 22 Feb. Lan IPv6 Neighbour Discovery events: NEIGHBOR_SOLICIT
12:05:52 22 Feb. Receive a DHCP request
12:05:52 22 Feb. WHW INFO A station STA(8C:17:59:4C:81:82) leave WHW infrastructure
12:05:38 22 Feb. SIP WAN DOWN
12:05:30 22 Feb. SIP WAN DOWN
12:05:30 22 Feb. WAN Sensing Auto sensing Complete
12:05:30 22 Feb. WAN Sensing Auto sensing Running
12:05:28 22 Feb. WAN Sensing Auto sensing Complete
12:05:28 22 Feb. WAN Sensing Auto sensing Running
12:05:28 22 Feb. WAN connection WAN2_INTERNET_PTM disconnected.[ERROR_NO_CARRIER]
12:05:27 22 Feb. PPP: Stopped PPP daemon(0
12:05:27 22 Feb. PPP LCP Send Termination Request (User request)
12:05:26 22 Feb. PPP: IPCP down
12:05:26 22 Feb. PPP: LCP down
12:05:26 22 Feb. DSL Link Down: duration was 84626 seconds
12:05:23 22 Feb. WHW INFO A station (Upstairs)IF[5G](4C:1B:86:CE:40:04):STA(1A:99:41:26:32:F8) join WHW infrastructure
12:03:31 22 Feb. DHCP device Connected: 192.168.1.116
12:03:31 22 Feb. LAN [ADD] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0(wds0.4.7)
12:03:31 22 Feb. ARP [add] br0(wds0.4.7) 192.168.1.116 1a:99:41:26:32:f8
12:03:15 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:02:55 22 Feb. WHW INFO A station (Loft)IF[5G](F0:86:20:87:DA:C6):STA(1A:99:41:26:32:F8) join WHW infrastructure
12:02:54 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
12:02:31 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:02:09 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
12:02:07 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:02:06 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
12:02:04 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:02:00 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
12:01:58 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:01:57 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
12:01:55 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:01:48 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
12:01:23 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
12:00:29 22 Feb. DHCP device Connected: 192.168.1.116
12:00:29 22 Feb. LAN [ADD] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0(wds0.4.9)
12:00:29 22 Feb. ARP [add] br0(wds0.4.9) 192.168.1.116 1a:99:41:26:32:f8
12:00:16 22 Feb. WHW INFO A station (Upstairs)IF[5G](4C:1B:86:CE:40:04):STA(1A:99:41:26:32:F8) join WHW infrastructure
11:58:18 22 Feb. DHCP device Connected: 192.168.1.116
11:58:18 22 Feb. LAN [ADD] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0(wds0.4.7)
11:58:18 22 Feb. ARP [add] br0(wds0.4.7) 192.168.1.116 1a:99:41:26:32:f8
11:58:15 22 Feb. WHW INFO A station (Loft)IF[5G](F0:86:20:87:DA:C6):STA(1A:99:41:26:32:F8) join WHW infrastructure
11:54:00 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
11:53:59 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
11:51:15 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
11:51:14 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
11:48:18 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
11:48:17 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
11:47:59 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
11:47:58 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
11:38:02 22 Feb. 2.4G Client associate from d4:91:0f:3b:80:db (IP=192.168.1.140) RSSI=-59
11:38:02 22 Feb. Receive a DHCP request
11:31:20 22 Feb. 2.4G Client associate from 74:ab:93:be:2e:37 (IP=192.168.1.190) RSSI=-74
11:31:20 22 Feb. Receive a DHCP request
11:31:02 22 Feb. WHW INFO A station STA(1A:99:41:26:32:F8) leave WHW infrastructure
11:27:40 22 Feb. 2.4G Client disassociate from 1a:99:41:26:32:f8 (IP=192.168.1.116) RSSI=0
11:27:38 22 Feb. WHW INFO A station STA(1A:99:41:26:32:F8) leave WHW infrastructure
11:27:38 22 Feb. 2.4G client Mac: 1A:99:41:26:32:F8 Deauthentications (Reason:Disassociated due to inactivity )
11:26:15 22 Feb. DHCP device Connected: 192.168.1.116
11:26:15 22 Feb. LAN [ADD] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0(wds0.4.9)
11:26:15 22 Feb. ARP [add] br0(wds0.4.9) 192.168.1.116 1a:99:41:26:32:f8
11:26:09 22 Feb. WHW INFO A station (Upstairs)IF[5G](4C:1B:86:CE:40:04):STA(1A:99:41:26:32:F8) join WHW infrastructure
11:23:32 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
11:23:28 22 Feb. Port forwarding rule added via UPnP/TR064. Protocol: UDP
11:23:27 22 Feb. Port forwarding rule deleted via UPnP/TR064. Protocol: UDP
11:23:12 22 Feb. DHCP device Connected: 192.168.1.116
11:23:12 22 Feb. LAN [ADD] ARP 192.168.1.116 with 1a:99:41:26:32:f8 from br0(wl1)
11:23:12 22 Feb. ARP [add] br0(wl1) 192.168.1.116 1a:99:41:26:32:f8
11:23:03 22 Feb. WHW INFO A station (Smart Hub 2)IF[2.4G](18:82:8C:6F:63:19):STA(1A:99:41:26:32:F8)(Legacy Device) join WHW infrastructure

licquorice · ‎22-02-2023

The logs won't give any indication as to the cause of the problem, all they do is confirm the date and time of the disconnection.

It is possible that it is REIN (repetitive electrical impulse noise) that is causing your problem.

It's an odd time, but do you have any electrical items switching on or off at that time?

pscraven · ‎22-02-2023

Thanks for the response, nothing locally switching on/off within the home at that time. The logs confirm it is a daily occurrence, but the time does differ slightly each day (+/- approx 30 mins). I agree that REIN (thanks for the explanation) could be a cause however it wasn't an issue prior to 6th Jan 2023 when my service was reinstated. That could be a coincidence, but feels unlikely as its pretty much like clock work every day now and yet was rock solid prior to that. The only difference in the service I can see is its now BB only. Do the logs not contain any useful information prior to the disconnect? I also wonder if this effects my neighbours and if there is any data available to BT to identify as such?

licquorice · ‎22-02-2023

No,the logs won't give any indication of a line dropping other than the drop itself..

12:05:26 22 Feb. DSL Link Down: duration was 84626 seconds is the only indication and it shows a line drop that restores 12:06:13 22 Feb. DSL Link Up: Down Rate=69426kbps

pscraven · ‎22-02-2023

Hi again, the below shows the drop time, date and duration. As you can see its pretty much daily (odd exceptions included). The duration doesn't make a lot of sense unless they're milliseconds.

12:05:26	22 Feb.	DSL Link Down: duration was 84626 seconds
12:34:23	21 Feb.	DSL Link Down: duration was 35200 seconds
02:47:14	21 Feb.	DSL Link Down: duration was 11370 seconds
12:50:06	20 Feb.	DSL Link Down: duration was 120216 seconds
03:26:05	19 Feb.	DSL Link Down: duration was 54059 seconds
12:24:28	18 Feb.	DSL Link Down: duration was 84017 seconds
13:03:34	17 Feb.	DSL Link Down: duration was 42013 seconds
01:22:42	17 Feb.	DSL Link Down: duration was 44135 seconds
13:06:29	16 Feb.	DSL Link Down: duration was 86572 seconds
13:02:59	15 Feb.	DSL Link Down: duration was 9969 seconds
10:16:25	15 Feb.	DSL Link Down: duration was 2742 seconds
08:19:23	15 Feb.	DSL Link Down: duration was 64214 seconds
14:28:34	14 Feb.	DSL Link Down: duration was 67192 seconds
19:48:04	13 Feb.	DSL Link Down: duration was 94138 seconds
14:49:45	12 Feb.	DSL Link Down: duration was 92795 seconds
13:02:32	11 Feb.	DSL Link Down: duration was 85625 seconds
13:14:49	10 Feb.	DSL Link Down: duration was 86073 seconds
13:19:29	09 Feb.	DSL Link Down: duration was 86031 seconds
13:25:01	08 Feb.	DSL Link Down: duration was 85467 seconds
13:39:56	07 Feb.	DSL Link Down: duration was 87732 seconds
13:17:06	06 Feb.	DSL Link Down: duration was 85118 seconds
13:37:52	05 Feb.	DSL Link Down: duration was 76663 seconds
13:36:06	04 Feb.	DSL Link Down: duration was 8236 seconds
13:50:50	03 Feb.	DSL Link Down: duration was 86739 seconds
13:44:33	02 Feb.	DSL Link Down: duration was 86360 seconds
13:44:35	01 Feb.	DSL Link Down: duration was 85923 seconds
13:51:54	31 Jan.	DSL Link Down: duration was 87109 seconds
13:39:27	30 Jan.	DSL Link Down: duration was 85728 seconds
13:50:00	29 Jan.	DSL Link Down: duration was 86164 seconds
13:53:18	28 Jan.	DSL Link Down: duration was 87401 seconds
13:35:59	27 Jan.	DSL Link Down: duration was 86030 seconds
13:41:23	26 Jan.	DSL Link Down: duration was 89752 seconds
12:44:44	25 Jan.	DSL Link Down: duration was 85347 seconds
13:01:39	24 Jan.	DSL Link Down: duration was 86984 seconds
12:51:17	23 Jan.	DSL Link Down: duration was 85802 seconds
13:00:34	22 Jan.	DSL Link Down: duration was 87081 seconds
12:48:35	21 Jan.	DSL Link Down: duration was 56581 seconds
21:04:47	20 Jan.	DSL Link Down: duration was 25423 seconds
14:03:40	19 Jan.	DSL Link Down: duration was 90570 seconds
12:53:31	18 Jan.	DSL Link Down: duration was 37659 seconds
02:25:27	18 Jan.	DSL Link Down: duration was 51548 seconds
12:05:41	17 Jan.	DSL Link Down: duration was 8756 seconds

rbz5416 · ‎22-02-2023

Duration is uptime since the last disconnect.

pscraven · ‎22-02-2023

Ok thanks. So its an approximate time of day issue not an exact time of day one. I would have thought if it were a issue related to a timer it would be exact rather than approximate? Therefore it could be another trigger such as a sensor? Is there a BT helpdesk of forum related to REIN does anyone know?

rbz5416 · ‎22-02-2023

When you were reconnected did you retain the same Hub or get a new one?

If it's the same Hub that does rather suggest the line rather than the local environment. If you haven't already you could try relocating the Hub to a different room with a longer RJ11 cable.

An AM radio may indicate a REIN problem:

https://kitz.co.uk/adsl/rein.htm

You could also try turning off all appliances, including central heating for an hour or two either side of the problem time to see if that helps.

kamen · ‎22-02-2023

Hi @pscraven , I'm having the same problem since mid December. I then switched from BT to Sky and the problem started. I thought that switching back to BT would solve the problem, but it hasn't.

With me the drops are around 11-12 in the morning and last for a minute. The log file from the router shows the same.

BT engineer came last week and changed the socket on the wall, but that hasn't fixed anything. I'm now trying with the router at the different place in the room, but no difference. Tomorrow morning I plan to disconnect the ethernet cables from the router and see if that makes any difference.

Could we be neighbours? I'm in Milton Keynes.