devices(ubiquiti): seven Dream/Gateway rows bridge their LAN banks (#130 fallback) #2349

Merged
jaylouisw merged 1 commit from catalogue/1121-0152 into main 2026-11-21 02:10:57 +00:00
Owner

Refs #130 only - the Dream Wall Pro is still absent from every Ubiquiti surface, as this thread's last ten passes record, and nothing here touches it.

This finishes the worklist research/ubiquiti-fingerprint-switch-capability.md left open: the seven UniFi gateway rows that Ubiquiti's own device database classifies as SWITCH but whose specs still had no l2-forward. Each row's count was read off its own vendor page before the change (all 200 to a bot UA on 2026-11-21; an unknown slug 307s to the 609,911 B techspecs front page, so the byte count is the control).

SKU MAC Address Table Size LACP VLAN segmentation page bytes
UDM no table on page; datasheet prints VLAN 802.1Q - - 608,032
UDR7 2,000 absent ticked 694,590
UDR-5G-Max 2,000 absent absent 876,426
UXG-Fiber 4,000 absent absent 649,433
UCG-Industrial 4,000 absent ticked 699,443
UDM-Beast 32,000 ticked absent 679,909
EF-Core 130,000 ticked absent 674,322

A MAC table is a bridge FDB. Before the change, two hosts in 192.168.1.0/24 on adjacent LAN ports could not resolve each other's ARP and switchport access vlan 10 answered "cannot switch frames: it has no l2-forward capability".

Census, PoE and WAN sides are unchanged. No copper socket is renamed WAN: UDR7 / UDR-5G-Max print Default WAN Ports = (1) 10G SFP+ / (1) 2.5 GbE RJ45 over an unbroken five-socket diagram and UCG-Industrial three defaults over six, so picking one would be a guess.

Gates: syntax-check 510 files OK; audit-port-types 0 gated; audit-devices 0 hard defects; hardware-invariants 26/0; run-tests 430 suites / 14,367 assertions, 0 failed. New rows in test/ubiquiti-gateway-lan-bridges.test.js (140 assertions).

Refs #130 only - the Dream Wall Pro is still absent from every Ubiquiti surface, as this thread's last ten passes record, and nothing here touches it. This finishes the worklist `research/ubiquiti-fingerprint-switch-capability.md` left open: the seven UniFi gateway rows that Ubiquiti's own device database classifies as `SWITCH` but whose specs still had no `l2-forward`. Each row's count was read off its own vendor page before the change (all 200 to a bot UA on 2026-11-21; an unknown slug 307s to the 609,911 B techspecs front page, so the byte count is the control). | SKU | MAC Address Table Size | LACP | VLAN segmentation | page bytes | |---|---|---|---|---| | UDM | no table on page; datasheet prints VLAN 802.1Q | - | - | 608,032 | | UDR7 | 2,000 | absent | ticked | 694,590 | | UDR-5G-Max | 2,000 | absent | absent | 876,426 | | UXG-Fiber | 4,000 | absent | absent | 649,433 | | UCG-Industrial | 4,000 | absent | ticked | 699,443 | | UDM-Beast | 32,000 | ticked | absent | 679,909 | | EF-Core | 130,000 | ticked | absent | 674,322 | A MAC table is a bridge FDB. Before the change, two hosts in 192.168.1.0/24 on adjacent LAN ports could not resolve each other's ARP and `switchport access vlan 10` answered "cannot switch frames: it has no l2-forward capability". Census, PoE and WAN sides are unchanged. No copper socket is renamed WAN: UDR7 / UDR-5G-Max print `Default WAN Ports = (1) 10G SFP+ / (1) 2.5 GbE RJ45` over an unbroken five-socket diagram and UCG-Industrial three defaults over six, so picking one would be a guess. Gates: syntax-check 510 files OK; audit-port-types 0 gated; audit-devices 0 hard defects; hardware-invariants 26/0; run-tests 430 suites / 14,367 assertions, 0 failed. New rows in `test/ubiquiti-gateway-lan-bridges.test.js` (140 assertions).
devices(ubiquiti): seven Dream/Gateway rows bridge their LAN banks (#130 fallback)
All checks were successful
CI / Classify the change (pull_request) Successful in 12s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 18s
CI / Test (Node 20) (pull_request) Successful in 55s
CI / Server smoke and Docker build (pull_request) Successful in 25s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 5s
b2854dd5fa
Ubiquiti's controller device database (static.ui.com/fingerprint/ui/public.json, 832,585 B,
read 2026-11-21) classifies all seven as SWITCH, and each vendor tech-spec page prints a bridge
forwarding database - UDM-Beast 32,000 MAC entries with LACP ticked, EF-Core 130,000 with LACP,
UDR7 and UDR-5G-Max 2,000, UXG-Fiber and UCG-Industrial 4,000, UDM via its datasheet's VLAN 802.1Q
(its tech-spec URL carries no table).

While these rows shipped without l2-forward their copper sockets were routed interfaces:
`switchport access vlan 10` answered "cannot switch frames: it has no l2-forward capability" and
two hosts in 192.168.1.0/24 on adjacent LAN ports could not resolve each other's ARP.

Census, WAN sides and PoE are untouched; no socket is renamed WAN, because none of these pages
pins a copper port to WAN. Test rows added to test/ubiquiti-gateway-lan-bridges.test.js (140
assertions).

refs #130
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 02:01:47 +00:00
jaylouisw deleted branch catalogue/1121-0152 2026-11-21 02:10:59 +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!2349
No description provided.