Lots of issues with (arguably broken) sites, that don't like it when your ipv4 address changes
A broken cable modem for month (mandatory, btw) that went into a freeze whenever the ipv6 prefix was renewed (not even changed, necessarily): Every 2-3 days the box locked up.
While I appreciate the 'No addresses left' argument, I was 'upgraded' to this crap. Before that I had a (dynamic) ipv4. My cable provider sits on ipv4 addresses and won't jump from providing cable in Germany into the huge Indian/Chinese market and run out of addresses.
Why do we allocate huge networks (was it a /10 recently?) to Akamai if we're scarce?
No way to access my home machines anymore. Dyndns is dead. I could implement that for ipv6 and that would be even better in theory, alas .. most people/networks/mobile carriers are on ipv4. So my AAAA is utterly useless, even if I keep it up to date.
In the end I'm a fan of ipv6. I ran ipv6 tunnels in the past, native ipv6 is cool. Somewhat. CGNAT is bullshit for the reasons above and more and forcing it down to your customers is a tough sell (-> The ISP loses goodwill here). For new or exploding markets? Probably no other way. Here it's just useless. Dual Stack is fine, DS Lite causes trouble again and again in my setup here.
And there's never an excuse for a known issue that requires your customers to unplug the cable modem you provided, because .. well .. it's not quite ipv6 ready yet. [1]
1: That was an issue for month, was solved around end of February. Support hotline knew about it, device manufacturer knew about it, official workaround see above.
Comments
Lots of issues with (arguably broken) sites, that don't like it when your ipv4 address changes
A broken cable modem for month (mandatory, btw) that went into a freeze whenever the ipv6 prefix was renewed (not even changed, necessarily): Every 2-3 days the box locked up.
While I appreciate the 'No addresses left' argument, I was 'upgraded' to this crap. Before that I had a (dynamic) ipv4. My cable provider sits on ipv4 addresses and won't jump from providing cable in Germany into the huge Indian/Chinese market and run out of addresses.
Why do we allocate huge networks (was it a /10 recently?) to Akamai if we're scarce?
No way to access my home machines anymore. Dyndns is dead. I could implement that for ipv6 and that would be even better in theory, alas .. most people/networks/mobile carriers are on ipv4. So my AAAA is utterly useless, even if I keep it up to date.
In the end I'm a fan of ipv6. I ran ipv6 tunnels in the past, native ipv6 is cool. Somewhat. CGNAT is bullshit for the reasons above and more and forcing it down to your customers is a tough sell (-> The ISP loses goodwill here). For new or exploding markets? Probably no other way. Here it's just useless. Dual Stack is fine, DS Lite causes trouble again and again in my setup here.
And there's never an excuse for a known issue that requires your customers to unplug the cable modem you provided, because .. well .. it's not quite ipv6 ready yet. [1]
1: That was an issue for month, was solved around end of February. Support hotline knew about it, device manufacturer knew about it, official workaround see above.