Why a special range
Before 2012, operators deploying CGNAT used RFC 1918 private ranges like 10.0.0.0/8 between the subscriber’s home router and the CGNAT. But home networks use those same ranges, causing conflicts. RFC 6598 set aside 100.64.0.0/10 as shared address space for this purpose.
How it is used
Subscribers’ routers receive addresses from 100.64.0.0/10 on their WAN side. CGNAT translates them to public addresses.
Keep it internal
Shared address space must never be announced on the internet. Treat it as a bogon and filter it on external BGP sessions — as Peer1IX route servers do.
Pitfalls
Some applications treat 100.64.0.0/10 as public and behave unexpectedly. Test key applications in a CGNAT environment.
Check whether any range is bogon space with our BGP security tool.
