devices(ubiquiti): the Fiber pair's copper bank served its LAN address on the uplink (#130) #2380
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!2380
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1121-0622"
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 itself is still absent from every Ubiquiti surface; this is the adjacent increment from the same thread).
What changed
UCG-FiberandUXG-Fibershipped their entire copper bank with norole, soownsIpOn's separation (owner.role && inIface.role && owner.role !== inIface.role, engine/device.js) never fired. Measured on the pre-change specs: with192.168.1.1/24on the first LAN port,ownsIpOn(WAN, '192.168.1.1')returned true on UCG-Fiber andownsIpOn(eth4, '192.168.1.1')returned true on UXG-Fiber — a host cabled to the 10G RJ45 uplink inside the LAN prefix was answered by the LAN gateway.Both rows now carry the vendor's split:
devices/ubiquiti/ucg-fiber.jsonPort 1-Port 4->role: lanWAN->role: wanportsmap + tech-specdevices/ubiquiti/uxg-fiber.jsoneth0-eth3->role: laneth4->role: wanportsmap (names already match) + tech-specEvidence (read 2026-11-21)
https://static.ui.com/fingerprint/ui/public.json— HTTP 200, 832,585 B,sku= UCG-Fiber / UXG-Fiber, both publishnumberOfPorts7 andports={eth0: LAN, eth1: LAN, eth2: LAN, eth3: LAN, eth4: WAN, eth5: LAN, eth6: WAN2};linkNegotiationputs eth0-eth3 at portIdx 1-4 (2500/1000/100/10 FDX), eth4 at portIdx 5 (10000/5000/2500/1000/100/10 FDX) and the two cages at portIdx 6-7 (10000/1000 FDX only).https://techspecs.ui.com/unifi/cloud-gateways/ucg-fiber— HTTP 200, 667,242 B:Port Layout 2.5 GbE RJ45 4 / 10 GbE RJ45 1 / 10G SFP+ 2,Default WAN Ports (1) 10G SFP+ (1) 10 GbE RJ45,Max. WAN Port Count 6.https://techspecs.ui.com/unifi/cloud-gateways/uxg-fiber— HTTP 200, 649,433 B: same rows.What is deliberately not modelled
The two SFP+ cages on each row stay role-less. The controller does number them (eth5 LAN, eth6 WAN2), but neither row's cage names (
SFP+ 1/SFP+ 2,SFP+-1/SFP+-2) are vendor-issued — both pages print one undifferentiated10G SFP+ 2row — so assigning a role would be an ordering guess that moves a lab's saved uplink.Max WAN Port Count 6stays unmodelled for the same reason. Both notes record this.Gates
node scripts/syntax-check.js-> 516 files, all OKnode scripts/audit-port-types.js-> gated 0 contradictionsnode scripts/audit-devices.js-> 2,352 models / 29,768 sockets, 0 uncablable, 0 hard defectsnode scripts/check-control-bytes.js-> cleannode scripts/run-tests.js-> 436 suites, 14,678 assertions, 0 failed (includes the 14 new assertions intest/ubiquiti-wan-lan-role-separation.test.js)node scripts/regen-registry-doc.js-> catalogue pages already current