15-02-2026 10:44 AM - edited 15-02-2026 10:45 AM
Service been down since yesterday on the 1.6 package. There are other posts that are similar and suggest an issue.
3rd party route logs (also no service on the EE hub,logs here don't seem detailed)
2026-02-15T10:27:52Noticeppp[wan_link0] Link: reconnection attempt 27613 in 3 seconds
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: LayerStart
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: state change Stopped --> Starting
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: Down event
2026-02-15T10:27:52Noticeppp[wan_link0] Link: DOWN event
2026-02-15T10:27:52Noticeppp[wan_link0] PPPoE: connection closed
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: LayerFinish
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: state change Stopping --> Stopped
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: rec'd Terminate Ack #91 (Stopping)
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: SendTerminateAck #92
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: rec'd Terminate Request #247 (Stopping)
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: LayerDown
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: SendTerminateReq #91
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: state change Opened --> Stopping
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: parameter negotiation failed
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: authorization failed
2026-02-15T10:27:52Noticeppp[wan_link0] MESG: CHAP authentication failure
2026-02-15T10:27:52Noticeppp[wan_link0] CHAP: rec'd FAILURE #1 len: 31
2026-02-15T10:27:52Noticeppp[wan_link0] CHAP: sending RESPONSE #1 len: 46
2026-02-15T10:27:52Noticeppp[wan_link0] CHAP: Using authname "bthomehub@btbroadband.com"
2026-02-15T10:27:52Noticeppp[wan_link0] Name: "acc-aln2.ra"
2026-02-15T10:27:52Noticeppp[wan_link0] CHAP: rec'd CHALLENGE #1 len: 64
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: LayerUp
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: auth: peer wants CHAP, I want nothing
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: state change Ack-Sent --> Opened
2026-02-15T10:27:52Noticeppp[wan_link0] MAGICNUM 0x32b9ff82
2026-02-15T10:27:52Noticeppp[wan_link0] MRU 1492
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: rec'd Configure Ack #90 (Ack-Sent)
2026-02-15T10:27:52Noticeppp[wan_link0] MAGICNUM 0x32b9ff82
2026-02-15T10:27:52Noticeppp[wan_link0] MRU 1492
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: SendConfigReq #90
2026-02-15T10:27:52Noticeppp[wan_link0] PROTOCOMP
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: rec'd Configure Reject #89 (Ack-Sent)
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: state change Req-Sent --> Ack-Sent
2026-02-15T10:27:52Noticeppp[wan_link0] MAGICNUM 0x67dd4d35
2026-02-15T10:27:52Noticeppp[wan_link0] AUTHPROTO CHAP MD5
2026-02-15T10:27:52Noticeppp[wan_link0] MRU 1492
2026-02-15T10:27:52Noticeppp[wan_link0] LCP: SendConfigAck #246
2026-02-15T10:27:52Noticeppp[wan_link0] MAGICNUM 0x67dd4d35
2026-02-15T10:27:52Noticeppp[wan_link0] AUTHPROTO CHAP MD5
Gpt summary -
EE FTTP down, CHAP authentication failure on both custom router and EE Hub
Broadband dropped this yesterday and will not reconnect.
Openreach ONT lights are normal:
Power green
PON solid green
LOS off
Using both OPNsense and the official EE Smart Hub gives the same result. Smart Hub flashes orange.
PPPoE logs show:
CHAP authentication failure
LCP authorization failed
Connecting to access concentrator acc-aln2.ra
Reconnection loop
Username in use: bthomehub@btbroadband.com
So fibre link is up and PPP session reaches EE, but authentication is being rejected.
No recent internal changes to network. Line was working fine previously.
Has anyone seen this recently with EE? Looks like a RADIUS or backend provisioning issue rather than physical line fault.
17-02-2026 05:03 PM
I hadn't used an Openreach circuit for 3 years, but got tempted back with the EE 1.6 Gbps offer - i think any ISP that uses Openreach is in a bad place 😫
17-02-2026 05:07 PM
I’ve only been on EE for 6 weeks so for me to have a days outage, just doesn’t look good. I wish I had an altnet available to me, but it’s Virgin media or EE.
To be fair it’s been rock solid for the 6 weeks, so hopefully this isn’t a regular occurrence!