IPv6 Trial Update

[#1]

@RPMozley It was Zen.https://status.zen.co.uk/broadband/

[#2]

Around that time, I saw DNS lookup failures, but the internet was otherwise working fine.

[#3]

@MPC looks like it was like BTWholesale or Openreach maintenance work that affected you last night. There were a number of customers that were disconnected all at the exact same time and all connected to the same router within the BTWholesale network and were down for just under 15 minutes. Annoyingly I can't find the report that tells me who was affected by maintenance work but I'm 99% certain that's what it was.

[#4]

Just had another wobble.

This one appears to be prefaced with a blip in connectivity on the link layer between the router and the ONT -

2025-07-29T10:13:41.801302+01:00 gw2 kernel: [1810544.193997] igc 0000:07:00.0 enp7s0: NIC Link is Down

2025-07-29T10:13:44.745298+01:00 gw2 kernel: [1810547.138248] igc 0000:07:00.0 enp7s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Then an LCP echo-request timeout and session tear down and restart.  This one didn't see the PADO timeout though and the session was only down for about 40 seconds.

2025-07-29T10:14:11.765599+01:00 gw2 pppd[3542617]: No response to 3 echo-requests

2025-07-29T10:14:11.765864+01:00 gw2 pppd[3542617]: Serial link appears to be disconnected.

2025-07-29T10:14:11.765929+01:00 gw2 pppd[3542617]: Connect time 574.6 minutes.

2025-07-29T10:14:11.765977+01:00 gw2 pppd[3542617]: Sent 2104538027 bytes, received 2189539337 bytes.

2025-07-29T10:14:11.766472+01:00 gw2 pppd[3542617]: Script /etc/ppp/ip-down started (pid 3608290)

2025-07-29T10:14:11.769269+01:00 gw2 pppd[3542617]: Script /etc/ppp/ipv6-down started (pid 3608295)

2025-07-29T10:14:11.769397+01:00 gw2 pppd[3542617]: sent [LCP TermReq id=0x3 "Peer not responding"]

2025-07-29T10:14:11.770701+01:00 gw2 pppd[3542617]: Script /etc/ppp/ipv6-down finished (pid 3608295), status = 0x0

2025-07-29T10:14:11.774681+01:00 gw2 pppd[3542617]: rcvd [LCP TermAck id=0x3]

2025-07-29T10:14:11.774790+01:00 gw2 pppd[3542617]: Connection terminated.

2025-07-29T10:14:11.774828+01:00 gw2 pppd[3542617]: Connect time 574.6 minutes.

2025-07-29T10:14:11.793575+01:00 gw2 pppd[3542617]: Script /etc/ppp/ip-down finished (pid 3608290), status = 0x0

2025-07-29T10:14:41.841552+01:00 gw2 pppd[3542617]: Send PPPOE Discovery V1T1 PADI session 0x0 length 18

2025-07-29T10:14:41.843141+01:00 gw2 pppd[3542617]:  dst ff:ff:ff:ff:ff:ff  src 00:e2:69:xx:xx:xx

2025-07-29T10:14:41.843186+01:00 gw2 pppd[3542617]:  [service-name] [host-uniq  59 xx xx xx] [PPP-max-payload  05 dc]

2025-07-29T10:14:41.843774+01:00 gw2 pppd[3542617]: Recv PPPOE Discovery V1T1 PADO session 0x0 length 57

This wouldn't rise to a level that I would have bothered reporting, other than being part of the trial.  I'm not even sure why there was a blip on the link layer between the ONT and the router - that could easily be something on my end.

[#5]

Thanks for the update, Dave.

A maintenance window means I don't have to go digging through the ppp/network setup here looking for something that isn't quite right in my setup.

Cheers,

Mark

[#6]

---

@dave wrote:

There were a number of customers that were disconnected all at the exact same time and all connected to the same router within the BTWholesale network and were down for just under 15 minutes. Annoyingly I can't find the report that tells me who was affected by maintenance work but I'm 99% certain that's what it was.

---

If that was the case, it wasn't seen on A&A's network.

A&A have a real time scrolling monitor of network logins and logouts, great for identifying BTWholesale router dropouts.

As you can see below (from this morning) there was nothing unusual going on -

This shows the last 12 hours of logins and logouts. The current time on left. Green is login. Red is logout. If there are spikes, then this shows a large number of logouts or logins.

[#7]

I did write another post but that appears to have gone away about a short interruption at 10:13 today.

Moderator's note:
Post released from the automatic Spam Filter.

This time there was a PADO reply when trying to bring the link back up and everything recovered within about a minute.

1. Loss of NIC link between ONT and router for about 3 seconds

2. PPP LCP echo timeout reached 25 seconds later

3. PPP tear down took about a second

4. PPP re-establish started 30 seconds later ( PADI sent, PADO received immediately, and PPP negotiation was fine )

Just documenting as part of the trial.

[#8]

@MPC 

Have you considered setting up a ThinkBroadband Broadband Quality Monitor graph to chart your WAN connectivity ?

.

[#9]

I hadn't but have just set up a couple to monitor the IP4 and IP6 connectivity.

Thanks!

[#10]

@MPC  perhaps add your "Share Live Graph" links to @dave 's topic Thinkbroadband BQM Graphs 

so they can be compared to other customer's charts (when Dave gets time to tidy up the Ping Graphs page).

Having your live links in that topic, would also help with having more eyeballs looking at your charts, to see whether other customers can spot issues with your connection.

.

[#11]

Done.

[#12]

Is IPV6 generally available on PN or is it still in Trial Phase?

[#13]

Its still in Trial

[#14]

Any idea when it might come out of trial and become generally available..?  

It seems like it is working well from a user perspective...?

[#15]

@Ian06 

It does with caveats which I suspect they do not want to take into a full production service.