Aquiss Community

Thanks Martin. This worked well. I did some preliminary work to ensure that DNS was picked up automatically and propagated correctly across my network, because I had a couple of instances of the Entanet IPv4 DNS being hard set. IPv6 DNS I left alone as it had set itself up correctly when you enabled IPv6 for me nearly a year ago. I had also been using Entanet's DNS for NTP [undocumented feature], so I changed to google's NTP on IPv6.

So the change happened last night. I started everything up this morning, used the internet as normal, noticed no change and checked my router to discover that the migration had happened a few seconds after 0200 this morning. Speed check did not initially do much better than the 160 I was on. Hmm.

I checked IP addresses on my devices and discovered that besides the 2 expected public IPv6 addresses, I had another with the old prefix on my PC and my phone. Linux helpfully identified this as 'deprecated'. A restart of the WAN PPPoE on my router and restarts of the network on my phone and my PC and the deprecated addresses were gone and I am getting a fairly even just over 205 Mb/s for IPv4 and just under for IPv6 and about 30 Mb/s for upload.

I know you are at the tail end of the migrations, but probably worth a follow up email when they are done, suggesting a restart of the WAN interface or a router reboot just to be sure of top performance.

Thanks for the feedback @Watty

As you say we are towards the last few months or so with this process. The next couple of month or so is planned customer changes and then we expect a couple of months of dealing with complex jobs and stragglers/customer requested delays. Our aim is to be completed in May 2025.

All in all, it's gone very well, our detailed plans and internal system changes have gone incredibly well. I can't be more proud of the team here and collective mindset.

As part of the final checks, we do test every single circuit, but an added email sounds like a reasonable idea that we can introduce quite easy.