mentalinc:

 

So basically four weeks after the migration to the new network, my issue is finally resolved.

 

 4+ calls to contact centre plus 10-20 hours of trying to get it work...

 

 

 

The issue was old static IP was on the old snap network, and IPv6 was populated with my IPv4 address.

 

First call today they allocated me a new IPv4 and IPv6 static address (two prior calls didn't do this as didn't know how or impacts of pressing this button in the backend).

 

BuT the provision didn't work this morning properly (was meant to be a 15-20 min change). 5 hours later still hadn't been fixed.

 

Call number 2 today, finally had them kick my session on their end. 

 

Power cycle of router finally got the new IPv4 and IPv6 addressing working.

 

 

 

In short VERY disappointing experience and really limited skill and understanding in the contact centre to manage the migration and issues from old to new network.

 

 

 

As soon as was fixed, my internet speeds/browsing sites has increased (as assume ipv6 no longer erroring and slowing it all down).

 

Now running on DHCP - no idea if pppoe is working.

 

@freitasm - you may have similar issues if you had a static IP address and been there 3+ years and were cycled from static to cg-nat to static on snap side.

 

My account is ~4 years old and also had a static IP assigned after 2D moved everyone onto CG-NAT, so I'm guessing IPv6 is broken on my account for the same reason (have turned it off on the Fritzbox for now).

What I don't understand is why 2D hasn't done a validation pass over all accounts with a static IP, checking for v4 addresses in the v6 field, and proactively fixing them, rather that forcing everyone to spend hours/days troubleshooting and talking/on hold with their call center...