devices(ubiquiti): the Dream Wall's 2.5G port is the WAN uplink, not an eighteenth LAN port #2320

Merged
jaylouisw merged 1 commit from catalogue/1120-2152 into main 2026-11-20 22:08:15 +00:00
Owner

Refs #130 only - no closing keyword anywhere in this body. No UDW-PRO spec is added; the Pro request stays blocked exactly as its thread records, and this PR deliberately does not settle it.

What was wrong

devices/ubiquiti/udw.json shipped eighteen interchangeable copper ports, eth0-eth17, with no WAN role anywhere on the box. A lab could not cable ip nat outside to the uplink Ubiquiti designates, and the 2.5G port was indistinguishable from the seventeen 1G LAN ports.

What the vendor says

https://dl.ui.com/ds/udw_ds.pdf (200, application/pdf, 544,909 B, 3 pp, text layer, read 2026-11-20):

Networking interface  (17) LAN: GbE RJ45 ports
                      (1) WAN: 2.5 GbE RJ45 port
SFP+ interface        (1) LAN: 10G SFP+ port
                      (1) WAN: 10G SFP+ port

https://techspecs.ui.com/unifi/cloud-gateways/udw (200, 704,702 B, read 2026-11-20) adds the three rows that decide the encoding:

row value
Max. WAN Port Count 8
Default WAN Ports (1) 2.5 GbE RJ45 / (1) 10G SFP+
Port Layout - 2.5 GbE RJ45 1 (2.5G/1G/100M)

Change

  • eth17 -> wan1, role: "wan", dualRole: ["wan","lan"].
  • sfp1 / sfp2 -> dualRole: ["wan","lan"], no fixed role: the datasheet prints one LAN and one WAN cage without numbering them, so naming which cage is which would be a guess; and the vendor's own 8-WAN ceiling makes port role configuration, not wiring.
  • Description now names the WAN side and the 532 W power ceiling (112 W excluding PoE + 420 W budget). The seventeen 1G LAN ports keep their names and PoE classes; no poeOut, budget or rate is touched.
  • research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md gains surface 15: ui.com/sitemap.xml (200, 7,794 B, 82 <loc>, category pages only) and the schema.org ItemList on ui.com/cloud-gateways (14 entries, position 13 = Dream Wall at /udw), zero entries naming a Pro.

Gates

node scripts/syntax-check.js      -> Syntax-checked 499 files: all OK
node scripts/audit-port-types.js  -> Gated: 0 port(s) contradict their declared type
node scripts/regen-registry-doc.js-> catalogue pages current (2,351 models, 258 vendors)
node --test test/hardware-invariants.test.js -> 26 passed, 0 failed
node --test test/catalogue-hygiene.test.js test/device-aliases.test.js test/faceplate-catalogue.test.js -> 3 passed
Refs #130 only - no closing keyword anywhere in this body. No UDW-PRO spec is added; the Pro request stays blocked exactly as its thread records, and this PR deliberately does not settle it. ## What was wrong `devices/ubiquiti/udw.json` shipped eighteen interchangeable copper ports, `eth0`-`eth17`, with **no WAN role anywhere on the box**. A lab could not cable `ip nat outside` to the uplink Ubiquiti designates, and the 2.5G port was indistinguishable from the seventeen 1G LAN ports. ## What the vendor says `https://dl.ui.com/ds/udw_ds.pdf` (200, `application/pdf`, 544,909 B, 3 pp, text layer, read 2026-11-20): ``` Networking interface (17) LAN: GbE RJ45 ports (1) WAN: 2.5 GbE RJ45 port SFP+ interface (1) LAN: 10G SFP+ port (1) WAN: 10G SFP+ port ``` `https://techspecs.ui.com/unifi/cloud-gateways/udw` (200, 704,702 B, read 2026-11-20) adds the three rows that decide the encoding: | row | value | |---|---| | Max. WAN Port Count | 8 | | Default WAN Ports | (1) 2.5 GbE RJ45 / (1) 10G SFP+ | | Port Layout - 2.5 GbE RJ45 | 1 (2.5G/1G/100M) | ## Change - `eth17` -> `wan1`, `role: "wan"`, `dualRole: ["wan","lan"]`. - `sfp1` / `sfp2` -> `dualRole: ["wan","lan"]`, no fixed role: the datasheet prints one LAN and one WAN cage **without numbering them**, so naming which cage is which would be a guess; and the vendor's own 8-WAN ceiling makes port role configuration, not wiring. - Description now names the WAN side and the 532 W power ceiling (112 W excluding PoE + 420 W budget). The seventeen 1G LAN ports keep their names and PoE classes; no `poeOut`, budget or rate is touched. - `research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md` gains surface 15: `ui.com/sitemap.xml` (200, 7,794 B, 82 `<loc>`, category pages only) and the schema.org `ItemList` on `ui.com/cloud-gateways` (14 entries, position 13 = Dream Wall at `/udw`), zero entries naming a Pro. ## Gates ``` node scripts/syntax-check.js -> Syntax-checked 499 files: all OK node scripts/audit-port-types.js -> Gated: 0 port(s) contradict their declared type node scripts/regen-registry-doc.js-> catalogue pages current (2,351 models, 258 vendors) node --test test/hardware-invariants.test.js -> 26 passed, 0 failed node --test test/catalogue-hygiene.test.js test/device-aliases.test.js test/faceplate-catalogue.test.js -> 3 passed ```
devices(ubiquiti): the Dream Wall's 2.5G port is the WAN uplink, not an eighteenth LAN port (#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 57s
CI / Server smoke and Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 59s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 5s
21df2ae25c
devices/ubiquiti/udw.json shipped eighteen interchangeable copper ports,
eth0-eth17, with no WAN role anywhere on the box. Ubiquiti's own datasheet
says otherwise: '(17) LAN: GbE RJ45 ports / (1) WAN: 2.5 GbE RJ45 port' and
'SFP+ interface (1) LAN: 10G SFP+ / (1) WAN: 10G SFP+'. The tech-spec table
adds 'Max. WAN Port Count 8' and 'Default WAN Ports (1) 2.5 GbE RJ45 /
(1) 10G SFP+', and gives the 2.5G port's rate set as 2.5G/1G/100M.

eth17 -> wan1, role 'wan'; both cages carry dualRole ['wan','lan'] because
the datasheet prints one LAN and one WAN cage without numbering them and
because the vendor's 8-WAN ceiling makes role configuration, not wiring.
The seventeen 1G LAN ports keep their names and PoE classes.

Also records surface 15 for the Pro request in the research note: ui.com's
own sitemap and its schema.org ItemList of 14 gateways, no Pro member.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 21:56:46 +00:00
jaylouisw deleted branch catalogue/1120-2152 2026-11-20 22:08:17 +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!2320
No description provided.