cancel
Showing results for 
Search instead for 
Did you mean: 
jonodavies69
Beginner
288 Views
Message 11 of 35

Re: FTTP router keeps on dropping out

We've had the ONT changed and tried various Cables from that to the router too. And tried 2 smart hubs and 2 different TP-link( 3rd party) routers to no avail.

The engineer then suggested it could be service provider related.
0 Ratings
Reply
Distinguished Sage
Distinguished Sage
286 Views
Message 12 of 35

Re: FTTP router keeps on dropping out

There could be an issue further up the network, which is causing the loss of connectivity, which I assume is what you are getting?

What are the symptoms, is it just a loss of DNS resolution, and how quickly does it recover?

0 Ratings
Reply
jonodavies69
Beginner
272 Views
Message 13 of 35

Re: FTTP router keeps on dropping out

The symptoms are :

devices dissconnect, router turns green then orange then comes back to blue.

It takes a good few minutes to come back with the smart hub, on the tp link routers it was faster coming back but i put that down to the router being a different model.
0 Ratings
Reply
Distinguished Sage
Distinguished Sage
270 Views
Message 14 of 35

Re: FTTP router keeps on dropping out

What does the event log show on the home hub, is it loss of PPPoE connection?

0 Ratings
Reply
jonodavies69
Beginner
257 Views
Message 15 of 35

Re: FTTP router keeps on dropping out

 

21:28:41, 07 Mar.

ppp0:TR69 ConnectionRequest Failed

21:28:41, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): Connection: Close

21:28:41, 07 Mar.

ppp0:TR69 ConnectionRequest: processing request from ACS

::, undefined.

7.1.2; AFTN Build/NS6260)

21:28:41, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:3, [unsupported User-Agent]): Accept-Encoding: gzip

::, undefined.

7.1.2; AFTN Build/NS6260)

21:28:38, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:3, [unsupported User-Agent]): Connection: Keep-Alive

21:28:36, 07 Mar.

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

21:28:36, 07 Mar.

��<¶:TR69 sending GetParameterValuesResponse message

21:28:36, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:36, 07 Mar.

:TR69 sending SetParameterValuesResponse message

21:28:36, 07 Mar.

ppp0:TR69 receiving SetParameterValues message

21:28:35, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:28:35, 07 Mar.

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

21:28:35, 07 Mar.

ppp0:TR69 receiving InformResponse message

21:28:34, 07 Mar.

ppp0:TR69 event found : 0 BOOTSTRAP

21:28:33, 07 Mar.

ppp0:TR69 sending Inform message

21:28:32, 07 Mar.

ppp0:TR69 event found : 0 BOOTSTRAP

21:28:31, 07 Mar.

ppp0:TR69 sending Inform message

21:28:30, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:28:29, 07 Mar.

ppp0:TR69 creating new session with ACS

21:28:25, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:28:23, 07 Mar.

ppp0:TR69 connectivity to (pbthdmw.bt.m) has been closed

21:28:22, 07 Mar.

:TR69 sending SetParameterValuesResponse message

21:28:22, 07 Mar.

ppp0:TR69 receiving SetParameterValues message

21:28:22, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:28:21, 07 Mar.

ppp0:TR69 connectivity to (pbthdmw.bt.m) has been initiated

21:28:21, 07 Mar.

ppp0:TR69 receiving InformResponse message

21:28:20, 07 Mar.

ppp0:TR69 event found : 6 CONNECTION REQUEST

21:28:20, 07 Mar.

ppp0:TR69 event found : 4 VALUE CHANGE

21:28:19, 07 Mar.

ppp0:TR69 sending Inform message

21:28:19, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): Accept: */*

21:28:18, 07 Mar.

ppp0:TR69 event found : 6 CONNECTION REQUEST

21:28:18, 07 Mar.

ppp0:TR69 event found : 4 VALUE CHANGE

21:28:17, 07 Mar.

ppp0:TR69 sending Inform message

21:28:15, 07 Mar.

ppp0:TR69 creating new session with ACS

21:28:14, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): Connection: Close

21:28:13, 07 Mar.

ppp0:TR69 ConnectionRequest: processing request from ACS

21:28:13, 07 Mar.

ppp0:TR69 ConnectionRequest Failed

21:28:13, 07 Mar.

ppp0:TR69 ConnectionRequest: processing request from ACS

21:28:09, 07 Mar.

ppp0:TR69 connectivity to (pbthdmw.bt.m) has been closed

21:28:08, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:28:08, 07 Mar.

��:TR69 sending SetParameterAttributesResponse message

21:28:08, 07 Mar.

ppp0:TR69 receiving SetParameterAttributes message

21:28:08, 07 Mar.

:TR69 sending GetParameterValuesResponse message

21:28:08, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:08, 07 Mar.

:TR69 sending GetParameterValuesResponse message

21:28:08, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:08, 07 Mar.

���jF:TR69 sending GetParameterValuesResponse message

21:28:08, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:08, 07 Mar.

:TR69 sending GetParameterValuesResponse message

21:28:08, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:07, 07 Mar.

:TR69 sending GetParameterValuesResponse message

21:28:07, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:07, 07 Mar.

��:TR69 sending SetParameterAttributesResponse message

21:28:07, 07 Mar.

ppp0:TR69 receiving SetParameterAttributes message

21:28:07, 07 Mar.

��<¶:TR69 sending GetParameterValuesResponse message

21:28:07, 07 Mar.

ppp0:TR69 receiving GetParameterValues message

21:28:06, 07 Mar.

:TR69 sending SetParameterValuesResponse message

21:28:06, 07 Mar.

ppp0:TR69 receiving SetParameterValues message

21:28:05, 07 Mar.

ppp0:TR69 connectivity to (pbthdmw.bt.m) has been initiated

21:28:05, 07 Mar.

ppp0:TR69 receiving InformResponse message

21:28:04, 07 Mar.

ppp0:TR69 event found : 0 BOOTSTRAP

21:28:04, 07 Mar.

ppp0:TR69 sending Inform message

21:28:03, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:28:02, 07 Mar.

ppp0:TR69 event found : 0 BOOTSTRAP

21:28:01, 07 Mar.

ppp0:TR69 sending Inform message

21:27:58, 07 Mar.

ppp0:TR69 creating new session with ACS

21:27:58, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:27:56, 07 Mar.

:HTTP UserBasic login from 192.168.1.65 successfully

21:27:56, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): Host: ncc.avast.com

21:27:56, 07 Mar.

wl0:IGMP group 224.0.1.187 on interface wl0 started by 192.168.1.65

21:27:56, 07 Mar.

wl0:IGMP group 224.0.1.187 on interface wl0 by 192.168.1.65 requested

21:27:56, 07 Mar.

wl0:IGMP join received for group 224.0.1.187 on interface wl0

21:27:39, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Microsoft NCSI

21:27:39, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): User-Agent: Avast NCC

21:27:39, 07 Mar.

BR_LAN:The HTTP headers offered by the device (id:2, [unknown User-Agent]): Host: ip-info.ff.avast.com

21:27:39, 07 Mar.

BR_LAN:The DHCP options that are offered by the device (id:2): DiscoverOptions: | DiscoverOption55: | RequestOptions: 53,61,50,12,81,60,55 | RequestOption55: 1,3,6,15,31,33,43,44,46,47,119,121,249,252 | HostName: BEAST-2 | VendorId: MSFT 5.0

21:27:39, 07 Mar.

:DHCP Confirmation of Request

21:27:37, 07 Mar.

wl0:A WiFi device <0C:8B:FD:74:74:FD> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

21:27:21, 07 Mar.

BR_LAN:A redirect rule is added for the device (id:5)

21:27:21, 07 Mar.

BR_LAN:The OIE is supported for the device (id:5)

21:27:21, 07 Mar.

BR_LAN:The DHCP options that are offered by the device (id:5): DiscoverOptions: | DiscoverOption55: | RequestOptions: 53,61,50,12,81,60,55 | RequestOption55: 1,3,6,15,31,33,43,44,46,47,119,121,249,252 | HostName: Jacys-Laptop | VendorId: MSFT 5.0

21:27:21, 07 Mar.

BR_LAN:A redirect rule is added for the device (id:4)

21:27:21, 07 Mar.

BR_LAN:The OIE is supported for the device (id:4)

21:27:21, 07 Mar.

BR_LAN:The DHCP options that are offered by the device (id:4): DiscoverOptions: 53,61,57,60,12,55 | DiscoverOption55: 1,3,6,15,26,28,51,58,59,43 | RequestOptions: 53,61,50,54,57,60,12,55 | RequestOption55: 1,3,6,15,26,28,51,58,59,43 | HostName: Galaxy-S7-edge | VendorId: android-dhcp-8.0.0

21:27:21, 07 Mar.

:DHCP Confirmation of Request

21:27:21, 07 Mar.

:DHCP Confirmation of Request

21:27:14, 07 Mar.

BR_LAN:New device (id:5) connecting on the LAN was detected

21:27:14, 07 Mar.

wl0:Device <0C:8B:FD:74:74:FD> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

21:27:14, 07 Mar.

wl1:A WiFi device <44:1C:A8:7D:C1:2B> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

21:27:07, 07 Mar.

BR_LAN:New device (id:4) connecting on the LAN was detected

21:27:07, 07 Mar.

wl0:A WiFi device <8C:45:00:AD:09:3A> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

21:26:43, 07 Mar.

BR_LAN:A redirect rule is added for the device (id:3)

21:26:43, 07 Mar.

BR_LAN:The OIE is supported for the device (id:3)

21:26:43, 07 Mar.

BR_LAN:The DHCP options that are offered by the device (id:3): DiscoverOptions: 53,61,57,60,12,55 | DiscoverOption55: 1,3,6,15,26,28,51,58,59,43 | RequestOptions: 53,61,50,54,57,60,12,55 | RequestOption55: 1,3,6,15,26,28,51,58,59,43 | HostName: amazon-f5fbe64b9 | VendorId: android-dhcp-7.1.2

21:26:43, 07 Mar.

:DHCP Confirmation of Request
Hi im not up to speed with this side of things to be honest. does this make more sense to you ? This is from last night
21:26:41, 07 Mar.

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

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
253 Views
Message 16 of 35

Re: FTTP router keeps on dropping out

Mostly :TR69 events which are initiated from the BT management end, but there do seem a lot of them.

The question is, what shows on the event log,  just prior to the router disconnect, and why is it only specific devices (Apple) that is causing the issue?

I guess that none of your own devices are Apple?

I do suspect an issue back towards the BT network, but I can see its going to be difficult to diagnose without higher level support from the FTTP team.

 

0 Ratings
Reply
jonodavies69
Beginner
245 Views
Message 17 of 35

Re: FTTP router keeps on dropping out

there's 3 apple devices here ,...an older ( 2012 model approx ) ipad that works fine, my daughters iphone 6 plus that's totally unusable and her ipad pro seems to be hit and miss. Just having the iphone turned on in our premises causes issues, even with the wifi on the iphone turned off completely.

awaiting the fttp call this morning so will keep you posted either way 🙂



0 Ratings
Reply
Distinguished Sage
Distinguished Sage
229 Views
Message 18 of 35

Re: FTTP router keeps on dropping out

Without some form of network diagnostics tools, I cannot see how this can be easily resolved.

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
220 Views
Message 19 of 35

Re: FTTP router keeps on dropping out

How close to the FTTP modem,home hub and Ethernet cabling, is the iPhone that causes the problem, could it be the actual mobile transmissions that are getting into the ONT, and causing it to lose connection?

Do you have any other mobile devices which are used in proximity to the ONT?

0 Ratings
Reply
Maryemm
Aspiring Contributor
208 Views
Message 20 of 35

Re: FTTP router keeps on dropping out

I find this problem interesting as I have a similar problem. 

We have FTTP and when it was first set up I was able to watch a whole film on TV without any trouble. Now my connection constantly drops while we are on line. On my Kindle and iPad there are hiccups which are soon over. On my desktops there is a slight pause and then the action continues. The blue light on my router never falters!!

My set-up is upstairs : our main TV downstairs. Recently we can't watch a 30 minute TV programme on the internet without that awful spinning "wheel" which soon gets unbearable. 

I have posted regarding the latter problem elsewhere as I hope using an extender will solve the problem.

However it is "interesting" that someone else has this loss of connection problem. BT have tested my connection and report it as "stable". Before FTTP was installed I had our house telephone set- up checked privately. and all was /is well. 

Before the connection drop, next door was "empty," being renovated. Now neighbours are back. Could changing the wireless frequency (is that the word?) on the router help?  

0 Ratings
Reply