devices(ubiquiti): the UDR-5G-Max row had no cellular port, so the fallback router could not take a 5G WAN (#130) #2096

Merged
jaylouisw merged 1 commit from catalogue/1119-0522 into main 2026-11-19 05:38:09 +00:00
Owner

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.

field vendor value
2.5 GbE RJ45 4 (1 PoE) (2.5G/1G/100M)
10G SFP+ 1 (10G/1G)
Max WAN port count / default WAN 4 / (1) 10G SFP+ + (1) 2.5 GbE RJ45
PoE budget 15.4 W — the single PoE port is 802.3af, 15.4 W, 44–57 V
Max. power consumption 34.5 W excluding PoE output
Cellular 5G NR Sub-6; NSA 3.4 Gbps DL / 560 Mbps UL, SA 1.8 Gbps / 650 Mbps, LTE 1.6 Gbps / 210 Mbps; (2) nano-SIM + (1) nano-SIM or eSIM
WiFi 7 — 2.4 GHz 688 Mbps / 5 GHz 4.3 Gbps / 6 GHz 5.7 Gbps, not modelled (see below)

What changed

  1. wwan0 added, at the vendor's 3.4 Gbps 5G NSA downlink — the same wwan0 convention u5g-max, u5g, u5g-max-outdoor, u-lte-backup-pro and umr already use. The engine now materialises it as a cellular cage at 3400 Mbps offering lte / lte-a / 5g-sub6 media:
wwan0 | wireless | cage: wwan | speed: 3.4G | caps: [3400] | media: ["lte","lte-a","5g-sub6"]
poeBudget: 15.4

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.

  1. poe.budgetW: 15.4 added. The row sat in audit-poe-budget.js's silent cohort (PoE out, no budget, no "never published" marker), so show power inline reported the port and refused the arithmetic. The cohort is now 112, from 113 — re-run to confirm.

  2. 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's notes rather than left silent.

Gates

  • node scripts/syntax-check.js — 441 files, all OK
  • node 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 failed
  • npm 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.

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. | field | vendor value | |---|---| | 2.5 GbE RJ45 | 4 (1 PoE) (2.5G/1G/100M) | | 10G SFP+ | 1 (10G/1G) | | Max WAN port count / default WAN | 4 / (1) 10G SFP+ + (1) 2.5 GbE RJ45 | | PoE budget | 15.4 W — the single PoE port is 802.3af, 15.4 W, 44–57 V | | Max. power consumption | 34.5 W excluding PoE output | | Cellular | 5G NR Sub-6; NSA 3.4 Gbps DL / 560 Mbps UL, SA 1.8 Gbps / 650 Mbps, LTE 1.6 Gbps / 210 Mbps; (2) nano-SIM + (1) nano-SIM or eSIM | | WiFi | 7 — 2.4 GHz 688 Mbps / 5 GHz 4.3 Gbps / 6 GHz 5.7 Gbps, not modelled (see below) | **What changed** 1. `wwan0` added, at the vendor's 3.4 Gbps 5G NSA downlink — the same `wwan0` convention `u5g-max`, `u5g`, `u5g-max-outdoor`, `u-lte-backup-pro` and `umr` already use. The engine now materialises it as a cellular cage at 3400 Mbps offering `lte` / `lte-a` / `5g-sub6` media: ``` wwan0 | wireless | cage: wwan | speed: 3.4G | caps: [3400] | media: ["lte","lte-a","5g-sub6"] poeBudget: 15.4 ``` 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. 2. `poe.budgetW: 15.4` added. The row sat in `audit-poe-budget.js`'s **silent** cohort (PoE out, no budget, no "never published" marker), so `show power inline` reported the port and refused the arithmetic. The cohort is now **112, from 113** — re-run to confirm. 3. 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's `notes` rather than left silent. **Gates** - `node scripts/syntax-check.js` — 441 files, all OK - `node 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 failed - `npm 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.
devices(ubiquiti): the UDR-5G-Max row had no cellular port, so the fallback router could not take a 5G WAN (#130)
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 8s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 20) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 56s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 3s
82ead5e8cb
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 05:32:00 +00:00
jaylouisw deleted branch catalogue/1119-0522 2026-11-19 05:38:11 +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!2096
No description provided.