Interesting post by Cloudflare on detecting #CGNAT as well as the performance and availability impacts to users behind it: https://blog.cloudflare.com/detecting-cgn-to-reduce-collateral-damage/

[nygren@hachyderm.io]

Interesting post by Cloudflare on detecting #CGNAT as well as the performance and availability impacts to users behind it: https://blog.cloudflare.com/detecting-cgn-to-reduce-collateral-damage/

This re-enforces the importance for both:
1) content providers to dual-stack sites (so that #IPv6 end-users can bypass CGNAT)
2) the importance for networks to deploy IPv6 alongside CGNAT so that only a shrinking subset of traffic needs to go through CGNAT

Of particular concern is the concentration of CGNAT in the developing world, creating even more risk of a multi-tier Internet with an IPv6-centric modern internet but with other parts of the world being stuck in the past with IPv4 CGNAT.

[nuintari@mastodon.bsd.cafe]

@nygren I've deployed CGNAT on four networks now, and every single time I have to explain to managemeny, endlessly, that every byte of traffic we can offload to #IPv6 is a byte of traffic we didn't have to move through the expensive CGNAT stack.

IPv4 is expensive, IPv6 is cheap.