devices(ubiquiti): the UDR-5G-Max row had no cellular port, so the fallback router could not take a 5G WAN (#130) #2096
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!2096
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-0522"
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
The row this request's own thread offers as the nearest real alternative —
devices/ubiquiti/udr-5g-max.json— could not be cabled for the thing the request asks for. The stated build is "a router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN)"; the UDR-5G-Max is the only UniFi console in the catalogue that ships a 5G modem, and the row modelled five Ethernet ports and no modem at all.Vendor census, read 2026-11-19. Source:
https://techspecs.ui.com/unifi/cloud-gateways/udr-5g-max(200, 876,426 B) — the structured spec table inside__NEXT_DATA__, not the rendered spec images, so the figures are the vendor's text and not OCR.What changed
wwan0added, at the vendor's 3.4 Gbps 5G NSA downlink — the samewwan0conventionu5g-max,u5g,u5g-max-outdoor,u-lte-backup-proandumralready use. The engine now materialises it as a cellular cage at 3400 Mbps offeringlte/lte-a/5g-sub6media:Before this, the box had four RJ45s, one cage and no WAN of the kind the request names — an empty array where the vendor publishes a whole Cellular section.
poe.budgetW: 15.4added. The row sat inaudit-poe-budget.js's silent cohort (PoE out, no budget, no "never published" marker), soshow power inlinereported the port and refused the arithmetic. The cohort is now 112, from 113 — re-run to confirm.Description corrected: the vendor says WiFi 7, not "WiFi 6/7".
Deliberately not modelled: the WiFi 7 radios. No UniFi console row in this catalogue carries radios (
udw,udr,udr7,ux,ux7,udm-*), so adding them to this one row would make the console family read as if only this model had WiFi. Recorded in the spec'snotesrather than left silent.Gates
node scripts/syntax-check.js— 441 files, all OKnode scripts/audit-port-types.js— "No port contradicts its declared type."node test/hardware-invariants.test.js— 26 passed, 0 failed (the radio-rate rule accepts the new interface; wwan speedCaps derive from the cage)npm test— 362 suites, 12,384 assertions, 0 failednpm run regen:registry-doc—docs/CONNECTORS.md: 29,716 sockets, 972 distinct port shapes (generated, not hand-edited)This PR does not answer issue #130 — no Ubiquiti source for UDW-PRO has appeared, and the UDW-PRO surfaces were not re-walked (the sixteen previous comments record where each ends). It repairs the row the thread offers as the fallback, so that a lab can actually build the cellular-WAN router the request describes.