A carrier BNG and CGNAT that runs on commodity x86.
PPPoE and IPoE termination, carrier-grade NAT, hierarchical QoS and ACLs — one XDP data plane, 50 Mpps per box with every feature enabled. No appliance. No per-subscriber licence tied to hardware.
PPPoE and IPoE termination, carrier-grade NAT, hierarchical QoS and ACLs — one XDP data plane, 50 Mpps per box with every feature enabled. No appliance. No per-subscriber licence tied to hardware.
A proof of concept runs on your own x86 against your traffic. Send subscriber count and busy-hour throughput and we size it with you.
Work it against your own traffic rather than our assumptions. Packet size, not gigabits, is what decides the answer.
One data plane does termination, translation, shaping and filtering. No separate CGNAT appliance, no separate edge router, and no per-feature licence to negotiate.
Seven jobs the subscriber edge has to do, and one forwarding path that does all of them. Same XDP data plane, same commodity server — termination, translation, traffic management and border routing become configuration, not four more boxes in the rack.
Port-block NAT44 with per-subscriber pressure sensing, plus NAT64 and MAP-T/MAP-E for IPv6-only access.
PPPoE and IPoE termination, RADIUS AAA with CoA, hierarchical QoS and QinQ — 50 Mpps per box.
Built from source into one signed artefact that boots to a RAM root. Every node verifiably runs the same code.
Cache and accelerate at the edge — less upstream transit, faster page loads for subscribers.
TV apps, edge cache, timeshift, VOD and EPG for operator-run television.
Anti-spoof, DDoS mitigation and abuse containment at the subscriber edge, before traffic reaches your core.
Border routing on the same box that terminates subscribers — no separate edge router to licence.
BNGSOFT is a team of ten. There is no support tier between you and the people who wrote the forwarding path — when a network card driver misbehaves at line rate, the person who answers is the person who fixes it.
That is why security patches ship in days instead of release trains, and why a proof of concept is a conversation with engineers rather than a procurement process.
Contact us if you need a solution.