cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Aspiring Contributor
1,026 Views
Message 1 of 13

Multiple, brief disconnections every day

Hi there,

About six weeks ago, I started getting brief disconnections on my line each day. My Internet would go down for maybe 1 or 2 minutes each time, before reconnecting. This happened at random times, and with varying frequency, but was typically about two or three times each day – with occasional days when I didn't have any disconnects.

Prior to this, I never had any problems on my line at this address.

I phoned BT who did line tests, but nothing was found. I had engineers round here on three occasions, who checked both indoors and the cabinet on the street outside, but didn't find any problems. I was sent a new hub (same model as before, BT Smart Hub – Type A) , and I even bought a new computer, but still the problems have continued exactly as before. I'm using a "Master Socket Type 5C – Open Reach MK4", a wired connection to my desktop PC.

More recently, the frequency of disconnects has begun to increase. Yesterday I had 10 disconnects, and already today by mid-afternoon I've had seven. This has become an extremely annoying problem now, and I would really appreciate some help in resolving the matter.

The only slight clue, is that these disconnections happen more often when I start watching a YouTube video, especially one that's in 1080p HD. Not always, but for a significant number of the disconnects.

Below is an example of an error log from today.

---

12:24:50, 03 Nov.

wl0.2:WiFi security settings have been successfully saved

12:24:50, 03 Nov.

wl0.1:WiFi security settings have been successfully saved

12:24:50, 03 Nov.

wl1.1:WiFi security settings have been successfully saved

12:24:48, 03 Nov.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f07:c400::/56 (valid time = 315360000 / preferred time = 315360000)

12:24:47, 03 Nov.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

12:24:47, 03 Nov.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

12:24:43, 03 Nov.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

12:24:42, 03 Nov.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated

12:24:42, 03 Nov.

ppp1:TR69 receiving InformResponse message

12:24:42, 03 Nov.

ppp1:TR69 event found : 4 VALUE CHANGE

12:24:41, 03 Nov.

ppp1:TR69 sending Inform message

12:24:40, 03 Nov.

ppp1:TR69 event found : 4 VALUE CHANGE

12:24:39, 03 Nov.

ppp1:TR69 sending Inform message

12:24:39, 03 Nov.

ppp1:TR69 creating new session with ACS

12:24:38, 03 Nov.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f07:c400::/56 (valid time = 315360000 / preferred time = 315360000)

12:24:36, 03 Nov.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

12:24:36, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:36, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:36, 03 Nov.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

12:24:36, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

BR_LAN: Allocated address = 2a00:23c5:3f07:c400:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated address = 2a00:23c5:3f07:c401:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:36, 03 Nov.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

12:24:36, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:36, 03 Nov.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

12:24:36, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

BR_LAN: Allocated address = 2a00:23c5:3f07:c400:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated address = 2a00:23c5:3f07:c401:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:36, 03 Nov.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

12:24:35, 03 Nov.

ppp1:WAN DHCPv6 Mode : Statefull

12:24:35, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:35, 03 Nov.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

12:24:35, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:35, 03 Nov.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

12:24:35, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:34, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:34, 03 Nov.

ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0

12:24:34, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:34, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:34, 03 Nov.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

12:24:34, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 240000000 / preferred time = 0)

12:24:33, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 240000000 / preferred time = 0)

12:24:33, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 2026291200 / preferred time = 2026291200)

12:24:33, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 2026291200 / preferred time = 2026291200)

12:24:33, 03 Nov.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f07:c400::/56 (valid time = 315360000 / preferred time = 315360000)

12:24:32, 03 Nov.

:WAN: SENSING AUTO VDSL

12:24:32, 03 Nov.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.11.165]

12:24:32, 03 Nov.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.11.165]

12:24:32, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:32, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:31, 03 Nov.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

12:24:31, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 240000000 / preferred time = 0)

12:24:31, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 240000000 / preferred time = 0)

12:24:31, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 240000000 / preferred time = 0)

12:24:31, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 240000000 / preferred time = 0)

12:24:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:24:31, 03 Nov.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

12:24:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:24:31, 03 Nov.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

12:24:30, 03 Nov.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

12:24:30, 03 Nov.

BR_LAN: Allocated prefix = 2a00:23c5:3f07:c400::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:30, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c401::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:24:30, 03 Nov.

ppp1: Allocated prefix = 2a00:23c5:3f07:c400::/56 (valid time = 2026291200 / preferred time = 2026291200)

12:24:30, 03 Nov.

ppp1:PPP: PPP INFO

12:24:29, 03 Nov.

ppp:PPP: IPCP_NAK

12:24:29, 03 Nov.

ppp:PPP: CHAP_SUCCESS

12:24:29, 03 Nov.

ppp:PPP: CHAP_RESPONSE

12:24:29, 03 Nov.

ppp:PPP: LCP_GOOD_ACK

12:24:29, 03 Nov.

ppp:PPP: LCP_REQUEST

12:24:29, 03 Nov.

:PPPoE error: timeout

12:24:13, 03 Nov.

:HTTP UserAdmin login from 192.168.1.68 successfully

12:24:13, 03 Nov.

:PPPoE error: timeout

12:24:05, 03 Nov.

:PPPoE error: timeout

12:24:01, 03 Nov.

:PPPoE error: timeout

12:23:56, 03 Nov.

ptm0.101:VLAN VLAN_DATA connected

12:23:56, 03 Nov.

:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]

12:23:56, 03 Nov.

:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]

12:23:56, 03 Nov.

dsl:VDSL link Up: Down Rate=51145Kbps, Up Rate=14998Kbps, SNR Margin Down=0.00dB, SNR Margin Up=6.00dB

12:23:52, 03 Nov.

:HTTP UserBasic login from 192.168.1.68 successfully

12:23:34, 03 Nov.

:VLAN VLAN_DATA disconnected

12:23:33, 03 Nov.

ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.11.165] is deleted

12:23:33, 03 Nov.

ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.11.165] is deleted

12:23:33, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:23:33, 03 Nov.

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

12:23:32, 03 Nov.

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

12:23:32, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:23:31, 03 Nov.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

12:23:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:23:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:23:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is active

12:23:31, 03 Nov.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

12:23:31, 03 Nov.

BR_LAN:The LAN DHCPv6 Server is inactive

12:23:31, 03 Nov.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

12:23:31, 03 Nov.

BR_LAN: Revoked prefix = 2a00:23c5:3f07:c400::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:23:31, 03 Nov.

ppp1: Revoked prefix = 2a00:23c5:3f07:c401::/64 (valid time = 2026291200 / preferred time = 2026291200)

12:23:31, 03 Nov.

ppp1: Revoked prefix = 2a00:23c5:3f07:c400::/56 (valid time = 2026291200 / preferred time = 2026291200)

12:23:30, 03 Nov.

dsl:VDSL Link Down: duration was 1400 seconds

12:11:53, 03 Nov.

: HTTP UserAdmin timeout from 192.168.1.68

12:01:06, 03 Nov.

wl0.2:WiFi security settings have been successfully saved

 

0 Ratings
Reply
12 REPLIES 12
Highlighted
Distinguished Sage
Distinguished Sage
1,001 Views
Message 2 of 13

Re: Multiple, brief disconnections every day

@wjfox2019 

You are seeing losses of the DSL connection.

Is there any noise on your phone calls? Dial 17070 and select option 2, there should be no noise between the announcements.

0 Ratings
Reply
Highlighted
Aspiring Contributor
976 Views
Message 3 of 13

Re: Multiple, brief disconnections every day

I performed a quiet line test.

The line had a very faint crackling. On a scale of 1 to 10, maybe only a 2.

I then switched off the hub, and turned it on again, while repeating the test. The hub light began to flash red, as it normally does before turning blue. During this time, I heard a very slight increase in the crackling – maybe a 3 out of 10.

Overall though it was pretty faint. Not sure what you can deduce from that.

Could these disconnections perhaps be electrical-related? My landlord recently had an electrician in the neighbouring property which is connected to mine.

0 Ratings
Reply
Highlighted
Distinguished Sage
Distinguished Sage
958 Views
Message 4 of 13

Re: Multiple, brief disconnections every day

You line should be silent and any noise is a problem for your broadband. Have you tried using the test socket with a filter to eliminate any internal wiring causing the interference. If noise persists then report phone fault to 151



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.
0 Ratings
Reply
Highlighted
Distinguished Sage
Distinguished Sage
945 Views
Message 5 of 13

Re: Multiple, brief disconnections every day

The crackling you can hear, is only being generated because of a line fault, or something wrong with your internal wiring. You should not be able to hear anything.

 

0 Ratings
Reply
Highlighted
Aspiring Contributor
624 Views
Message 6 of 13

Re: Multiple, brief disconnections every day

An update on this. I'm still having problems.

In December, a second problem occurred, as my connection speed slowed greatly. I called an engineer (for the 4th time since September) and he identified a fault on part of the line between my flat and a neighbour's wall. He drilled through my wall and physically installed a new wire, bypassing the older one. His tests on the line, including a quiet line test, showed it was now working fine. My connection speed was restored, and for two weeks I had super-fast Internet with zero disconnections.

Fast forward to today. My connection speed is fine. However, the random disconnects have started again. I've been keeping a diary of the times and durations – and I've had 10 today, each lasting just a couple of minutes before my hub restarts itself.

What on earth is causing this?

I thought it might be a Wi-Fi issue caused by my neighbour(s), and the admin log included "Wi-Fi security settings" so I turned Wi-Fi off, but it still happens even with just a wired connection to my desktop.

Could it be a firmware issue, or something else related to my hub? Could it be a power issue? (I've had some recent electrical problems in my flat – these haven't actually switched the hub off, though). Am I being hacked?

On a personal note, this is now having a significant impact on my mental health – and is harming my ability to work at home and earn a living. I'd be very grateful if anyone could shed some light on this. I'm on the verge of leaving BT and trying another provider. Below are 2 examples of logs, both from today.

----------

9:00am on Saturday 11th January 2020

(first disconnect since engineer visit)

 

09:04:28, 11 Jan.

:HTTP UserAdmin login from 192.168.1.68 successfully

09:04:23, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:22, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:21, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:20, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:19, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:18, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:17, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:04:16, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

09:02:09, 11 Jan.

:HTTP UserBasic login from 192.168.1.68 successfully

08:55:14, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:13, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:12, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:10, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:09, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:08, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:07, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:55:06, 11 Jan.

wl1:A device <D0:04:01:9F:DB:46> failed to connect to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G]) because it provided incorrect login information.

08:52:46, 11 Jan.

wl1:(11/1) Channel Hopping initiated/Manually initiated

08:52:44, 11 Jan.

wl0.2:WiFi security settings have been successfully saved

 

 

----------


Again on 11th January 2020, this time at 16:29

 

16:29:53, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:53, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:53, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

16:29:53, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:52, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:52, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:52, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

16:29:52, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

16:29:52, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:52, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:52, 11 Jan.

ppp1:WAN DHCPv6 Mode : Statefull

16:29:52, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

16:29:51, 11 Jan.

ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0

16:29:51, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:51, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:51, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:51, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

16:29:51, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:51, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

16:29:51, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:51, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:50, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

16:29:50, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:50, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:49, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:49, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:49, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 240000000 / preferred time = 0)

16:29:49, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 240000000 / preferred time = 0)

16:29:49, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

16:29:49, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

16:29:49, 11 Jan.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f0a:5000::/56 (valid time = 315360000 / preferred time = 315360000)

16:29:48, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:48, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:48, 11 Jan.

:WAN: SENSING AUTO VDSL

16:29:48, 11 Jan.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.11.165]

16:29:48, 11 Jan.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.11.165]

16:29:47, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:47, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:47, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:47, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 240000000 / preferred time = 0)

16:29:47, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 240000000 / preferred time = 0)

16:29:47, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 240000000 / preferred time = 0)

16:29:47, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 240000000 / preferred time = 0)

16:29:47, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:29:47, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

16:29:46, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:29:46, 11 Jan.

ppp1:PPP: PPP INFO 81.139.56.100,81.139.57.100

16:29:46, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

16:29:46, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:46, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

16:29:46, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

16:29:46, 11 Jan.

ppp1:PPP: PPP INFO

16:29:46, 11 Jan.

ppp:PPP: IPCP_NAK

16:29:45, 11 Jan.

ppp:PPP: CHAP_SUCCESS

16:29:45, 11 Jan.

ppp:PPP: CHAP_RESPONSE

16:29:45, 11 Jan.

ppp:PPP: LCP_GOOD_ACK

16:29:45, 11 Jan.

ppp:PPP: LCP_REQUEST

16:29:45, 11 Jan.

:PPPoE error: timeout

16:29:40, 11 Jan.

:HTTP UserAdmin login from 192.168.1.68 successfully

16:29:29, 11 Jan.

:PPPoE error: timeout

16:29:21, 11 Jan.

:PPPoE error: timeout

16:29:18, 11 Jan.

:HTTP UserBasic login from 192.168.1.68 successfully

16:29:17, 11 Jan.

:PPPoE error: timeout

16:29:12, 11 Jan.

ptm0.101:VLAN VLAN_DATA connected

16:29:12, 11 Jan.

:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]

16:29:12, 11 Jan.

:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]

16:29:12, 11 Jan.

dsl:VDSL link Up: Down Rate=97255Kbps, Up Rate=20000Kbps, SNR Margin Down=0.00dB, SNR Margin Up=6.00dB

16:28:50, 11 Jan.

:VLAN VLAN_DATA disconnected

16:28:50, 11 Jan.

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

16:28:49, 11 Jan.

ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.11.165] is deleted

16:28:49, 11 Jan.

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

16:28:49, 11 Jan.

ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.11.165] is deleted

16:28:49, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:28:48, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:28:48, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

16:28:48, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:28:47, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:28:47, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

16:28:47, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

16:28:47, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

16:28:47, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

0 Ratings
Reply
Highlighted
Distinguished Sage
Distinguished Sage
612 Views
Message 7 of 13

Re: Multiple, brief disconnections every day

That looks more like an issue with the home hub,

Try a factory reset of the home hub.

http://bt.custhelp.com/app/answers/detail/a_id/11386/%7E/how-do-i-reset-my-bt-hub-to-its-factory-set...

Then turn off smart setup.

http://bt.custhelp.com/app/answers/detail/a_id/44328/~/switching-smart-setup-on-and-off-on-the-bt-ho...

You also seem to have an issue with one wireless device with the wrong wireless password, that could have been a neighbour trying to connect.

Its a Motorola  wireless device which is failing with the wrong password.

Its always best to use devices which are connected by an Ethernet cable and not wireless, as wireless nearly always suffers disconnections.

 

0 Ratings
Reply
Highlighted
Aspiring Contributor
588 Views
Message 8 of 13

Re: Multiple, brief disconnections every day

Okay, I tried a factory reset at 8pm, and turned off smart setup.

It lasted 20 minutes before disconnecting again, then the hub restarted itself.

Here's the log.

----------

20:20:56, 11 Jan.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f0a:5000::/56 (valid time = 315360000 / preferred time = 315360000)

20:20:55, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

20:20:54, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

20:20:52, 11 Jan.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

20:20:51, 11 Jan.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated

20:20:51, 11 Jan.

ppp1:TR69 receiving InformResponse message

20:20:51, 11 Jan.

ppp1:TR69 event found : 4 VALUE CHANGE

20:20:50, 11 Jan.

ppp1:TR69 sending Inform message

20:20:49, 11 Jan.

ppp1:TR69 event found : 4 VALUE CHANGE

20:20:48, 11 Jan.

ppp1:TR69 sending Inform message

20:20:48, 11 Jan.

ppp1:TR69 creating new session with ACS

20:20:46, 11 Jan.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f0a:5000::/56 (valid time = 315360000 / preferred time = 315360000)

20:20:45, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

20:20:45, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:20:45, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:20:45, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:45, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:45, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:45, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

20:20:44, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

20:20:44, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

20:20:44, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:20:44, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:20:44, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:44, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:20:44, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:20:44, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:44, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

BR_LAN: Allocated address = 2a00:23c5:3f0a:5000:8220:daff:fefd:b81 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated address = 2a00:23c5:3f0a:5001:8220:daff:fefd:b7f (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:44, 11 Jan.

ppp1:WAN DHCPv6 Mode : Statefull

20:20:44, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

20:20:44, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:20:43, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:20:43, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:43, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 240000000 / preferred time = 0)

20:20:43, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 240000000 / preferred time = 0)

20:20:43, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:43, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:43, 11 Jan.

:WAN DHCPv6 Client Prefix : 2a00:23c5:3f0a:5000::/56 (valid time = 315360000 / preferred time = 315360000)

20:20:43, 11 Jan.

ppp1:WAN Router Discovery Setting Updated : M_flag = 1, O_flag = 0

20:20:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:20:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:20:42, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:42, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 240000000 / preferred time = 0)

20:20:42, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 240000000 / preferred time = 0)

20:20:42, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 240000000 / preferred time = 0)

20:20:42, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 240000000 / preferred time = 0)

20:20:41, 11 Jan.

:WAN: SENSING AUTO VDSL

20:20:41, 11 Jan.

ppp1:New DYN ROUTE is added [81.139.56.100/32 gw 172.16.11.165]

20:20:41, 11 Jan.

ppp1:New DYN ROUTE is added [81.139.57.100/32 gw 172.16.11.165]

20:20:41, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:20:41, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

20:20:41, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:20:40, 11 Jan.

ppp1:PPP: PPP INFO 81.139.57.100,81.139.56.100

20:20:40, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:20:40, 11 Jan.

BR_LAN: Allocated prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:40, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:20:40, 11 Jan.

ppp1: Allocated prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:20:40, 11 Jan.

ppp1:PPP: PPP INFO 81.139.57.100,81.139.56.100

20:20:40, 11 Jan.

ppp:PPP: IPCP_NAK

20:20:40, 11 Jan.

ppp:PPP: CHAP_SUCCESS

20:20:40, 11 Jan.

ppp:PPP: CHAP_RESPONSE

20:20:40, 11 Jan.

ppp:PPP: LCP_GOOD_ACK

20:20:40, 11 Jan.

ppp:PPP: LCP_REQUEST

20:20:40, 11 Jan.

:PPPoE error: timeout

 

20:20:24, 11 Jan.

:HTTP UserAdmin login from 192.168.1.64 successfully

20:20:23, 11 Jan.

:PPPoE error: timeout

20:20:15, 11 Jan.

:PPPoE error: timeout

20:20:12, 11 Jan.

:HTTP UserBasic login from 192.168.1.64 successfully

20:20:11, 11 Jan.

:PPPoE error: timeout

20:20:07, 11 Jan.

ptm0.101:VLAN VLAN_DATA connected

20:20:07, 11 Jan.

:connection ATM_TV disconnected.[ERROR_USER_DISCONNECT]

20:20:07, 11 Jan.

:connection ATM_DATA disconnected.[ERROR_USER_DISCONNECT]

20:20:07, 11 Jan.

dsl:VDSL link Up: Down Rate=90630Kbps, Up Rate=12340Kbps, SNR Margin Down=0.00dB, SNR Margin Up=6.00dB

20:19:45, 11 Jan.

:VLAN VLAN_DATA disconnected

20:19:43, 11 Jan.

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

20:19:43, 11 Jan.

ppp1:The DYN ROUTE [81.139.57.100/32 gw 172.16.11.165] is deleted

20:19:43, 11 Jan.

ppp1:The DYN ROUTE [81.139.56.100/32 gw 172.16.11.165] is deleted

20:19:43, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:19:43, 11 Jan.

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

20:19:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:19:42, 11 Jan.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

20:19:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:19:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:19:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is active

20:19:42, 11 Jan.

ppp1:The WAN DHCPv6 Client Process has successfully been terminated on Vlan 36

20:19:42, 11 Jan.

BR_LAN:The LAN DHCPv6 Server is inactive

20:19:41, 11 Jan.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4294967295 / preferred time = 4294967295)

20:19:41, 11 Jan.

BR_LAN: Revoked prefix = 2a00:23c5:3f0a:5000::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:19:41, 11 Jan.

ppp1: Revoked prefix = 2a00:23c5:3f0a:5001::/64 (valid time = 2026291200 / preferred time = 2026291200)

20:19:41, 11 Jan.

ppp1: Revoked prefix = 2a00:23c5:3f0a:5000::/56 (valid time = 2026291200 / preferred time = 2026291200)

20:19:41, 11 Jan.

dsl:VDSL Link Down: duration was 1236 seconds

20:10:37, 11 Jan.

: HTTP UserAdmin timeout from 192.168.1.64

20:00:32, 11 Jan.

:HTTP UserAdmin login from 192.168.1.64 successfully

20:00:29, 11 Jan.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

 

0 Ratings
Reply
Highlighted
Aspiring Contributor
526 Views
Message 9 of 13

Re: Multiple, brief disconnections every day

Another load of disconnections today. Can anyone help?

For many years, I had perfect Internet – superfast speeds, zero disconnections. Then my hub breaks down and I'm sent a new one (BT Smart Hub – Type A). And suddenly I have all these disconnections. A further replacement (another Type A) solved nothing.

Since then it's been a total nightmare.

Could this be some kind of software/hardware problem with my hub? Could I try going back to using an older one, and are they still available from BT? If so, which one is the best?

If the hub isn't the problem, then what is?

0 Ratings
Reply
Highlighted
Distinguished Sage
Distinguished Sage
520 Views
Message 10 of 13

Re: Multiple, brief disconnections every day

If you think its hub related, and nothing to do with your external line, then try a third party router instead, provided you are not on an ultrafast (G.Fast) connection.

This one from Argo works well Item 572/8882.  £32.99

Other retailers sell it as well.

If it does not cure the problem, then you can normally return it.

Its a much simpler device, with lots of extra features.