You are reading the documentation for v1.3.0. The current release is v1.4.0.

New features

Onboarding scale and throughput [controller] (#11, #27)

  • Punt→DHCP processing is no longer strictly serial. Punts are fast-consumed,
    deduplicated by subscriber identity and applied in batched session adds, so
    completion no longer collapses as the concurrent-request rate rises.
  • Onboarding throughput no longer degrades cumulatively under heavy load, and
    no longer needs a restart to recover.

Measured. Against a 900/s requested in-rush, the box completes the cold
phase at ~600 subscribers/s (run 670: 605.65/s cold, 491.8/s warm; runs
663/665/669/670 average ~610/s cold), with limited_by: none — neither the
BNG nor the load generator saturated at that rate. Earlier in the cycle the
same suite could only request 220/s; the generator-side work in CPESIM 0.4.16
is what made a rate this high askable, and the box answered it.

Bulk local-AAA provisioning [controller + console] (#26)

Gated-mode admission previously required one PUT per subscriber line, which
serialised through the controller and collapsed provisioning throughput at
scale. A bulk endpoint loads many lines in one atomic call.

The console's bulk subscriber import was rewritten onto that atomic endpoint,
with batched subscriber and session reads and an all-or-nothing result
state
— a partial import no longer leaves the operator guessing which rows
landed. The per-row console path cost three controller round-trips per
subscriber (a record GET, a full session-list GET, and the record PUT), which
is what held CSV import to ~2/s before this change.

Captive-portal URL via DHCP Option 114 [controller] (#25)

The DHCP OFFER/ACK path emits Option 114 (RFC 7710 / 8910) carrying the
captive-portal metadata URL, so iOS 12+, Android 10+, macOS 10.13+ and
Windows 10 2004+ natively detect the captive network and open the sign-in flow.
No DNS-interception fallback required.

Out-of-contract DSCP marking [controller + console] (#19)

The per-subscriber trTCM policer DSCP-marks yellow (out-of-contract) traffic as
AF11 on both upstream and downstream paths, so downstream devices can
differentiate in- from out-of-contract packets. Previously yellow was counted
but forwarded byte-identical to green; green/red behaviour is unchanged (red
still dropped). The console gained a DSCP marking policy section on the
Dataplane page
to set it, and the dashboard's QoS panel captions the
active marking state.

RADIUS diagnostics on the audit timeline

radius-exchanges joins qt-events as a source on the audit timeline:
decoded, linted RADIUS exchanges shown beside everything else that happened on
the box, so a failing subscriber authentication can be read without leaving the
console or running tcpdump by hand.

Off by default, and opt-in. When enabled, the box elects a single capture
owner so four gunicorn workers cannot start four dumpcap children over one
ring buffer, and every path where a capture was requested but could not be
started publishes that fact rather than showing an empty feed. With capture
off, the timeline's "no tap" clause is a true statement rather than an absence
of evidence.

RADIUS shared secrets are read for verification and never emitted — the
timeline distinguishes thirteen secret states without printing one.

Prometheus read proxy

A same-origin read proxy for Prometheus with a default-deny allowlist,
registered on /api/bng and forwarding allowlisted reads unwrapped. This is
what lets a Grafana instance query the box without handing it broad access, and
it pairs with the scoped metrics-only API key preset below.

Grafana dashboard pack

A curated BNG dashboard pack, installable in one click from About → Toybox,
with a multi-select download. Platform Health reads the host rather than a
metric that never populated, and host sections sort above the fold.

Supporting work: a Prometheus read proxy with a default-deny allowlist, and
a Grafana/metrics-only API key preset with a 365-day default expiry and a
visible path_scope, so a dashboard key is visibly scoped to what it can read.

Observability

IPMI chassis sensors are exported to Prometheus, and Prometheus alerting rules
ship wired into rule_files.