Product / Router & CPE

The LAN side of the lab.

A R3S/OpenWrt surface for multi-CPE inventory and local policy drafts — designed to show state before changing it, and to keep routing changes manual.

OpenWrtR3SMulti-CPELab build

Multi-CPE inventory

See multiple CPEs in one view and select the one you mean. Discovery does not imply control or a route change.

Dry-run policy

Local policy JSON is a draft. It is not automatically synced to R3S, and it does not silently apply firewall or routing rules.

Manual apply

Applying a change is a separate, explicit action with a rollback path. The lab build does not claim unattended production routing.

What it is

A router panel that does not surprise you.

The router surface is for labs with more than one CPE, a R3S board, or a need to see device and policy state without SSHing into every box. It is intentionally conservative: visibility first, drafts second, apply last.

R3S / OpenWrt

The current handover includes an ARM64 OpenWrt tarball built locally. It was not deployed to the router in the UI11 handover, so “built” is not “running on your network”.

Authorization is explicit

Remote router pages may require an authorization link or session. SIMCAT does not bypass a 401 or invent a credential. If the page is not authorized, the panel says so.

No automatic route changes

Policy JSON is a local draft. DNS, routing, firewall, VPN and proxy changes remain manual and outside the default write path.

$simcat router inventory --local
→CPE A reachable · CPE B auth required
→policy: draft only · apply: manual
→route changes: 0
$simcat router export --dry-run
→wrote local-policy.json (not applied)
✓ Visibility first · draft second · apply last

Planning a multi-CPE lab?

Start with the router branch and the current handover notes. Bring your authorization and rollback plan.