devices(ubiquiti): three gateways' LAN banks are bridges, not routed ports #2334

Merged
jaylouisw merged 1 commit from catalogue/1120-2352 into main 2026-11-21 00:08:27 +00:00
Owner

Refs #130. This does not close it: the Dream Wall Pro is still unpublished by its vendor, and nothing here touches that census.

Three more UniFi gateways shipped their LAN sockets as routed interfaces while Ubiquiti publishes a bridge FDB for each of them. Measured today, same UA, server-rendered pages:

model vendor row tech-specs page storefront payload
UDM-Pro-Max MAC Address Table Size = 4,000; LACP Port Aggregation (storefront note: "GbE RJ45 ports 1-8"); Port Layout 1 GbE RJ45 = 8 200, 677,375 B 200, 598,660 B
UCG-Max MAC Address Table Size = 2,000; Port Layout 2.5 GbE RJ45 = 5 200, 668,564 B 200, 646,522 B (/us/en/products/ucg-max 307s here)
UXG-Max MAC Address Table Size = 2,000; VLAN and LACP rows flagged Empty 200, 647,803 B 200, 525,294 B

A MAC table is the bridge's forwarding database and a LAG over ports 1-8 cannot be built from routed ports, so these banks forward at layer 2. The token is claimed for exactly that - l2-forward is MAC learning + flooding in engine/device.js; Ubiquiti's VLAN/LACP rows are quoted as they stand, Empty where Empty. UDM is deliberately untouched: its tech-spec page carries no Networking rows at all (0 occurrences of "MAC Address Table"), and its datasheet's only VLAN 802.1Q line is the wireless row.

Before (UDM-Pro-Max, two hosts on Port 1 / Port 2 in 192.168.1.0/24):

ARP: false
% UniFi Dream Machine Pro Max-gw cannot switch frames: it has no l2-forward capability - this port routes

test/ubiquiti-gateway-lan-bridges.test.js (28 assertions) pins the ARP path across the bank, the gateway address answering from a sibling port, switchport access vlan, channel-group on the Pro Max, no switchport still routing a port, and the WAN port still taking an address.

Gates: syntax-check.js 505 files OK; audit-port-types.js 0 contradicting ports; audit-devices.js 0 uncablable ethernet ports; check-control-bytes.js clean; hardware-invariants 26/26; catalogue-hygiene 25/25; capability-vocabulary 13/13; lldp 27/27; l2 28/28; poe 21/21; regen-registry-doc.js reports the catalogue pages current.

Refs #130. This does not close it: the Dream Wall Pro is still unpublished by its vendor, and nothing here touches that census. Three more UniFi gateways shipped their LAN sockets as routed interfaces while Ubiquiti publishes a bridge FDB for each of them. Measured today, same UA, server-rendered pages: | model | vendor row | tech-specs page | storefront payload | |---|---|---|---| | UDM-Pro-Max | `MAC Address Table Size = 4,000`; `LACP Port Aggregation` (storefront note: "GbE RJ45 ports 1-8"); `Port Layout 1 GbE RJ45 = 8` | 200, 677,375 B | 200, 598,660 B | | UCG-Max | `MAC Address Table Size = 2,000`; `Port Layout 2.5 GbE RJ45 = 5` | 200, 668,564 B | 200, 646,522 B (`/us/en/products/ucg-max` 307s here) | | UXG-Max | `MAC Address Table Size = 2,000`; VLAN and LACP rows flagged **Empty** | 200, 647,803 B | 200, 525,294 B | A MAC table is the bridge's forwarding database and a LAG over ports 1-8 cannot be built from routed ports, so these banks forward at layer 2. The token is claimed for exactly that - `l2-forward` is MAC learning + flooding in `engine/device.js`; Ubiquiti's VLAN/LACP rows are quoted as they stand, Empty where Empty. `UDM` is deliberately untouched: its tech-spec page carries no Networking rows at all (0 occurrences of "MAC Address Table"), and its datasheet's only `VLAN 802.1Q` line is the wireless row. Before (UDM-Pro-Max, two hosts on Port 1 / Port 2 in 192.168.1.0/24): ``` ARP: false % UniFi Dream Machine Pro Max-gw cannot switch frames: it has no l2-forward capability - this port routes ``` `test/ubiquiti-gateway-lan-bridges.test.js` (28 assertions) pins the ARP path across the bank, the gateway address answering from a sibling port, `switchport access vlan`, `channel-group` on the Pro Max, `no switchport` still routing a port, and the WAN port still taking an address. Gates: `syntax-check.js` 505 files OK; `audit-port-types.js` 0 contradicting ports; `audit-devices.js` 0 uncablable ethernet ports; `check-control-bytes.js` clean; `hardware-invariants` 26/26; `catalogue-hygiene` 25/25; `capability-vocabulary` 13/13; `lldp` 27/27; `l2` 28/28; `poe` 21/21; `regen-registry-doc.js` reports the catalogue pages current.
devices(ubiquiti): three gateways' LAN banks are bridges, not routed ports (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Test (Node 20) (pull_request) Successful in 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m3s
CI / Server smoke and Docker build (pull_request) Successful in 28s
CI / Arm auto-merge (pull_request) Successful in 4s
6cdc27fd36
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 23:58:10 +00:00
jaylouisw deleted branch catalogue/1120-2352 2026-11-21 00:08:32 +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!2334
No description provided.