Fttp on fibre 36

[Vicgurt]

I've recently upgraded to fibre 36 from standard and my Internet drops on the regular and kicks everybody off the network. Part of the deal is we get FTTP, if fibre runs thru the street then to our property on the standard line instead of of a new fibre line would that cause a problem with the Internet?

Thanks in advance

[XRaySpeX]

Forget FTTP! You just can't get it there. All the rubbish that @mikeliuk posts about it & other disruptive time-wasting is not helpful to your cause.

[XRaySpeX]

Also forget the logs! All they can tell you is what you already know; namely that your connection is up & down like a yo-yo. The only events worth pinpointing are extraordinary unusual ones. The only events I usually look for in logs are PPP Authentication Success or Failure. The rest is boring overlong bumph. A bit like @mikeliuk 's posts 😉 !

[Mustrum]

@Vicgurt  the DSL checker results you showed earlier shows that FTTP is not available in your area, so forget about it for now. The EE 36 product description you also showed earlier just says the product can be delivered via FTTC or FTTP, but it depends on which which infrastructure is available to you. Given that you could get VDSL/FTTC speeds up to 80Mbps, you will not be in a priority area for FTTP for a while yet.

As for the compensation, that should be automatically applied for the time you have an open fault with EE, so do make sure you keep speaking to them, and don't close the fault until it is fixed.

I did not keep my router connected for very long using the BTConnect username, so not sure if it will work for longer periods, and perhaps you have a faulty EE Router. But the fact they are behaving differently suggests it is worth getting a new EE one. Hopefully you have got confirmation from EE one is on its way.

This community is open to everyone, customers try and help others, some have practical knowledge, some theoretical but like posting lots of words - alas it is up to you to work some of that out - but myself and @XRaySpeX  have given a few clues 😎

Good luck, and keep us posted

[XRaySpeX]

@Mustrum : When you used your BT router with the BTConnect username on EE BB did you notice anything in the logs about PPP Authentication?

[Vicgurt]

@mikeliukmy. New hub is due tomorrow so we should soon find out.

@XRaySpeX  I'm not sure but I can look back at the logs now and see. The BT router been on since 7 o'clock this evening and so far only once its dropped I think. I will post the PPP log now,, I'm not quite sure if the list of logs I gave you last night where of the EE Hub. Give me ten minutes to check 

[Mustrum]

@XRaySpeX  I used my Netgear D7000 to check earlier today, but after finding it worked OK, changed back to the old firmware - lost telnet access, so no more DSLstats which I did not want, and reverted to my EE username and password. 

That said, happy to check again tomorrow for a longer test of the BT username.

I did have a quick look for an old BT HH5, but I must have put it in a safe place! . 

[Vicgurt]

This shows all events that have taken place on your BT Smart Hub since the last time it was reset.

Category: 

Selected: PPP  

  Page 1 of 1

Time and date / Message

20:08:41, 26 Aug.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

20:08:41, 26 Aug.

ppp:PPP: IPCP_NAK

20:08:41, 26 Aug.

ppp:PPP: CHAP_SUCCESS

20:08:41, 26 Aug.

ppp:PPP: CHAP_RESPONSE

20:08:41, 26 Aug.

ppp:PPP: LCP_GOOD_ACK

20:08:41, 26 Aug.

ppp:PPP: LCP_REQUEST

20:08:41, 26 Aug.

:PPPoE error: timeout

20:08:25, 26 Aug.

:PPPoE error: timeout

20:08:17, 26 Aug.

:PPPoE error: timeout

20:08:12, 26 Aug.

:PPPoE error: timeout

20:07:39, 26 Aug.

:PPPoE error: timeout

20:07:37, 26 Aug.

:Connection has been terminated: remote station is not answering to LCP Echo requests.

20:07:33, 26 Aug.

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

00:01:42, 01 Jan.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

00:01:42, 01 Jan.

ppp:PPP: IPCP_NAK

00:01:42, 01 Jan.

ppp:PPP: CHAP_SUCCESS

00:01:42, 01 Jan.

ppp:PPP: CHAP_RESPONSE

00:01:42, 01 Jan.

ppp:PPP: LCP_GOOD_ACK

00:01:42, 01 Jan.

ppp:PPP: LCP_REQUEST

00:01:38, 01 Jan.

:PPPoE error: timeout

00:01:52, 01 Jan.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

00:01:52, 01 Jan.

ppp:PPP: IPCP_NAK

00:01:52, 01 Jan.

ppp:PPP: CHAP_SUCCESS

00:01:52, 01 Jan.

ppp:PPP: CHAP_RESPONSE

00:01:52, 01 Jan.

ppp:PPP: LCP_GOOD_ACK

00:01:52, 01 Jan.

ppp:PPP: LCP_REQUEST

00:01:52, 01 Jan.

:PPPoE error: timeout

00:01:44, 01 Jan.

:PPPoE error: timeout

00:01:40, 01 Jan.

:PPPoE error: timeout

00:01:45, 01 Jan.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

00:01:45, 01 Jan.

ppp:PPP: IPCP_NAK

00:01:45, 01 Jan.

ppp:PPP: CHAP_SUCCESS

00:01:45, 01 Jan.

ppp:PPP: CHAP_RESPONSE

00:01:45, 01 Jan.

ppp:PPP: LCP_GOOD_ACK

00:01:45, 01 Jan.

ppp:PPP: LCP_REQUEST

00:01:45, 01 Jan.

:PPPoE error: timeout

00:01:37, 01 Jan.

:PPPoE error: timeout

00:01:32, 01 Jan.

:PPPoE error: timeout

01:45:12, 24 Aug.

:PPPoE error: timeout

01:44:40, 24 Aug.

:PPPoE error: timeout

01:44:08, 24 Aug.

:PPPoE error: timeout

01:43:36, 24 Aug.

:PPPoE error: timeout

01:43:04, 24 Aug.

:PPPoE error: timeout

01:42:32, 24 Aug.

:PPPoE error: timeout

01:42:00, 24 Aug.

:PPPoE error: timeout

01:41:27, 24 Aug.

:PPPoE error: timeout

01:40:55, 24 Aug.

:PPPoE error: timeout

01:40:23, 24 Aug.

:PPPoE error: timeout

01:40:07, 24 Aug.

:PPPoE error: timeout

01:39:59, 24 Aug.

:PPPoE error: timeout

01:39:55, 24 Aug.

:PPPoE error: timeout

01:39:53, 24 Aug.

:Connection has been terminated: remote station is not answering to LCP Echo requests.

01:39:49, 24 Aug.

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

00:01:43, 01 Jan.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

00:01:43, 01 Jan.

ppp:PPP: IPCP_NAK

00:01:43, 01 Jan.

ppp:PPP: CHAP_SUCCESS

00:01:43, 01 Jan.

ppp:PPP: CHAP_RESPONSE

00:01:43, 01 Jan.

ppp:PPP: LCP_GOOD_ACK

00:01:43, 01 Jan.

ppp:PPP: LCP_REQUEST

00:01:43, 01 Jan.

:PPPoE error: timeout

00:01:34, 01 Jan.

:PPPoE error: timeout

00:01:30, 01 Jan.

:PPPoE error: timeout

00:46:37, 24 Aug.

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

00:46:37, 24 Aug.

ppp1:Timeout during PPP initialization LCP/IPCP

00:40:27, 24 Aug.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

00:40:27, 24 Aug.

ppp:PPP: IPCP_NAK

00:40:27, 24 Aug.

ppp:PPP: CHAP_SUCCESS

00:40:27, 24 Aug.

ppp:PPP: CHAP_RESPONSE

00:40:27, 24 Aug.

ppp:PPP: LCP_GOOD_ACK

00:40:27, 24 Aug.

ppp:PPP: LCP_REQUEST

00:40:27, 24 Aug.

:PPPoE error: timeout

00:40:10, 24 Aug.

:PPPoE error: timeout

00:40:02, 24 Aug.

:PPPoE error: timeout

00:39:58, 24 Aug.

:PPPoE error: timeout

00:39:31, 24 Aug.

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

00:01:41, 01 Jan.

ppp1:PPP: PPP INFO 87.237.17.168,87.237.17.200

00:01:41, 01 Jan.

ppp:PPP: IPCP_NAK

00:01:41, 01 Jan.

ppp:PPP: CHAP_SUCCESS

00:01:41, 01 Jan.

ppp:PPP: CHAP_RESPONSE

00:01:41, 01 Jan.

ppp:PPP: LCP_GOOD_ACK

00:01:41, 01 Jan.

ppp:PPP: LCP_REQUEST

00:01:41, 01 Jan.

:PPPoE error: timeout

00:01:37, 01 Jan.

:PPPoE error: timeout

[XRaySpeX]

Thanks. The only event of interest to me is "ppp:PPP: CHAP_SUCCESS", meaning EE BB was happy with the BTConnect username,

[mikeliuk]

Hi @Vicgurt ,

I suspect in principle you should not see that flood of PPPoE timeout errors given that your property is within sight of the cabinet and you measure a ping of 12 ms once a connection is up.

The PPP authentication behaviour of the EE Smart Hub would be more authoritative but it's possible these may not be available.

It's likely you might need another engineer to visit and you can discuss with them that the BT Smart Hub/BT Hub 6 appears to work on EE's network and show that flood of timeouts.

You also see indications the connection is being deliberately terminated and it may just be referring to the authentication process or the entire connection with EE's infrastructure as if automatic restarts are being tried to clear an issue.

I would love to conclude that the BT Smart Hub with its default credentials can work on EE's network but I think the flood of authentication timeouts means it's too early to conclude this. It's like finding one intact car in a huge motorway pileup and concluding things are fine.

My feeling is that during the course of the upgrade, the service provider has introduced a fault somewhere in your service and now you are taking time out of your day and evening to debug an issue caused by the service provider.

The community may enjoy the ins and outs of network debugging but I feel you should be supplied with a 4GEE mobile service if the replacement router does not fix your issue as it seems that the service/upgrade you have paid for is not the one you are receiving (unless you are easy going and don't mind the frequent drops).

Here's one example where the frequent disconnects were fixed with a recabling at the cabinet: https://community.bt.com/t5/BT-Fibre-broadband/Connection-to-the-Internet-has-been-terminated-Reboot...

There's no consistent pattern or root cause for the symptoms described in this thread when looking for similar reported cases such that I think it really needs to be handed over to EE or OpenReach's engineers to debug as a commercial service issue instead of being investigated by the community.

[Vicgurt]

Yes finally getting there, @mikeliuk your the man 😎. Thank you so much for Can I present this to EE to help my cause. Please? I'll re sraftot into my own version.

So you seem to think EE are deliberately doing this to my account then? Why would they place a fault on my line delibruty