My router has broken

[#1]

@JulieD42 

To see if the messages have changed can you post the current PPP event log please

[#2]

[#3]

Thanks

The clocks moved on 2 hours, still the same error message.

Your hub keeps sending PADI because it is not receiving a PADO (PPPoE Active Discovery Offer) from the PPPoE server.

The order of expected messages

1. PADI (PPPoE Active Discovery Initiation): The client sends a PADI packet to the broadcast address, looking for PPPoE servers.
2. PADO (PPPoE Active Discovery Offer): Upon receiving a PADI packet, the server sends back a PADO packet, indicating the server is available.
3. PADR (PPPoE Active Discovery Request): The client selects a server and sends a PADR packet to request the establishment of a session.
4. PADS (PPPoE Active Discovery Session-confirmation): The server responds to the PADR packet with a PADS packet to confirm the session, at which point a session ID is created.
5. Data Transmission: After the session is established, the client and server can exchange data via the PPP protocol.

So as already stated the Hub is not receiving a PADO. As to why, there are a few scenarios but I would suggest Openreach need investigate this more, I would hope they can view individual connection ports at the head end equipment

[#4]

Just to point out - those log entries are dated 1 October. Today is 8 December.

[#5]

That's because the router hasn't been able to contact a time server and so it's time/date is still at the default

[#6]

Probably because the clock has not been able to establish a connection to update, so has defaulted to the installation date - at least one of the screenshots shows the correct date at the top, as it has been pulled from an iPhone.

[#7]

OK. I did wonder...

[#8]

Thank you, so does this mean I need an outreach engineer and not the Qube engineer they’re sending on Thursday?

[#9]

Yes, I screenshot these today. I did wonder why the dates are October. 

[#10]

An OpenReach engineer, yes - unless OR can fix it remotely.

[#11]

So am I beat calling pn back tomorrow? They’ve a Qube engineer coming Thursday.

[#12]

I would do that, @JulieD42 - if he/she comes, it will be a waste of time.

I'll tag @MatthewWheeler in case he is around and see if he can help.

[#13]

Exactly. Then I’d have to wait even longer for an engineer to come out. Are the Qube engineers Plusnet? They just come in to try and basically do the internal checks I’ve already done?

[#14]

So is this why it’s suddenly broken? If was fine until Saturday lafgernoin, never any issue. When I call should I tell them this is the issue?

[#15]

No - Qube are sub-contracted by OpenReach to assist end-users where OpenReach consider that a reported fault is due to customers own equipment/internal set-up - they are 'cheaper' than sending out an OR engineer.

And yes, they are only really as technically competent as you appear to be, and cannot even touch any OR infrastructure beyond that that you can -i.e. as far back as the test socket.