devices(ubiquiti): four gateway LAN banks are bridges, not routed ports (refs #130) #2338

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

Refs #130 — does not close it. Ubiquiti publishes no Dream Wall Pro (this thread's sixteen surfaces), so the request stays blocked; this pass swept the defect class the last one fixed in three siblings onto the four gateway rows it left behind.

What was wrong. devices/ubiquiti/UDM-Pro.json, udm-se.json, UCG-Ultra.json and ucg-fiber.json modelled their LAN banks as routed interfaces with no l2-forward. Measured on the pre-change specs (two hosts in 192.168.1.0/24 on two adjacent LAN ports):

model ARP between LAN ports switchport access vlan 10
UDM-Pro no % ... cannot switch frames: it has no l2-forward capability
UDM-SE no same
UCG-Ultra no same
UCG-Fiber no same

What the vendor prints (both surfaces read 2026-11-21, byte counts as returned):

model MAC Address Table Size LACP Port Aggregation VLAN/Subnet segmentation techspecs storefront
UDM-Pro 4,000 True, note "GbE RJ45 ports 1-8" True 200 / 676,527 B 200 / 600,722 B
UDM-SE 4,000 True, note "GbE RJ45 ports 1-8" True 200 / 682,320 B 200 / 602,395 B
UCG-Ultra 2,000 Empty True 200 / 657,109 B 200 / 550,987 B
UCG-Fiber 4,000 Empty True 200 / 667,242 B 200 / 595,995 B (via 307 from /products/ucg-fiber)

A MAC table is a bridge FDB and a LAG over eight 1G sockets cannot be built from routed ports, so each LAN bank forward at layer 2 and the rows now declare l2-forward (MAC learning + flooding only). The two UCG rows do not claim bundle support: their LACP row is Empty on both surfaces.

What did not change: port census (9 / 9 / 5 / 5 copper + cages), WAN roles, PoE declarations, no switchport still routes a LAN port, and every WAN port still takes an address. UDM-Pro.json's note lost its stale "no 'l2-forward'" clause, which had copied the Dream Machine line's capability set before UDM-Pro-Max was read (fixed in PR #2334).

Tests. test/ubiquiti-gateway-lan-bridges.test.js now covers seven models (66 assertions, was 28): l2-forward declared, l3-forward+nat kept, vendor copper census, ARP across the bank, bank address answered off-port, VLAN accepted, LAG accepted only where the vendor states it, no switchport + address, WAN address.

Gates. syntax 506 OK; audit-port-types 0 contradictions; audit-devices 0 hard defects (2,351 models, 29,712 ports); hardware invariants 26/0; run-tests 426 suites / 14,192 assertions, 0 failed; control-bytes and doc-citations clean; registry doc current (2,351 models).

Blocker, unchanged. No Ubiquiti source names UDW-PRO — gateway index, storefront (control-slug tested), fingerprint register, FCC census, firmware platform codes. Unblock: any vendor artefact naming the SKU, or the requester confirming they meant the catalogued UDW or the UDM-Pro.

Refs #130 — does not close it. Ubiquiti publishes no Dream Wall Pro (this thread's sixteen surfaces), so the request stays blocked; this pass swept the defect class the last one fixed in three siblings onto the four gateway rows it left behind. **What was wrong.** `devices/ubiquiti/UDM-Pro.json`, `udm-se.json`, `UCG-Ultra.json` and `ucg-fiber.json` modelled their LAN banks as routed interfaces with no `l2-forward`. Measured on the pre-change specs (two hosts in 192.168.1.0/24 on two adjacent LAN ports): | model | ARP between LAN ports | `switchport access vlan 10` | |---|---|---| | UDM-Pro | no | `% ... cannot switch frames: it has no l2-forward capability` | | UDM-SE | no | same | | UCG-Ultra | no | same | | UCG-Fiber | no | same | **What the vendor prints** (both surfaces read 2026-11-21, byte counts as returned): | model | MAC Address Table Size | LACP Port Aggregation | VLAN/Subnet segmentation | techspecs | storefront | |---|---|---|---|---|---| | UDM-Pro | 4,000 | True, note "GbE RJ45 ports 1-8" | True | 200 / 676,527 B | 200 / 600,722 B | | UDM-SE | 4,000 | True, note "GbE RJ45 ports 1-8" | True | 200 / 682,320 B | 200 / 602,395 B | | UCG-Ultra | 2,000 | Empty | True | 200 / 657,109 B | 200 / 550,987 B | | UCG-Fiber | 4,000 | Empty | True | 200 / 667,242 B | 200 / 595,995 B (via 307 from `/products/ucg-fiber`) | A MAC table is a bridge FDB and a LAG over eight 1G sockets cannot be built from routed ports, so each LAN bank forward at layer 2 and the rows now declare `l2-forward` (MAC learning + flooding only). The two UCG rows do **not** claim bundle support: their LACP row is Empty on both surfaces. **What did not change:** port census (9 / 9 / 5 / 5 copper + cages), WAN roles, PoE declarations, `no switchport` still routes a LAN port, and every WAN port still takes an address. `UDM-Pro.json`'s note lost its stale "no 'l2-forward'" clause, which had copied the Dream Machine line's capability set before `UDM-Pro-Max` was read (fixed in PR #2334). **Tests.** `test/ubiquiti-gateway-lan-bridges.test.js` now covers seven models (66 assertions, was 28): l2-forward declared, l3-forward+nat kept, vendor copper census, ARP across the bank, bank address answered off-port, VLAN accepted, LAG accepted only where the vendor states it, `no switchport` + address, WAN address. **Gates.** syntax 506 OK; audit-port-types 0 contradictions; audit-devices 0 hard defects (2,351 models, 29,712 ports); hardware invariants 26/0; run-tests 426 suites / 14,192 assertions, 0 failed; control-bytes and doc-citations clean; registry doc current (2,351 models). **Blocker, unchanged.** No Ubiquiti source names `UDW-PRO` — gateway index, storefront (control-slug tested), fingerprint register, FCC census, firmware platform codes. Unblock: any vendor artefact naming the SKU, or the requester confirming they meant the catalogued UDW or the UDM-Pro.
devices(ubiquiti): four gateway LAN banks are bridges, not routed ports (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 55s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 29s
CI / Test (Node 22) (pull_request) Successful in 1m27s
CI / Test (Node 18) (pull_request) Successful in 1m37s
CI / Test (Node 20) (pull_request) Successful in 1m41s
CI / Server smoke and Docker build (pull_request) Successful in 27s
CI / Arm auto-merge (pull_request) Successful in 7s
a1be56b130
UDM-Pro, UDM-SE, UCG-Ultra and UCG-Fiber shipped their LAN banks as routed
interfaces with no l2-forward. Both Ubiquiti surfaces print a bridge FDB and a
VLAN row for each box (4,000 / 4,000 / 2,000 / 4,000 entries); UDM-Pro and
UDM-SE additionally print LACP over GbE RJ45 ports 1-8. Hosts on adjacent LAN
ports in one subnet could not resolve each other's ARP, and 'switchport access
vlan' was refused. l2-forward is now declared; census, WAN roles and 'no
switchport' behaviour are unchanged. test/ubiquiti-gateway-lan-bridges.test.js
extended to 7 models (66 assertions).
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 00:37:12 +00:00
jaylouisw deleted branch catalogue/1121-0022 2026-11-21 00:39:27 +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!2338
No description provided.