Need Solution?
Contact us if you need a solution.
Four tools we built for our own sizing conversations, with the assumptions written down beside them. No sign-up and nothing leaves your browser — the arithmetic runs on this page.
Subscribers, busy-hour bandwidth each and the frame size you carry go in; the packet rate, the line rate and the number of commodity servers that cover it come out. Open the calculator.
How many public IPv4 addresses a port-block CGNAT deployment actually needs at your subscriber count — and what the addresses you stop buying were worth. Open the calculator.
Convert packets per second into line rate at any frame size, and see what a datasheet Gbit/s number quietly assumes about frames and features. Open the calculator.
Which of the seven forwarding stages a packet actually touches, for three deployment models — subscriber gateway, full data plane, or translation only. Open the explorer.
Most of these started as a spreadsheet we kept re-deriving in front of operators. They encode the arithmetic we use ourselves: packets per second as the real limit, port blocks rather than per-flow NAT, and commodity servers rather than a chassis. The figures they lean on are the ones we publish — 50 Mpps per box with PPPoE, CGNAT, hierarchical QoS and ACLs all enabled — and every one of them is reproducible on hardware you already own.
Contact us if you need a solution.