A BNG (Broadband Network Gateway) is the service provider device that terminates subscriber connections. It identifies the subscriber, authenticates them against RADIUS, assigns an IP address, enforces the speed profile and policy, and keeps accounting records for the life of the session. It is the first intelligent point between the access network and the IP core: every subscriber session starts and ends here.
The term became common with the Broadband Forum's TR-101, which described Ethernet-based broadband aggregation. Older networks called the same role a BRAS (Broadband Remote Access Server). Whether access is fibre, wireless or DSL, the moment a subscriber "gets online" is really the moment a session comes up on the BNG.
Where does a BNG sit in the network?
On a typical provider network, subscriber traffic follows this path:
- Subscriber CPE or ONT: the device at the home or business.
- Access network: OLT, wireless base station or DSLAM, carrying traffic on per-subscriber or per-service VLANs.
- Aggregation: VLANs from the access devices are collected.
- BNG: the subscriber session terminates; everything beyond is routed.
- CGNAT, DPI and edge router: address sharing, traffic visibility and the upstream connection.
Below the BNG the network is mostly layer 2 and sees a subscriber only as a VLAN or MAC address. Above it, traffic is routed using an IP address that belongs to a known subscriber. That is why every per-subscriber decision (speed, quota, access rights, records) is made on the BNG.
What a BNG does
Subscriber termination
The two common models are PPPoE and IPoE. With PPPoE the CPE builds a PPP session with a username and password; with IPoE the subscriber gets an address over DHCP and is identified by VLAN or DHCP option 82. For a detailed comparison, see PPPoE or IPoE?.
AAA: authentication, authorisation and accounting
The BNG does not hold the subscriber database itself; it asks RADIUS:
- Access-Request: the BNG sends the subscriber's credentials to RADIUS.
- Access-Accept: RADIUS returns the address pool, speed profile and policy as attributes. Invalid credentials get an Access-Reject.
- Accounting: a Start record when the session begins, Interim-Update records at regular intervals and a Stop record when it ends. These records underpin billing, quota tracking and the subscriber-to-IP mapping that compliance logging depends on.
Address assignment
The BNG gives the subscriber an IPv4 address; on networks running CGNAT this usually comes from the 100.64.0.0/10 shared address space. On the IPv6 side, alongside a WAN address, DHCPv6 prefix delegation hands out a prefix (for example a /56) for the subscriber's LAN. For dual-stack subscribers both address families are tied to the same session.
Per-subscriber QoS and shaping
Each subscriber is held to a speed profile that matches their plan. In the download direction, shaping (queuing excess traffic) usually gives a better experience than policing (dropping it), because TCP sees less packet loss. Priority classes let latency-sensitive traffic such as VoIP jump ahead of the same subscriber's other traffic.
Changes on the fly: CoA
RADIUS Change of Authorization (RFC 5176) applies a new profile while the session stays up. Plan upgrades, slowing a subscriber down when a quota runs out or redirecting them to a payment reminder page all happen without a drop. The Disconnect-Message defined in the same RFC closes a session remotely.
The life of a PPPoE session
- Discovery: the CPE broadcasts a PADI, the BNG answers with a PADO. The CPE confirms with a PADR and the BNG assigns a session ID in the PADS.
- LCP: the MRU (usually 1492) and the authentication method are negotiated.
- Authentication: PAP or CHAP credentials are passed through the BNG to RADIUS.
- IPCP and IPv6CP: addresses are assigned, followed by DHCPv6 prefix delegation.
- Accounting-Start: traffic starts flowing and Interim-Update records are sent regularly.
- Termination: a PADT, lost LCP keepalives or a Disconnect-Message close the session, and an Accounting-Stop is sent.
BNG, CGNAT and edge router: who does what?
| BNG | CGNAT | BGP edge router | |
|---|---|---|---|
| Main job | Subscriber termination and AAA | Sharing IPv4 addresses | Upstream and peering |
| How it sees subscribers | Session and identity | Private IP and port block | It doesn't; it works per prefix |
| Typical features | PPPoE, IPoE, RADIUS, CoA, QoS | NAT444, PBA, EIM/EIF | Full table, RPKI, FlowSpec, BFD |
| Records it keeps | Subscriber, session times, private IP | Private IP, public IP, port block | Route and peer changes |
The three can run on separate devices or on one platform. On small and mid-size networks, running the BNG and CGNAT together cuts both the device count and the work of correlating subscriber records.
How to size a BNG
- Concurrent subscriber sessions: sessions up at peak. Licensing usually follows this figure.
- Peak throughput: total subscriber traffic during the evening busy hour.
- Session setup rate: after a power cut or an OLT reboot, thousands of CPEs try to reconnect at once. Both the BNG and RADIUS must absorb that reconnect storm.
- RADIUS availability: if RADIUS is unreachable, no new subscriber can connect. Configure at least two RADIUS servers with sensible timeouts.
- Per-subscriber feature load: dual-stack, multi-class QoS and extra policies all increase the state held per subscriber.
Redundancy
A single BNG is a single point of failure for every subscriber behind it. There are two common approaches: an active/standby pair that synchronises session state, or subscribers spread across several BNGs so that CPEs reconnect to another one when a device fails. Because several BNGs can answer a PADI with a PADO, the second approach is easy to build with PPPoE, but subscribers see a short reconnection outage when a box fails.
With CoreGate BNG
CoreGate BNG terminates PPPoE and IPoE on the same platform on different VLANs, connects to your existing AAA and billing with standard RADIUS attributes and applies plan changes through CoA without dropping sessions. Per-subscriber QoS, dual-stack addressing and session start and stop records come built in. Licensing follows concurrent PPPoE subscribers in five tiers from BNG-8K to BNG-128K, and clusters of up to 16 nodes with automatic failover remove the single point of failure. You can also run it alongside CoreGate CGNAT on the same platform.