This topic

Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Sat, 23 May 2020 19:10:14 GMT

Multiple dropouts every day (6 so far today, same on the 19th, usually 3 or 4 each day) on

Exchange name: Locks Heath
Exchange code: STLOCKH

Router light changes from blue to solid orange and about half the time, requires to be physically switched off/restarted, the rest of the time it restarts via the BT Smart Hub Manager. Every once in a while however, the lights are either solid orange, or solid green. I've raised 2 vol complaints but had no contact - I appreciate C19 issues mean I am not the priority.

Note the date change from today to the 01 Jan:

14:13:17, 23 May.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

14:13:17, 23 May.

ppp1:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

00:02:18, 01 Jan.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

00:02:13, 01 Jan.

ppp1:PPP: PPP INFO

00:02:09, 01 Jan.

ppp:PPP: IPCP_NAK

00:02:08, 01 Jan.

ppp:PPP: CHAP_SUCCESS

00:02:08, 01 Jan.

ppp:PPP: CHAP_RESPONSE

00:02:08, 01 Jan.

ppp:PPP: LCP_GOOD_ACK

00:02:06, 01 Jan.

ppp:PPP: LCP_REQUEST

18:04:36, 22 May.

:PPPoE error: timeout

18:04:28, 22 May.

:PPPoE error: timeout

18:04:24, 22 May.

:PPPoE error: timeout

18:02:44, 22 May.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

18:02:43, 22 May.

ppp1:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

17:50:43, 22 May.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

17:50:43, 22 May.

ppp1:PPP: PPP INFO

17:50:43, 22 May.

ppp:PPP: IPCP_NAK

17:50:43, 22 May.

ppp:PPP: CHAP_SUCCESS

17:50:42, 22 May.

ppp:PPP: CHAP_RESPONSE

17:50:42, 22 May.

ppp:PPP: LCP_GOOD_ACK

17:50:42, 22 May.

ppp:PPP: LCP_REQUEST

17:50:42, 22 May.

:PPPoE error: timeout

17:50:26, 22 May.

:PPPoE error: timeout

17:50:18, 22 May.

:PPPoE error: timeout

17:50:14, 22 May.

:PPPoE error: timeout

17:49:26, 22 May.

:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

17:49:26, 22 May.

ppp1:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Starwire — Sun, 24 May 2020 05:45:40 GMT

You say that Openreach can never trace the fault. Has an Openreach Engineer(s) been out because you said you faults/complaints but they’ve gone unanswered?

Do you have any noise on the line? If so depending on what kind of noise there might be a HR or Contact fault, which I’ll play havoc with your connection.

Get a known working phone, preferably a corded one, plug it in, ring 17070 and use option 2 for the quiet line test. Check for noise. Normal to heard a faint electrical humming noise, you need to listen out for crackling noises or loud Earthing Noise.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

TNT555 — Sun, 24 May 2020 09:11:53 GMT

I've been having very similar issues here.

had 2 dropout today so far. on downstream from the Southampton area on STLYMTN.

Not using a BT resethub here.

My Modem has been up for days , but the PPP session keep dropping off on the router. but I need to reboot the router to get the PPP session to come back up.

OR would have to gather the data from ISP's so I wonder if anything has been flagged for OR to react too yet.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

pippincp — Sun, 24 May 2020 10:14:32 GMT

What data do you think OR need to gather from an ISP?

Have you conducted a quiet line test?

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Sun, 24 May 2020 16:44:36 GMT

All I get is a pre recorded msg. This number does nor accept income calls.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

pippincp — Sun, 24 May 2020 17:06:23 GMT

It is a quiet line test. Was the line silent between announcements?

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Starwire — Sun, 24 May 2020 17:16:08 GMT

Whose your telephone provider, BT?

The 17070 Fast Test System should work on all WLR3 Lines.

Even the LLU Providers except Vodafone have 17070 as their Fast Test Number.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Sun, 24 May 2020 17:17:07 GMT

There wasn't an option 2 to select.

Line seemed quiet but i do know that at times our line is quite noisy.

When we've had OR engineers out before, they always decry that an intermittent fault can't be found. issue (after a visit) goes away for a while, but returns between a week and a moth later.

I raised the first two of my current fault reports (with VOL numbers) as per opening post - not received any feedback for it and the fault tracking shows it has passed it's resolution date without action.

When everything is working as expected (and as per contract) I get a good 54MB upload speed which is the mon my line claims it should be supporting. Currently report 40mb.

Today one drop out so far, yesterday 5 (Reboot,Reconfiguration,forced termination).

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Sun, 24 May 2020 17:23:07 GMT

We're with BT

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Tue, 26 May 2020 08:38:09 GMT

I've also bought a new micro-filter because the call centre suggested this would help when the same issue was occurring previously.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

TNT555 — Tue, 26 May 2020 09:25:22 GMT

In this case PPPoE session logs from both the BT end and the router.

Like I said and the point seems to have been missed somehow, it's even there in the logs, the PPPoE session is dropping not the VDSL line.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Tue, 26 May 2020 09:40:57 GMT

Hi - apologies but I don't know what that means.

I created manually the log files to show only the PPPoE - there is no option to select VDSL on my BT router.

Also, why do the router logs for UPNP/DNS show a change of date to 01 JAN.

00:01:49, 01 Jan.

BR_LAN:UPnP functionality has been activated

00:01:49, 01 Jan.

BR_LAN:UPnP functionality has been deactivated (manually)

00:00:55, 01 Jan.

BR_LAN:UPnP functionality has been activated

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

TNT555 — Tue, 26 May 2020 11:06:35 GMT

The Hub might not have picked up the time from the NTP server, or just kept the logs relative to the default time from when the hub was switched on.

You can get a good idea if the VDSL line droped from the technical info, I have no idea if the recent BT smart hubs reset the Connection uptime on DSL, PPPOE or both. if the time exceeds the last PPPoE drop is safe to assume that the DSL up time exceeds the PPPoE session.

The normal reason for a PPPoE session to drop is the DSL line dropping out or erroring.

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Tue, 26 May 2020 11:14:42 GMT

would it help if I posted all the router info from the time of the drop out, instead of only the PPPoE which is what I filtered on?

Router Stats?

11:12:51, 25 May.

dsl:VDSL Link Down: duration was 1007 seconds

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

CJT80 — Tue, 26 May 2020 11:15:04 GMT

@Hangerheadwrote:
All I get is a pre recorded msg. This number does nor accept income calls.

Just to check you dialled: 17070? You should get "this circuit is defined as (will read out your landline number) , welcome to your Openreach line test facilities" - followed by a list of options. Can you re-dial and check it again?

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Tue, 26 May 2020 11:20:59 GMT

That number worked - a little bit noisy which is part of previous complaint to BT - gets resolved temporrily and then worsens.

logs for 2 separate dropouts.

11:13:01, 25 May.
wl1:A WiFi device <0C:47:C9:53:13:07> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
11:13:00, 25 May.
wl1:Device <0C:47:C9:53:13:07> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
11:12:58, 25 May.
wl1:(1/6) Channel Hopping initiated/Manually initiated
11:12:55, 25 May.
:VLAN VLAN_DATA disconnected
11:12:55, 25 May.
:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
11:12:54, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
11:12:53, 25 May.
ppp1:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
11:12:53, 25 May.
ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.14.188] is deleted
11:12:53, 25 May.
ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.14.188] is deleted
11:12:53, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
11:12:52, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
11:12:52, 25 May.
BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
11:12:52, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
11:12:52, 25 May.
ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36
11:12:52, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
11:12:52, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
11:12:51, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
11:12:51, 25 May.
BR_LAN: Revoked prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
11:12:51, 25 May.
ppp1: Revoked prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
11:12:51, 25 May.
ppp1: Revoked prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
11:12:51, 25 May.
dsl:VDSL Link Down: duration was 1007 seconds

10:56:51, 25 May.
wl1:A WiFi device <A8:DB:03:B1:30:26> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
10:56:50, 25 May.
wl0:Device <A8:DB:03:B1:30:26> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])
10:56:49, 25 May.
wl1:Device <A8:DB:03:B1:30:26> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])
10:56:49, 25 May.
wl1:IGMP group 224.0.1.187 on interface wl1 ended by 192.168.1.206
10:56:48, 25 May.
:WAN DHCPv6 Client Prefix : 2a00:23c6:7487:fb00::/56 (valid time = 315360000 / preferred time = 315360000)
10:56:46, 25 May.
BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
10:56:46, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:56:46, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:46, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
BR_LAN: Allocated address = 2a00:23c6:7487:fb00:2620:c7ff:fe66:7c89 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
ppp1: Allocated address = 2a00:23c6:7487:fb01:2620:c7ff:fe66:7c87 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:46, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:56:46, 25 May.
ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36
10:56:45, 25 May.
BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
10:56:45, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:56:45, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
ppp1: Allocated address = 2a00:23c6:7487:fb01:2620:c7ff:fe66:7c87 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:45, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated address = 2a00:23c6:7487:fb00:2620:c7ff:fe66:7c89 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:45, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated address = 2a00:23c6:7487:fb00:2620:c7ff:fe66:7c89 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:45, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated address = 2a00:23c6:7487:fb00:2620:c7ff:fe66:7c89 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:45, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:56:45, 25 May.
ppp1:WAN DHCPv6 Mode : Statefull
10:56:44, 25 May.
BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
10:56:44, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:56:44, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:56:44, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:44, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 240000000 / preferred time = 0)
10:56:43, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 240000000 / preferred time = 0)
10:56:43, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
10:56:43, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
10:56:43, 25 May.
:WAN DHCPv6 Client Prefix : 2a00:23c6:7487:fb00::/56 (valid time = 315360000 / preferred time = 315360000)
10:56:43, 25 May.
ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36
10:56:43, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:56:43, 25 May.
wl0:A WiFi device <A8:DB:03:B1:30:26> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])
10:56:42, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:42, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 240000000 / preferred time = 0)
10:56:42, 25 May.
BR_LAN: Allocated address = 2a00:23c6:7487:fb00:2620:c7ff:fe66:7c89 (valid time = 2026291200 / preferred time = 2026291200)
10:56:42, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:41, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:56:41, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:41, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 240000000 / preferred time = 0)
10:56:41, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 240000000 / preferred time = 0)
10:56:41, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 240000000 / preferred time = 0)
10:56:41, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 240000000 / preferred time = 0)
10:56:41, 25 May.
ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0
10:56:41, 25 May.
BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
10:56:41, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:56:40, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:56:39, 25 May.
:WAN: SENSING AUTO VDSL
10:56:39, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:56:39, 25 May.
ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36
10:56:39, 25 May.
ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.14.188]
10:56:39, 25 May.
ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.14.188]
10:56:39, 25 May.
wl1:IGMP join received for group 224.0.1.187 on interface wl1
10:56:39, 25 May.
ppp1:PPP: PPP INFO 81.139.57.100,81.139.56.100
10:56:39, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:56:39, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:56:39, 25 May.
BR_LAN: Allocated prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:38, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:56:38, 25 May.
ppp1: Allocated prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
10:56:38, 25 May.
ppp1:PPP: PPP INFO
10:56:38, 25 May.
ppp:PPP: IPCP_NAK
10:56:38, 25 May.
ppp:PPP: CHAP_SUCCESS
10:56:38, 25 May.
ppp:PPP: CHAP_RESPONSE
10:56:38, 25 May.
ppp:PPP: LCP_GOOD_ACK
10:56:38, 25 May.
ppp:PPP: LCP_REQUEST
10:56:38, 25 May.
:PPPoE error: timeout
10:56:22, 25 May.
:PPPoE error: timeout
10:56:14, 25 May.
:PPPoE error: timeout
10:56:10, 25 May.
:PPPoE error: timeout
10:56:09, 25 May.
wl1:IGMP join received for group 224.0.1.187 on interface wl1
10:56:09, 25 May.
wl1:IGMP group 224.0.1.187 on interface wl1 started by 192.168.1.206
10:56:09, 25 May.
wl1:IGMP group 224.0.1.187 on interface wl1 by 192.168.1.206 requested
10:56:05, 25 May.
ptm0.101:VLAN VLAN_DATA connected
10:56:05, 25 May.
:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]
10:56:05, 25 May.
:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]
10:56:05, 25 May.
dsl:VDSL link Up: Down Rate=74239Kbps, Up Rate=17000Kbps, SNR Margin Down=0.00dB, SNR Margin Up=6.00dB
10:55:43, 25 May.
wl0:IGMP group 224.0.1.187 on interface wl0 ended by 192.168.1.240
10:55:43, 25 May.
:VLAN VLAN_DATA disconnected
10:55:43, 25 May.
:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
10:55:42, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:55:42, 25 May.
:Connection to the Internet has been terminated.(Reboot,Reconfiguration,forced termination)
10:55:41, 25 May.
ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.14.188] is deleted
10:55:41, 25 May.
ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.14.188] is deleted
10:55:41, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:55:40, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:55:40, 25 May.
BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1
10:55:40, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:55:40, 25 May.
ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36
10:55:40, 25 May.
BR_LAN:The LAN DHCPv6 Server is active
10:55:40, 25 May.
BR_LAN:The LAN DHCPv6 Server is inactive
10:55:40, 25 May.
BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)
10:55:40, 25 May.
BR_LAN: Revoked prefix = 2a00:23c6:7487:fb00::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:55:39, 25 May.
ppp1: Revoked prefix = 2a00:23c6:7487:fb01::/64 (valid time = 2026291200 / preferred time = 2026291200)
10:55:39, 25 May.
ppp1: Revoked prefix = 2a00:23c6:7487:fb00::/56 (valid time = 2026291200 / preferred time = 2026291200)
10:55:39, 25 May.
dsl:VDSL Link Down: duration was 482 seconds
10:55:33, 25 May.
wl0:Device <D0:C5:F3:0C:5A:32> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])
10:54:34, 25 May.
wl1:IGMP join received for group 224.0.1.187 on interface wl1
10:54:34, 25 May.
wl1:IGMP group 224.0.1.187 on interface wl1 started by 192.168.1.206
10:54:34, 25 May.
wl1:IGMP group 224.0.1.187 on interface wl1 by 192.168.1.206 requested
10:53:37, 25 May.
wl0:Device <38:53:9C:90:B2:C8> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])
10:53:34, 25 May.
wl0:Device <A8:DB:03:B1:30:26> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

Re: Frequent BT Fibre disconnects that OpenReach can never trace.

Hangerhead — Tue, 26 May 2020 11:44:25 GMT

Router Stats:

(NOISE Margin looks high?)

Product name:

BT Hub 6A

Serial number:

+084316+xxxxx

Firmware version:

SG4B1000E020

Firmware updated:

27-Mar-2020

Board version:

1.0

Gui version:

1.115.0

DSL uptime:

1 Days, 0 Hours 57 Minutes 33 Seconds

Data rate:

17.00 Mbps / 49.00 Mbps

Maximum data rate:

29464 / 78027

Noise margin:

14.1 dB / 13.8 dB

Line attenuation:

21 dB

Signal attenuation:

13.4 dB / 21 dB

VPI / VCI:

0/38

Modulation:

G_993_2_ANNEX_B

Latency type:

Fast Path

Data sent / received:

9 GB Uploaded / 24 GB Downloaded

Broadband username:

bthomehub@btbroadband.com

BT Wi-fi:

Active

2.4 GHz wireless network name:

xxxxx

2.4 GHz wireless channel:

Smart (Channel 1)

5 GHz wireless network name:

xxxx

5 GHz wireless channel:

Smart (Channel 36)

Wireless security:

WPA2 (Recommended)

Wireless mode:

Mode 1

Firewall:

MAC address:

xxxx

Software variant:

Boot loader:

7.33.1