Know before
you field it.
Nobody buys CHAOS for the chaos. They buy knowing how their system behaves when the network turns hostile. Patch it in between two sites, give the link the network your system will meet, and leave with a sealed answer. This is that bench, in your browser.
- 01Patch in
- 02Bring it up
- 03Give it the field
- 04Get the verdict
Put CHAOS in the path.
Site A is a drone ground station; Site B is the ops centre that depends on its feed. Drag Site A's cable into PORT1, then the other into the other port. CHAOS is a transparent bridge, so nothing on either side gets reconfigured.
██████╗██╗ ██╗ █████╗ ██████╗ ███████╗ ██╔════╝██║ ██║██╔══██╗██╔═══██╗██╔════╝ ██║ ███████║███████║██║ ██║███████╗ ██║ ██╔══██║██╔══██║██║ ██║╚════██║ ╚██████╗██║ ██║██║ ██║╚██████╔╝███████║ ╚═════╝╚═╝ ╚═╝╚═╝ ╚═╝ ╚═════╝ ╚══════╝
- applied
- —
- thrpt
- —
- pps
- —
- drops
- —
- backlog
- —
- applied
- —
- thrpt
- —
- pps
- —
- drops
- —
- backlog
- —
Nothing is reaching Site B yet. Patch both sites into CHAOS to bring the link up.
- Class
In-line transparent L2 WAN-emulation T&E
- Form Factor
Rackmount fanless-class N-series
- Data-Plane Capacity
1 Gbps bidirectional · per-direction impairment
- Data Ports
2 × 2.5GbE Intel i226-V · per-port PHC
- Throughput Headroom
2 × 10GbE reserved · future high-rate
- Root of Trust
TPM 2.0 hardware-bound identity
Impair it. Capture it.
Prove it.
Impairment Engine
01- ›Latency — constant + stochastic distributions
- ›Jitter, loss, duplication, reordering, corruption
- ›Rate limiting + bounded-queue drop
- ›Per-direction control; time-varying scenarios (TOML)
Defensible Artifacts
02- ›Per-port PHC hardware-timestamped pcaps
- ›Structured event log + system-state snapshot
- ›Sealed bundle — SHA-256 manifest, immutable
- ›HTML / Markdown / PDF report with attestation
Control & Posture
03- ›Web UI primary · full HTTP/JSON API · service CLI
- ›TPM 2.0 hardware-bound identity
- ›In-line transparent L2 — no DUT reconfiguration
- ›Per-port PHC hardware timestamping
Drop in-line
Place the appliance on any link. Transparent at Layer 2 — no DUT reconfiguration required.
Author / replay
Define a network-conditions scenario in TOML, or replay a captured one. Per-direction, time-varying.
Walk away
Leave with a sealed, hardware-timestamped test artifact that holds up under technical scrutiny.
Defensible by design.
Prototype available.
CHAOS runs on the ETHRX-ONE hardware platform — a TPM-anchored, hardware-timestamped appliance built for test & evaluation that has to survive scrutiny. The CHAOS-2 prototype reference unit is a candidate SKU available for evaluation today.
