devices(ubiquiti): the Dream Machine LAN banks carry a LAN role, so the uplink stops answering the LAN address (#130 fallback) #2359

Merged
jaylouisw merged 1 commit from catalogue/1121-0322 into main 2026-11-21 03:37:53 +00:00
Owner

Refs #130 only - no closing keyword. The Dream Wall Pro is still unmodelled; this is the next row in the fallback worklist.

The three Dream Machine chassis rows (UDM-Pro, UDM-Pro-Max, UDM-SE) shipped their eight 1G LAN sockets and their 2.5G/1G uplink with no role, so ownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role) was a no-op. With 192.168.1.1/24 on Port 1 / port1, ownsIpOn(<uplink>, '192.168.1.1') returned the LAN interface on all three rows: a host cabled to the uplink inside 192.168.1.0/24 was answered by the LAN gateway, i.e. the LAN address was served on the WAN socket.

row lan wan ownsIpOn(wan, LAN IP) before after
UDM-Pro port1..port8 wan1 truthy (port1) false
UDM-Pro-Max Port 1..Port 8 WAN truthy (Port 1) false
UDM-SE Port 1..Port 8 WAN truthy (Port 1) false

After: the uplink no longer owns the LAN address, Port 2/port2 still reaches the address held on Port 1/port1 (the bank still answers bank-wide), and the uplink still answers its own address.

Sources (all read 2026-11-21, bytes as returned):

  1. https://static.ui.com/fingerprint/ui/public.json - HTTP 200, 832,585 B. Per-SKU ports map, identical on all three: eth0-eth7 LAN, eth8 WAN, eth9 WAN2, eth10 LAN, standard 9, numberOfPorts 11 - nine RJ45 sockets, the ninth the uplink, then two 10G cages.
  2. https://techspecs.ui.com/unifi/cloud-gateways/udm-pro - HTTP 200, 676,527 B: Default WAN Ports (1) 10G SFP+ / (1) GbE RJ45, 1 GbE RJ45 = 9 (1G/100M/10M), 10G SFP+ = 2 (10G/1G), MAC Address Table Size = 4,000.
  3. https://techspecs.ui.com/unifi/cloud-gateways/udm-pro-max - HTTP 200, 677,375 B: Default WAN Ports (1) 10G SFP+ / (1) 2.5 GbE RJ45, 1 GbE RJ45 = 8, 2.5 GbE RJ45 = 1, MAC Address Table Size = 4,000.
  4. https://techspecs.ui.com/unifi/cloud-gateways/udm-se - HTTP 200, 682,320 B: same four rows.
  5. https://dl.ui.com/ds/udm-pro.pdf (already cited by the row, 353,553 B): SFP+ interface (1) LAN: 10G SFP+ / (1) WAN: 10G SFP+ - unnumbered, which is why the two cages keep no role (same restraint udw.json records). dl.ui.com/ds/udm-pro_ds.pdf still answers 302 to the 609,911-byte techspecs front page.

Test: test/ubiquiti-wan-lan-role-separation.test.js gains the three rows plus an assertion that the two cages on each keep no role/dualRole. 117 passed, 0 failed.

Gates: node scripts/syntax-check.js 512 files OK; node scripts/audit-port-types.js 0 gated; node scripts/audit-devices.js 0 hard defects (29,712 ports); node test/import-devices-capabilities.test.js 34 passed; node test/hardware-invariants.test.js 26 passed; node scripts/regen-registry-doc.js no doc change; node scripts/run-tests.js 432 suites, 14,506 assertions, 0 failed.

Refs #130 only - no closing keyword. The Dream Wall Pro is still unmodelled; this is the next row in the fallback worklist. The three Dream Machine chassis rows (`UDM-Pro`, `UDM-Pro-Max`, `UDM-SE`) shipped their eight 1G LAN sockets and their 2.5G/1G uplink with no `role`, so `ownsIpOn`'s separation (`owner.role && inIface.role && owner.role !== inIface.role`) was a no-op. With `192.168.1.1/24` on `Port 1` / `port1`, `ownsIpOn(<uplink>, '192.168.1.1')` returned the LAN interface on all three rows: a host cabled to the uplink inside `192.168.1.0/24` was answered by the LAN gateway, i.e. the LAN address was served on the WAN socket. | row | lan | wan | ownsIpOn(wan, LAN IP) before | after | |---|---|---|---|---| | UDM-Pro | port1..port8 | wan1 | truthy (`port1`) | false | | UDM-Pro-Max | Port 1..Port 8 | WAN | truthy (`Port 1`) | false | | UDM-SE | Port 1..Port 8 | WAN | truthy (`Port 1`) | false | After: the uplink no longer owns the LAN address, `Port 2`/`port2` still reaches the address held on `Port 1`/`port1` (the bank still answers bank-wide), and the uplink still answers its own address. Sources (all read 2026-11-21, bytes as returned): 1. `https://static.ui.com/fingerprint/ui/public.json` - HTTP 200, 832,585 B. Per-SKU `ports` map, identical on all three: `eth0`-`eth7` LAN, `eth8` WAN, `eth9` WAN2, `eth10` LAN, `standard` 9, `numberOfPorts` 11 - nine RJ45 sockets, the ninth the uplink, then two 10G cages. 2. `https://techspecs.ui.com/unifi/cloud-gateways/udm-pro` - HTTP 200, 676,527 B: `Default WAN Ports (1) 10G SFP+ / (1) GbE RJ45`, `1 GbE RJ45 = 9 (1G/100M/10M)`, `10G SFP+ = 2 (10G/1G)`, `MAC Address Table Size = 4,000`. 3. `https://techspecs.ui.com/unifi/cloud-gateways/udm-pro-max` - HTTP 200, 677,375 B: `Default WAN Ports (1) 10G SFP+ / (1) 2.5 GbE RJ45`, `1 GbE RJ45 = 8`, `2.5 GbE RJ45 = 1`, `MAC Address Table Size = 4,000`. 4. `https://techspecs.ui.com/unifi/cloud-gateways/udm-se` - HTTP 200, 682,320 B: same four rows. 5. `https://dl.ui.com/ds/udm-pro.pdf` (already cited by the row, 353,553 B): `SFP+ interface (1) LAN: 10G SFP+ / (1) WAN: 10G SFP+` - unnumbered, which is why the two cages keep no `role` (same restraint `udw.json` records). `dl.ui.com/ds/udm-pro_ds.pdf` still answers 302 to the 609,911-byte techspecs front page. Test: `test/ubiquiti-wan-lan-role-separation.test.js` gains the three rows plus an assertion that the two cages on each keep no role/dualRole. 117 passed, 0 failed. Gates: `node scripts/syntax-check.js` 512 files OK; `node scripts/audit-port-types.js` 0 gated; `node scripts/audit-devices.js` 0 hard defects (29,712 ports); `node test/import-devices-capabilities.test.js` 34 passed; `node test/hardware-invariants.test.js` 26 passed; `node scripts/regen-registry-doc.js` no doc change; `node scripts/run-tests.js` 432 suites, 14,506 assertions, 0 failed.
devices(ubiquiti): the Dream Machine LAN banks carry a LAN role, so the uplink stops answering the LAN address (#130 fallback)
All checks were successful
CI / Classify the change (pull_request) Successful in 36s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 22s
CI / Test (Node 22) (pull_request) Successful in 1m5s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Test (Node 20) (pull_request) Successful in 1m8s
CI / Server smoke and Docker build (pull_request) Successful in 19s
CI / Arm auto-merge (pull_request) Successful in 4s
cd2ab6e901
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 03:31:20 +00:00
jaylouisw deleted branch catalogue/1121-0322 2026-11-21 03:37:56 +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!2359
No description provided.