Describe your edge
Access handoffs, VLAN/QinQ, CPE types, PPPoE/IPoE mix, MTU, subscriber identity and upstream connectivity.
Good questions.
Clearer decisions.
Practical starting points for a product conversation, a topology review or your next platform evaluation.
Bring the right information.
Describe the workload
Busiest-hour bandwidth, packet-size mix, subscribers, simultaneous flows, new-flow rate and routing scale.
Describe the operation
RADIUS, billing, service profiles, mapping retention, staff roles, maintenance windows and incident escalation.
Define recovery
Acceptable interruption, session continuity, configuration recovery, backup needs and site-loss expectations.
Define acceptance
A representative test topology, enabled features, thresholds, evidence capture and ownership of results.
Plan the return path
Source configuration, address ownership, routing, subscriber reconnection and accounting reconciliation.
Straight to the useful part.
Is LiquidNAT an internet service provider?
LiquidNAT is an ISP network software platform. The customer operates the infrastructure and subscriber network; the product business supplies software and related services.
Do we have to replace the entire network?
Start with standalone CGNAT, a combined subscriber edge or the management and identity workflows you want to improve. Choose scope around your topology.
How should we compare performance?
Ask for a defined hardware/software profile and repeatable tests with the intended features enabled. Include packet rate, flow churn, logging, latency and recovery headroom.
Can we keep our billing or RADIUS platform?
Bring the current APIs, RADIUS attributes and lifecycle requirements to a technical review. Integration depends on the exact products, versions and workflows.
Where does migration start?
Inventory the service model, map the target configuration, validate representative journeys and agree a staged transition with a return path.
Is a browser demonstration a throughput test?
A browser simulation explains the interface and workflows. Packet processing, capacity and recovery require technical tests on the applicable system.
How do we discuss pricing?
Use the contact page. Share the intended deployment, capacity requirements, support expectations and migration scope so the conversation has the right context.