devices(ubiquiti): the mobile routers had no cellular port to route out of #2160

Merged
jaylouisw merged 1 commit from catalogue/1119-1352 into main 2026-11-19 14:11:10 +00:00
Owner

Refs #130

The lab in that request wants "a router/gateway node ... (NAT, DHCP, VPN, cellular WAN)". The
Mobile Router family is what a requester is handed for the cellular half of it, and two of its
three rows had no cellular port at all
.

devices/ubiquiti/umr.json and devices/ubiquiti/umr-ultra.json modelled rj45-1, rj45-2 and
radio-2g - two copper ports and the WiFi 4 radio - and no wwan port. umr-industrial.json,
the third member, has carried a wwan0 all along, so the family disagreed with itself about
whether an LTE radio is an interface.

The vendor names the radio in the first row of the table

surface (read 2026-11-19, crawler user-agent) bytes row
https://techspecs.ui.com/unifi/integrations/umr-us 708,698 "Networking Interface (2) GbE RJ45 ports, LTE Cat 4 radio, WiFi 4"; "LTE Throughput Speed Download 150 Mbps / Upload 50 Mbps"
https://dl.ui.com/ds/umr_ds.pdf 597,924, PDF, 2 pp p2: "LTE throughput speed* Download 150 Mbps / Upload 50 Mbps", "LTE Category 4 radio", WiFi 4 "6.5 Mbps to 150 Mbps"
https://techspecs.ui.com/unifi/integrations/umr-ultra-us 682,619 "(2) FE RJ45 ports, LTE Cat 4 radio, WiFi 4"; same throughput row
https://techspecs.ui.com/unifi/integrations/umr-industrial-us 693,659 same "LTE Cat 4 radio" and throughput row; WiFi 4 to 300 Mbps

The Ultra and the Industrial have no datasheet (dl.ui.com/ds/umr-ultra_ds.pdf and
.../umr-industrial_ds.pdf answer the 609,911-byte techspecs front page), so those two rest on the
rendered spec table - the same surface the earlier passes on this family already cited.

What changed

file was now
devices/ubiquiti/umr.json rj45-1, rj45-2, radio-2g + wwan0 wireless 150M
devices/ubiquiti/umr-ultra.json rj45-1, rj45-2, radio-2g + wwan0 wireless 150M
devices/ubiquiti/umr-industrial.json wwan0 50M wwan0 150M

150 Mbps is the published download figure - the convention udr-5g-max (5G NSA downlink) and
u5g-max already use. The 50 Mbps uplink is recorded in notes rather than in a field, because the
schema carries one rate per port. umr-industrial.json's 50M was the uplink half of the same table
row, which made it the only row in the family reading the wrong column.

Why it is not cosmetic

A wwan port cannot be cabled - test/cellular-cage.test.js pins that two modems are not cabled to
each other, they are both subscribed to a network neither contains - so a cellular WAN in this
engine is an interface you configure. Before, the UMR offered nothing to configure:

Interface              IP-Address      OK? Method Status                Protocol
rj45-1                 unassigned      YES unset  down                  down
rj45-2                 unassigned      YES unset  down                  down
radio-2g               unassigned      YES unset  up                    up

After, the lab's cellular WAN exists and can carry the default route:

R1(config-if)# ip address 10.99.0.10 255.255.255.0
IP address set on wwan0: 10.99.0.10/24
R1(config)# ip route 0.0.0.0 0.0.0.0 10.99.0.1
Route added: 0.0.0.0/0 via 10.99.0.1
R1# show ip route
S*  0.0.0.0/0  [1/0] via 10.99.0.1

Cage resolution was measured, not assumed: wwan0 -> cage=wwan, media=['lte'], 150 Mbps;
radio-2g stays antenna. No cellular port offers a copper medium and no port sources power.

Gates

  • node scripts/syntax-check.js - 454 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
  • node test/cellular-cage.test.js - 18 passed, 0 failed (every cellular port has a medium)
  • node test/catalogue-hygiene.test.js - 25 passed, 0 failed
  • node test/poe.test.js / poe-inference / poe-agreement - 21/17/17 passed, 0 failed
  • node test/doc-catalog-counts.test.js - 43 passed; node test/doc-citations.test.js - 11 passed
  • node scripts/regen-registry-doc.js - regenerated: 2,356 models, 29,718 sockets (+2), 972 port shapes
  • node scripts/audit-poe-budget.js - 104 of 405 PSEs silent (unchanged by this PR)

research/ubiquiti-mobile-router-census.md records the census, the traps and one measured
follow-up left for its own pass: u-lte-backup-pro.json still carries wwan0 at 100M while its
own datasheet prints "Download 150 Mbps / Upload 50 Mbps" - the earlier comment claiming that
correction does not match main.

This does not model a Dream Wall Pro, and it does not settle that request: no Ubiquiti surface names
UDW-PRO (see the issue thread). Issue 130 stays open with its blocker unchanged.

Refs #130 The lab in that request wants "a router/gateway node ... (NAT, DHCP, VPN, cellular WAN)". The Mobile Router family is what a requester is handed for the cellular half of it, and **two of its three rows had no cellular port at all**. `devices/ubiquiti/umr.json` and `devices/ubiquiti/umr-ultra.json` modelled `rj45-1`, `rj45-2` and `radio-2g` - two copper ports and the **WiFi 4** radio - and no `wwan` port. `umr-industrial.json`, the third member, has carried a `wwan0` all along, so the family disagreed with itself about whether an LTE radio is an interface. ## The vendor names the radio in the first row of the table | surface (read 2026-11-19, crawler user-agent) | bytes | row | |---|---|---| | `https://techspecs.ui.com/unifi/integrations/umr-us` | 708,698 | "Networking Interface (2) GbE RJ45 ports, **LTE Cat 4 radio**, WiFi 4"; "LTE Throughput Speed **Download 150 Mbps / Upload 50 Mbps**" | | `https://dl.ui.com/ds/umr_ds.pdf` | 597,924, PDF, 2 pp | p2: "LTE throughput speed* **Download 150 Mbps / Upload 50 Mbps**", "LTE Category 4 radio", WiFi 4 "6.5 Mbps to 150 Mbps" | | `https://techspecs.ui.com/unifi/integrations/umr-ultra-us` | 682,619 | "(2) FE RJ45 ports, **LTE Cat 4 radio**, WiFi 4"; same throughput row | | `https://techspecs.ui.com/unifi/integrations/umr-industrial-us` | 693,659 | same "LTE Cat 4 radio" and throughput row; WiFi 4 to 300 Mbps | The Ultra and the Industrial have no datasheet (`dl.ui.com/ds/umr-ultra_ds.pdf` and `.../umr-industrial_ds.pdf` answer the 609,911-byte techspecs front page), so those two rest on the rendered spec table - the same surface the earlier passes on this family already cited. ## What changed | file | was | now | |---|---|---| | `devices/ubiquiti/umr.json` | rj45-1, rj45-2, radio-2g | + `wwan0` wireless **150M** | | `devices/ubiquiti/umr-ultra.json` | rj45-1, rj45-2, radio-2g | + `wwan0` wireless **150M** | | `devices/ubiquiti/umr-industrial.json` | `wwan0` **50M** | `wwan0` **150M** | 150 Mbps is the published **download** figure - the convention `udr-5g-max` (5G NSA downlink) and `u5g-max` already use. The 50 Mbps uplink is recorded in `notes` rather than in a field, because the schema carries one rate per port. `umr-industrial.json`'s 50M was the uplink half of the same table row, which made it the only row in the family reading the wrong column. ## Why it is not cosmetic A `wwan` port cannot be cabled - `test/cellular-cage.test.js` pins that two modems are not cabled to each other, they are both subscribed to a network neither contains - so a cellular WAN in this engine is an interface you *configure*. Before, the UMR offered nothing to configure: ``` Interface IP-Address OK? Method Status Protocol rj45-1 unassigned YES unset down down rj45-2 unassigned YES unset down down radio-2g unassigned YES unset up up ``` After, the lab's cellular WAN exists and can carry the default route: ``` R1(config-if)# ip address 10.99.0.10 255.255.255.0 IP address set on wwan0: 10.99.0.10/24 R1(config)# ip route 0.0.0.0 0.0.0.0 10.99.0.1 Route added: 0.0.0.0/0 via 10.99.0.1 R1# show ip route S* 0.0.0.0/0 [1/0] via 10.99.0.1 ``` Cage resolution was measured, not assumed: `wwan0` -> `cage=wwan`, `media=['lte']`, 150 Mbps; `radio-2g` stays `antenna`. No cellular port offers a copper medium and no port sources power. ## Gates - `node scripts/syntax-check.js` - 454 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 - `node test/cellular-cage.test.js` - 18 passed, 0 failed (every cellular port has a medium) - `node test/catalogue-hygiene.test.js` - 25 passed, 0 failed - `node test/poe.test.js` / `poe-inference` / `poe-agreement` - 21/17/17 passed, 0 failed - `node test/doc-catalog-counts.test.js` - 43 passed; `node test/doc-citations.test.js` - 11 passed - `node scripts/regen-registry-doc.js` - regenerated: 2,356 models, 29,718 sockets (+2), 972 port shapes - `node scripts/audit-poe-budget.js` - 104 of 405 PSEs silent (unchanged by this PR) `research/ubiquiti-mobile-router-census.md` records the census, the traps and one measured follow-up left for its own pass: `u-lte-backup-pro.json` still carries `wwan0` at 100M while its own datasheet prints "Download 150 Mbps / Upload 50 Mbps" - the earlier comment claiming that correction does not match `main`. This does not model a Dream Wall Pro, and it does not settle that request: no Ubiquiti surface names `UDW-PRO` (see the issue thread). Issue 130 stays open with its blocker unchanged.
devices(ubiquiti): the mobile routers had no cellular port to route out of (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 13s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 10s
CI / Test (Node 22) (pull_request) Successful in 59s
CI / Test (Node 20) (pull_request) Successful in 1m4s
CI / Docker build (pull_request) Successful in 22s
CI / Test (Node 18) (pull_request) Successful in 1m7s
CI / Arm auto-merge (pull_request) Successful in 5s
332baa6236
umr.json and umr-ultra.json modelled rj45-1, rj45-2 and the WiFi 4 radio, and no
wwan port, so the LTE radio the product is named for had no interface and the
cellular WAN of the lab in issue 130 could not be configured. umr-industrial.json
carried wwan0 at 50M - the uplink half of the same vendor row.

Vendor rows (read 2026-11-19):
  techspecs umr-us 708,698 B: 'Networking Interface (2) GbE RJ45 ports, LTE Cat 4
  radio, WiFi 4'; 'LTE Throughput Speed Download 150 Mbps / Upload 50 Mbps'
  dl.ui.com/ds/umr_ds.pdf 597,924 B p2: 'LTE throughput speed* Download 150 Mbps /
  Upload 50 Mbps', 'LTE Category 4 radio'
  techspecs umr-ultra-us 682,619 B: same LTE Cat 4 radio and throughput row
  techspecs umr-industrial-us 693,659 B: same row, WiFi 4 to 300 Mbps

wwan0 is 150M on all three (download, the convention udr-5g-max and u5g-max use).
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 13:58:53 +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!2160
No description provided.