Land the LiteBeam 5AC XR and the LAN/WAN split on the UISP Console (gh #1442) #1125

Merged
jaylouisw merged 1 commit from contrib/uisp-lbe2 into main 2026-11-08 20:28:19 +00:00
Owner

Carried across from GitHub pull request #1442 by the gh-bridge.

Most of that branch had already landed on the forge in pieces — the DrayTek VigorSwitch 2540x pair, the regenerated example labs and their drift test, the README rewrite. What was still missing is here.

LiteBeam 5AC XR (new)

5 GHz 802.11ac CPE from the vendor figures: 450 Mbps, one GbE with 24 V passive PoE in, 20 dBi.

UISP Console, corrected

The version on main had eleven data ports and no notion of which side they were on — so a lab could show LAN traffic passing straight to the WAN port, and the gateway role meant nothing. This carries the vendor interface table's real split:

  • 8 × LAN GbE RJ45 + 1 × LAN 1/10G SFP+
  • 1 × WAN GbE RJ45 + 1 × WAN 1/10G SFP+
  • LAN ports in one bridge group; the WAN side carrying the wan role

30 checks in test/uisp-console-lbe-xr.test.js, and the full suite with it — 113 suites, 4998 assertions, 0 failed.

The doc guard earned its keep immediately

Adding the device flipped the catalogue counts, and test/doc-catalog-counts.test.js — added two PRs ago — failed on the spot: 1,718 models, Ubiquiti 318, document says 1,717 / 317. Updated in the same commit. That is the whole point of it: a number in prose is a claim, and now something checks it.

Closes #1069.

Carried across from GitHub pull request #1442 by the `gh-bridge`. Most of that branch had already landed on the forge in pieces — the DrayTek VigorSwitch 2540x pair, the regenerated example labs and their drift test, the README rewrite. What was still missing is here. ### LiteBeam 5AC XR (new) 5 GHz 802.11ac CPE from the vendor figures: 450 Mbps, one GbE with 24 V passive PoE in, 20 dBi. ### UISP Console, corrected The version on main had eleven data ports and **no notion of which side they were on** — so a lab could show LAN traffic passing straight to the WAN port, and the gateway role meant nothing. This carries the vendor interface table's real split: - 8 × LAN GbE RJ45 + 1 × LAN 1/10G SFP+ - 1 × WAN GbE RJ45 + 1 × WAN 1/10G SFP+ - LAN ports in one bridge group; the WAN side carrying the `wan` role 30 checks in `test/uisp-console-lbe-xr.test.js`, and the full suite with it — **113 suites, 4998 assertions, 0 failed**. ### The doc guard earned its keep immediately Adding the device flipped the catalogue counts, and `test/doc-catalog-counts.test.js` — added two PRs ago — failed on the spot: *1,718 models, Ubiquiti 318, document says 1,717 / 317*. Updated in the same commit. That is the whole point of it: a number in prose is a claim, and now something checks it. Closes #1069.
Land the LiteBeam 5AC XR and the LAN/WAN split on the UISP Console (gh #1442)
Some checks failed
CI / Test (Node 20) (pull_request) Successful in 1m53s
CI / Test (Node 18) (pull_request) Successful in 1m57s
CI / Server smoke test (pull_request) Successful in 35s
CI / Docker build (pull_request) Successful in 46s
CI / Test (Node 22) (pull_request) Successful in 1m43s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Failing after 18s
8f34db125a
Carried across from GitHub pull request #1442. Most of that branch was already on main —
the DrayTek 2540x pair, the regenerated example labs and their drift test all landed
separately — so what is here is the part that was still missing.

**LiteBeam 5AC XR** — a new device from the vendor figures: 5 GHz 802.11ac CPE, 450 Mbps,
one GbE with 24 V passive PoE in, 20 dBi.

**UISP Console, corrected.** The version on main had eleven data ports and no notion of
which side they were on, so a lab could pass LAN traffic to the WAN port and the gateway
role meant nothing. This carries the vendor interface table's split: 8 LAN GbE RJ45 + 1
LAN 1/10G SFP+, 1 WAN GbE RJ45 + 1 WAN 1/10G SFP+, LAN ports in one bridge group, the WAN
side carrying the `wan` role.

30 checks in `test/uisp-console-lbe-xr.test.js`, and the whole suite with it —
113 suites, 4998 assertions.

Also the catalogue counts in `docs/DEVICE_REGISTRY.md`: the guard added in #1123 caught
this the moment the device landed (1,717 → 1,718 models, Ubiquiti 317 → 318), which is
exactly what it is for.

Co-authored-by: the contributor on GitHub pull request #1442
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1125
No description provided.