devices(ubiquiti): both Dream Routers get the controller's LAN/WAN split (refs #130) #2365

Merged
jaylouisw merged 1 commit from catalogue/1121-0422 into main 2026-11-21 04:38:51 +00:00
Owner

Refs #130 (no closing keyword: the Dream Wall Pro is still absent from every Ubiquiti surface, so this is the fallback row work, not a close).

The two Dream Routers shipped four 2.5G RJ45 sockets and one 10G SFP+ cage with no role on any of them. engine/device.js separates the L3 surfaces only when both sides carry one (owner.role && inIface.role && owner.role !== inIface.role), so the invariant was a no-op on both rows:

probe UDR7 before after UDR-5G-Max before after
ownsIpOn(eth3, '192.168.1.1') with the LAN address on eth0 true false true false
host on eth3 inside 192.168.1.0/24 pings the LAN gateway answered no reply answered no reply

Sources, read 2026-11-21:

surface bytes text
https://static.ui.com/fingerprint/ui/public.json (sku = UDR7 / UDR-5G-Max) 832,585 ports = {"eth0":"LAN","eth1":"LAN","eth2":"LAN","eth3":"WAN","eth4":"WAN2"}; linkNegotiation puts eth2 at portIdx 3 and eth3 at portIdx 4 at 2500/1000/100/10 FDX, eth4 at portIdx 5 at 10000/1000 FDX only - the cage
https://techspecs.ui.com/unifi/cloud-gateways/udr7 694,590 Port Layout = 2.5 GbE RJ45 4 (1 PoE) / 10G SFP+ 1, Max. WAN Port Count = 4, Default WAN Ports (1) 10G SFP+ / (1) 2.5 GbE RJ45
https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-max 876,426 same four rows, 2.5G set printed as 2.5G/1G/100M

What the rows now say: eth0-eth2 role: lan, eth3 role: wan, sfp1 role: wan (the controller's eth4, i.e. the default 10G SFP+ second WAN). The defaults are the vendor's; re-assigning a socket is a configuration change and is not modelled. Nothing else moved: census, speeds, the PoE port on eth0, the radios and the Wi-Fi rows are untouched.

Gates: syntax-check.js 514 files OK; audit-port-types.js 0 gated defects (2,704 reported template ports, unchanged); audit-devices.js 29,712 ports, 0 uncablable, 0 hard defects; hardware-invariants 26/0; port-roles 19/0; ubiquiti-wan-lan-role-separation 153/0 (was 129); run-tests.js 434 suites / 14,582 assertions, 0 failed. regen-registry-doc.js: catalogue pages already current (2,351 models / 258 vendors / 29,712 sockets), no doc change.

Still blocked on the request itself, unchanged: no Ubiquiti surface names UDW-PRO - not the storefront (both slugs 404), not the gateway index, not the 701-device fingerprint register (UDW only), and techspecs.ui.com/unifi/cloud-gateways/udw-pro 307s to the 609,911-byte front page.

Refs #130 (no closing keyword: the Dream Wall Pro is still absent from every Ubiquiti surface, so this is the fallback row work, not a close). The two Dream Routers shipped four 2.5G RJ45 sockets and one 10G SFP+ cage with no `role` on any of them. `engine/device.js` separates the L3 surfaces only when both sides carry one (`owner.role && inIface.role && owner.role !== inIface.role`), so the invariant was a no-op on both rows: | probe | UDR7 before | after | UDR-5G-Max before | after | |---|---|---|---|---| | `ownsIpOn(eth3, '192.168.1.1')` with the LAN address on eth0 | **true** | false | **true** | false | | host on eth3 inside 192.168.1.0/24 pings the LAN gateway | **answered** | no reply | **answered** | no reply | Sources, read 2026-11-21: | surface | bytes | text | |---|---|---| | `https://static.ui.com/fingerprint/ui/public.json` (`sku` = UDR7 / UDR-5G-Max) | 832,585 | `ports` = `{"eth0":"LAN","eth1":"LAN","eth2":"LAN","eth3":"WAN","eth4":"WAN2"}`; `linkNegotiation` puts eth2 at portIdx 3 and eth3 at portIdx 4 at 2500/1000/100/10 FDX, eth4 at portIdx 5 at 10000/1000 FDX only - the cage | | `https://techspecs.ui.com/unifi/cloud-gateways/udr7` | 694,590 | `Port Layout = 2.5 GbE RJ45 4 (1 PoE) / 10G SFP+ 1`, `Max. WAN Port Count = 4`, `Default WAN Ports (1) 10G SFP+ / (1) 2.5 GbE RJ45` | | `https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-max` | 876,426 | same four rows, 2.5G set printed as 2.5G/1G/100M | What the rows now say: eth0-eth2 `role: lan`, eth3 `role: wan`, sfp1 `role: wan` (the controller's eth4, i.e. the default 10G SFP+ second WAN). The defaults are the vendor's; re-assigning a socket is a configuration change and is not modelled. Nothing else moved: census, speeds, the PoE port on eth0, the radios and the Wi-Fi rows are untouched. Gates: `syntax-check.js` 514 files OK; `audit-port-types.js` 0 gated defects (2,704 reported template ports, unchanged); `audit-devices.js` 29,712 ports, 0 uncablable, 0 hard defects; `hardware-invariants` 26/0; `port-roles` 19/0; `ubiquiti-wan-lan-role-separation` 153/0 (was 129); `run-tests.js` 434 suites / 14,582 assertions, 0 failed. `regen-registry-doc.js`: catalogue pages already current (2,351 models / 258 vendors / 29,712 sockets), no doc change. Still blocked on the request itself, unchanged: no Ubiquiti surface names `UDW-PRO` - not the storefront (both slugs 404), not the gateway index, not the 701-device fingerprint register (UDW only), and `techspecs.ui.com/unifi/cloud-gateways/udw-pro` 307s to the 609,911-byte front page.
devices(ubiquiti): both Dream Routers get the controller's LAN/WAN split (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 16s
CI / Server smoke and Docker build (pull_request) Successful in 27s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Test (Node 22) (pull_request) Successful in 1m6s
CI / Test (Node 20) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 5s
e9aaa47256
UDR7 and UDR-5G-Max shipped four 2.5G RJ45 sockets and one 10G SFP+
cage with no `role` on any of them, so ownsIpOn()'s separation
(`owner.role && inIface.role && owner.role !== inIface.role`) never
fired: with 192.168.1.1/24 on eth0, `ownsIpOn(eth3, '192.168.1.1')`
returned true on both rows.

Ubiquiti's controller database names the sockets - `ports` =
{"eth0":"LAN","eth1":"LAN","eth2":"LAN","eth3":"WAN","eth4":"WAN2"}
- and its linkNegotiation block is positional (eth2/eth3 at 2.5G,
eth4 at 10G/1G only, so eth4 is the cage). The tech-spec table prints
"2.5 GbE RJ45 4 (1 PoE) / 10G SFP+ 1" and "Default WAN Ports (1) 10G
SFP+ / (1) 2.5 GbE RJ45". eth0-eth2 = lan, eth3 = wan, sfp1 = wan.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 04:33:44 +00:00
jaylouisw deleted branch catalogue/1121-0422 2026-11-21 04:38:54 +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!2365
No description provided.