Broadband network gateway
Plan PPPoE or IPoE termination around subscriber identity, circuit information, address assignment and service policy. Include the handoff, VLAN/QinQ and MTU in your design.
Your edge.
More possibility.
Explore a software broadband edge that brings subscriber access, CGNAT and routing into one architectural conversation.
From access circuit to internet.
Carrier-grade NAT
Connect private subscriber addressing to public IPv4 resources. Consider port allocation, TCP/UDP/ICMP behaviour, exhaustion and mapping traceability together.
Dual-stack services
Treat IPv4 and IPv6 as one service. Include prefix delegation, neighbour discovery, path MTU and subscriber policy in both directions.
Routing integration
Align forwarding intent with BGP/OSPF control through FRRouting integration. Review route policy, next-hop behaviour and traffic symmetry.
Service enforcement
Define upload/download policy, aggregate limits, ACLs and subscriber resource limits as explicit, reviewable service intent.
Recovery planning
Separate configuration recovery, address ownership, NAT flow continuity and subscriber session continuity. Set expectations for each failure domain.
ADDRESS ECONOMICSIPv4 is valuable.
IPv4 is valuable.
So is your time.
A CGNAT decision goes beyond conserving addresses. You also need an answer when a pool fills, a subscriber consumes too many ports or an attribution query arrives.
Understand allocation
Compare public address use, subscriber port demand, pool separation and allocation modes for your traffic mix.
Think in tuples and time
Traceability needs the external address, port, protocol and timestamp, connected to allocation and subscriber history.
Plan for pressure
Separate address exhaustion, port exhaustion, state-table pressure and CPU limits in the capacity review.
Start where your network needs you.
Alongside your BNG
Evaluate standalone CGNAT behind your existing subscriber platform. Define traffic symmetry, pool ownership and routing boundaries.
A connected broadband edge
Bring access, identity and translation into a combined design. Review handoff, MTU, CPE compatibility and service policy together.
A regional footprint
Map gateways to regional failure domains with central operational intent. Keep local resilience and site disaster recovery distinct.
Sizing starts with your workload: packet sizes, simultaneous flows, new-flow rate, subscriber churn, routes, logging and recovery headroom. Request a deployment-specific technical review.