devices(ubiquiti): both Dream Routers get the controller's LAN/WAN split (refs #130) #2365
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2365
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1121-0422"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
roleon any of them.engine/device.jsseparates 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:ownsIpOn(eth3, '192.168.1.1')with the LAN address on eth0Sources, read 2026-11-21:
https://static.ui.com/fingerprint/ui/public.json(sku= UDR7 / UDR-5G-Max)ports={"eth0":"LAN","eth1":"LAN","eth2":"LAN","eth3":"WAN","eth4":"WAN2"};linkNegotiationputs 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 cagehttps://techspecs.ui.com/unifi/cloud-gateways/udr7Port 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 RJ45https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-maxWhat the rows now say: eth0-eth2
role: lan, eth3role: wan, sfp1role: 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.js514 files OK;audit-port-types.js0 gated defects (2,704 reported template ports, unchanged);audit-devices.js29,712 ports, 0 uncablable, 0 hard defects;hardware-invariants26/0;port-roles19/0;ubiquiti-wan-lan-role-separation153/0 (was 129);run-tests.js434 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), andtechspecs.ui.com/unifi/cloud-gateways/udw-pro307s to the 609,911-byte front page.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.