devices(ubiquiti): the Dream Router's LAN bank is a bridge, and its fifth socket is the WAN #2346

Merged
jaylouisw merged 1 commit from catalogue/1121-0122 into main 2026-11-21 01:39:20 +00:00
Owner

Refs #130. This request stays open: the Dream Wall Pro has no vendor page, datasheet or storefront SKU, and nothing here invents one. What it does is take the nearest row in the family that does have a vendor record and fix a defect the Dream Wall Pro request would inherit if it ever lands - the LAN bank modelled as routed ports.

UDR (devices/ubiquiti/udr.json)

claim vendor surface
the console is a switch deviceCapabilities for sku UDR include GATEWAY, SWITCH, ACCESS_POINT, NETWORK_APPLICATION, PROTECT_APPLICATION, CONTROLLER, APPLICATION_MODE, HAS_CLIENTS - https://static.ui.com/fingerprint/ui/public.json (200, 832,585 B, read 2026-11-21)
1,000-entry bridge FDB MAC Address Table Size = 1,000, VLAN/Subnet-based Traffic Segmentation = True, Port Layout 1 GbE RJ45 = 5 (2 PoE) (1G/100M/10M) - https://techspecs.ui.com/unifi/cloud-gateways/udr (200, 685,837 B)
802.1Q tagging VLAN 802.1Q in the Software block - https://dl.ui.com/ds/udr_ds.pdf (200, 771,202 B, 3 pp)
4 LAN + 1 WAN datasheet Networking interface LAN: (4) GbE RJ45 ports / WAN: (1) GbE RJ45 port; fingerprint diagram 01 02 03 04 __ 05, the same 4+1 pattern as UDM and UCG-Ultra

Measured before the change: hosts on eth0 and eth1 in 192.168.1.0/24 could not resolve each other's ARP, and switchport access vlan 10 answered cannot switch frames: it has no l2-forward capability. Now the four LAN sockets forward at layer 2, eth4 carries role: "wan" (the separated fifth socket, so ip nat outside can be cabled to the uplink), and no switchport still makes a LAN port routed.

speedCaps gained 10M on the five copper ports: the tech-spec Port Layout row prints the trio (1G/100M/10M) and the row stopped at 100M.

Gates: node scripts/syntax-check.js 509 files OK; node scripts/audit-port-types.js gated 0 contradictions; node test/ubiquiti-gateway-lan-bridges.test.js 75 passed 0 failed (new UDR row); node test/hardware-invariants.test.js 26 passed; node test/catalogue-hygiene.test.js 25 passed; node test/doc-catalog-counts.test.js 43 passed.

Research: research/ubiquiti-fingerprint-switch-capability.md records the fingerprint instrument and the seven gateways whose vendor record says SWITCH while the spec still lacks l2-forward - the worklist for the next passes.

No engine change, no hand edit of docs/DEVICE_REGISTRY.md, no force-push.

Refs #130. This request stays open: the Dream Wall Pro has no vendor page, datasheet or storefront SKU, and nothing here invents one. What it does is take the nearest row in the family that *does* have a vendor record and fix a defect the Dream Wall Pro request would inherit if it ever lands - the LAN bank modelled as routed ports. **UDR (`devices/ubiquiti/udr.json`)** | claim | vendor surface | |---|---| | the console is a switch | `deviceCapabilities` for sku UDR include `GATEWAY`, **`SWITCH`**, `ACCESS_POINT`, `NETWORK_APPLICATION`, `PROTECT_APPLICATION`, `CONTROLLER`, `APPLICATION_MODE`, `HAS_CLIENTS` - https://static.ui.com/fingerprint/ui/public.json (200, 832,585 B, read 2026-11-21) | | 1,000-entry bridge FDB | `MAC Address Table Size = 1,000`, `VLAN/Subnet-based Traffic Segmentation = True`, `Port Layout 1 GbE RJ45 = 5 (2 PoE) (1G/100M/10M)` - https://techspecs.ui.com/unifi/cloud-gateways/udr (200, 685,837 B) | | 802.1Q tagging | `VLAN 802.1Q` in the Software block - https://dl.ui.com/ds/udr_ds.pdf (200, 771,202 B, 3 pp) | | 4 LAN + 1 WAN | datasheet `Networking interface LAN: (4) GbE RJ45 ports / WAN: (1) GbE RJ45 port`; fingerprint diagram `01 02 03 04 __ 05`, the same 4+1 pattern as UDM and UCG-Ultra | Measured before the change: hosts on `eth0` and `eth1` in 192.168.1.0/24 could not resolve each other's ARP, and `switchport access vlan 10` answered *cannot switch frames: it has no l2-forward capability*. Now the four LAN sockets forward at layer 2, `eth4` carries `role: "wan"` (the separated fifth socket, so `ip nat outside` can be cabled to the uplink), and `no switchport` still makes a LAN port routed. `speedCaps` gained `10M` on the five copper ports: the tech-spec Port Layout row prints the trio `(1G/100M/10M)` and the row stopped at 100M. **Gates**: `node scripts/syntax-check.js` 509 files OK; `node scripts/audit-port-types.js` gated 0 contradictions; `node test/ubiquiti-gateway-lan-bridges.test.js` 75 passed 0 failed (new UDR row); `node test/hardware-invariants.test.js` 26 passed; `node test/catalogue-hygiene.test.js` 25 passed; `node test/doc-catalog-counts.test.js` 43 passed. **Research**: `research/ubiquiti-fingerprint-switch-capability.md` records the fingerprint instrument and the seven gateways whose vendor record says `SWITCH` while the spec still lacks `l2-forward` - the worklist for the next passes. No engine change, no hand edit of `docs/DEVICE_REGISTRY.md`, no force-push.
devices(ubiquiti): the Dream Router's LAN bank is a bridge, and its fifth socket is the WAN (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 14s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 15s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Server smoke and Docker build (pull_request) Successful in 25s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 4s
e4d40a33ea
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 01:29:56 +00:00
jaylouisw deleted branch catalogue/1121-0122 2026-11-21 01:39:21 +00:00
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!2346
No description provided.