IPv6 Trial Update

[#1]

I'm still experiencing sporadic issues with my main Windows PC. The same issue occurs whereby Outlook Web Access takes 30-60 seconds to load an email - if I turn off IPv6 on the network adapter, it suddenly springs to life and works immediately, so it's definitely an IPv6 issue.

I need to do more testing on my Windows laptop, but I think it's potentially device specific. I've updated LAN drivers (Killer E3100G 2.5 Gigabit Ethernet Controller).

Testing sites like  https://ip6.biz/  and http://icmpcheckv6.popcount.org/ show no issues when experiencing this problem.

I don't think it's a software or built-in Windows firewall issue as ICMPv6 is completely enabled on both.

I'm at the point now of configuring Windows to use IPv4 over IPv6 where possible.

[#2]

@AndrewN I see problems sometimes accessing my amazon account from my Win 11 laptop. Seems to take an age to load up the account details. My lappie has an Intel AX201 NIC so it wouldnt appear to be NIC specific.

Dont see similar problems on my Android tablet.

In the very early stage of the trial, I did see some delays accessing email from k9 on the tablet. It sorted itself out in a few days so I put it down to IPv6 routing issues in the early stages.

[#3]

Thanks for your reply MJN,

Was working like a dream - and the only useful syslog entry - 

 WAN1 PPPoE <== Protocol:LCP(c021) ProtRej Identifier:0x18 Rejected Protocol: 0x8057

I've read a few forums entries and have tried lowering the MTU value from 1520 to 1492, even reset the router to defaults.

The next logical step is to downgrade the firmware to 3.9.9.9 just to see if the modem code is broken in 3.9.9.10 and trying another router.

I dont want to change too many things at once in case DLM kicks in and sends my line down from 17 to 2mbits lol.

Will let you all know what I find.

Andrew

[#4]

@AStokes 

If you can, drop the IP6 MTU to 1280.  That is required to be supported by all IP6 routers, and means you should never trigger any IP6 path MTU discovery issues.  It's a decent troubleshooting step that avoids some potential problems that aren't necessarily at your end of the connection.

Good luck!

Mark

[#5]

@dave 

What is my IP type services are not detecting my IPv6 address.

Test your IPv6. reports no IPv6 address.

Has something been changed?

Scratch that - looks like an issue with my Win10 platform! 

[#6]

Just to say has been and is still working for me here.

[#7]

Indeed, has not been a problem on the Win11 platform.

Following the above, I bounced the WiFi connection on the Win10 box and it all just stared working.  No idea what that did not have a IPv6 address.

[#8]

Morning @dave 

Is there any space left on the trial, or any info on when GA will actually be? I've been on plusnet for nearly 2 years so at my renewal point and I'm really after having Native IPv6 instead of having to tunnel it elsewhere....

Thanks!

[#9]

hi, its it still possible to join the IPv6 trail?

[#10]

@adambann_forum Nope - they have all the trialists they need.

[#11]

Mid-July and the setup has been very solid for me (other than the Cloudflare 1.1.1.1 outage earlier this week which is obviously not a plusnet issue).

Thanks for all at PlusNet who are doing the work on this behind the scenes.

Cheers,

Mark

[#12]

when will it be going live then?

[#13]

Your guess is as good as anyone's , but it isn't a quick fix.

[#14]

As it is a trial, I am reporting that I just had the pppoe session, and thus all internet connectivity IP4 and IP6 drop for approximately 13 minutes.

1. The pppoe session appeared to be lost at 00:26 on 29th July.

2. Scripted and manual attempts to restart the pppoe were failing with PADO response timeouts (wireshark not seeing the PADO responses).

3. The pppoe session was finally brought up successfully at about 00:39.

I'm not sure if the apparent timeout of about 13 minutes is due to something in my configuration or something else.

[ It is easy to find other reports of similar timeouts - https://www.snbforums.com/threads/pppoe-take-forever-to-reconnect-after-reboot.64479/ as one example.   ]

Other than this little blip, it continues to be a very solid and speedy service.

[#15]

At that sort of time, it could have been BT networks maintenance. Do we still have that link to recent planned maintenance over at A&A (or was it Zen)?