devices(ubiquiti): the mobile routers had no cellular port to route out of #2160
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!2160
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1119-1352"
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 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.jsonanddevices/ubiquiti/umr-ultra.jsonmodelledrj45-1,rj45-2andradio-2g- two copper ports and the WiFi 4 radio - and nowwanport.umr-industrial.json,the third member, has carried a
wwan0all along, so the family disagreed with itself aboutwhether an LTE radio is an interface.
The vendor names the radio in the first row of the table
https://techspecs.ui.com/unifi/integrations/umr-ushttps://dl.ui.com/ds/umr_ds.pdfhttps://techspecs.ui.com/unifi/integrations/umr-ultra-ushttps://techspecs.ui.com/unifi/integrations/umr-industrial-usThe Ultra and the Industrial have no datasheet (
dl.ui.com/ds/umr-ultra_ds.pdfand.../umr-industrial_ds.pdfanswer the 609,911-byte techspecs front page), so those two rest on therendered spec table - the same surface the earlier passes on this family already cited.
What changed
devices/ubiquiti/umr.jsonwwan0wireless 150Mdevices/ubiquiti/umr-ultra.jsonwwan0wireless 150Mdevices/ubiquiti/umr-industrial.jsonwwan050Mwwan0150M150 Mbps is the published download figure - the convention
udr-5g-max(5G NSA downlink) andu5g-maxalready use. The 50 Mbps uplink is recorded innotesrather than in a field, because theschema carries one rate per port.
umr-industrial.json's 50M was the uplink half of the same tablerow, which made it the only row in the family reading the wrong column.
Why it is not cosmetic
A
wwanport cannot be cabled -test/cellular-cage.test.jspins that two modems are not cabled toeach 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:
After, the lab's cellular WAN exists and can carry the default route:
Cage resolution was measured, not assumed:
wwan0->cage=wwan,media=['lte'], 150 Mbps;radio-2gstaysantenna. No cellular port offers a copper medium and no port sources power.Gates
node scripts/syntax-check.js- 454 files, all OKnode scripts/audit-port-types.js- "No port contradicts its declared type."node test/hardware-invariants.test.js- 26 passed, 0 failednode test/cellular-cage.test.js- 18 passed, 0 failed (every cellular port has a medium)node test/catalogue-hygiene.test.js- 25 passed, 0 failednode test/poe.test.js/poe-inference/poe-agreement- 21/17/17 passed, 0 failednode test/doc-catalog-counts.test.js- 43 passed;node test/doc-citations.test.js- 11 passednode scripts/regen-registry-doc.js- regenerated: 2,356 models, 29,718 sockets (+2), 972 port shapesnode scripts/audit-poe-budget.js- 104 of 405 PSEs silent (unchanged by this PR)research/ubiquiti-mobile-router-census.mdrecords the census, the traps and one measuredfollow-up left for its own pass:
u-lte-backup-pro.jsonstill carrieswwan0at 100M while itsown 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.