How much public IPv4 do I need with CGNAT?

It depends on your sharing ratio and traffic profile. Deterministic port-block allocation makes the math simple: pool size = subscribers divided by sharing ratio. NAT port-pressure analytics then show real headroom per subscriber, so you can tighten or relax ratios with data instead of guesswork.

GridM BNG · CGNAT + IPv6

Stretch IPv4. Ship IPv6. Stay compliant.

Deterministic CGNAT with port-block allocation and court-ready logging runs in the same hop as native dual-stack IPv6 with prefix delegation. One data plane handles both, and the console shows exactly how hard your address space is working.

Request a demo All capabilities

Illustration mirrors the shipping GridM BNG console. Identifiers are fictional.

What ships in the box

IPv4 address pools with DHCP and static assignment
Native dual-stack: IPv6CP, SLAAC and DHCPv6 prefix delegation
Integrated CGNAT (NAT44) with deterministic NAT and port-block allocation
Per-session NAT logging and IPDR export for lawful compliance
NAT port pressure analytics to right-size public pools

Deterministic NAT44

Every subscriber gets a predictable public IP and port block at the sharing ratio you choose. Port pressure analytics show usage, peaks and blocked connections per subscriber, so pools are sized on data.

Dual-stack by default

IPv6CP, SLAAC and DHCPv6-PD hand every CPE a delegated prefix alongside IPv4. Adoption cohorts separate working IPv6 from broken CPEs, and the broken list exports as a support call list.

Logging that stands up

Per-session NAT mappings are logged and exportable as IPDR. Given a public IP, port and timestamp, the console resolves the subscriber in seconds, which is exactly what a legal request needs.

Reference

CGNAT + IPv6: the spec card

Addressing

IPv4: Pools, DHCP, static, framed routes
IPv6: Dual-stack, IPv6CP, SLAAC, DHCPv6-PD
CGNAT: NAT44, deterministic NAT, port-block allocation, NAT logging

FAQ

CGNAT + IPv6, in detail

Both, natively. Dual-stack IPv6 with IPv6CP, SLAAC and DHCPv6 prefix delegation runs alongside IPv4, and integrated CGNAT (NAT44 with deterministic NAT and port-block allocation) conserves public IPv4. NAT sessions are logged and exportable as IPDR for lawful compliance, with port-pressure analytics to plan pool sizing.

Explore the rest of the platform

Session termination RADIUS AAA + CoA QoS + plan enforcement Line-rate data plane High availability Observability Central web console Security & compliance

See cgnat + ipv6 on live traffic

Book a live demo with a network engineer. We will walk your topology, size the hardware and show real sessions terminating on the console, not slides.

Request a demo Talk to sales

Runs on your hardware · One plan, every feature · Migrate in slices