Access requirements
List PPPoE, IPoE, relay behaviour, CPE profiles and any L2TP requirements. Ask each supplier to identify exact supported configurations.
Compare with context.
Choose with confidence.
A useful comparison looks at your actual deployment requirements and the exact scope of each product family.
Start with the jobs to be done.
| Network job | LiquidNAT family | netElastic public product family |
|---|---|---|
| Broadband subscriber edge | LiquidNAT Gateway architecture | Virtual BNG |
| IPv4 address sharing | Gateway CGNAT architecture | Carrier-Grade NAT |
| Network routing | Gateway with FRRouting integration | Virtual Router |
| Operational interface | LiquidNAT Manager | netVision Router Manager |
| Subscriber identity | LiquidNAT RADIUS product focus | Confirm authentication integration for the proposed configuration. |
netElastic family names and positioning: official product overview ↗, reviewed 5 November 2026. These mappings identify areas to evaluate; they do not establish equivalent capabilities, availability, scale or commercial terms. Trademarks belong to their owners.
Put both proposals through the same test.
CGNAT behaviour
Compare protocols, allocation modes, mapping retention, lookup workflows and outcomes when logging or pools are under pressure.
Operational fit
Ask each supplier to demonstrate a failed login, wrong VLAN, pool exhaustion and package change using the proposed system.
Performance evidence
Use the same hardware basis, traffic mix and enabled features. Compare simultaneous flows and new-flow rate alongside bandwidth.
Resilience
Separate NAT flow continuity, subscriber continuity, packet interruption and route convergence. Request failure-test evidence.
Commercial fit
Request written software, hardware, support, renewal, migration and capacity terms. Compare cost over your own planning period.
The subscriber journey
connects the stack.
That is the organising idea behind LiquidNAT Gateway, RADIUS and Manager: join the edge, identity and operations around the service your customer receives.
Bring your requirements, existing topology and shortlist. The most valuable comparison is the one that reflects the network you actually operate.
Discuss your shortlist ↗