devices(ubiquiti): the Dream Wall's 2.5G port is the WAN uplink, not an eighteenth LAN port #2320
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2320
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1120-2152"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.jsonshipped eighteen interchangeable copper ports,eth0-eth17, with no WAN role anywhere on the box. A lab could not cableip nat outsideto 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):https://techspecs.ui.com/unifi/cloud-gateways/udw(200, 704,702 B, read 2026-11-20) adds the three rows that decide the encoding: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.poeOut, budget or rate is touched.research/ubiquiti-udw-pro-absent-from-vendor-catalogue.mdgains surface 15:ui.com/sitemap.xml(200, 7,794 B, 82<loc>, category pages only) and the schema.orgItemListonui.com/cloud-gateways(14 entries, position 13 = Dream Wall at/udw), zero entries naming a Pro.Gates