devices(teltonika): the ALTOS CAP700 could not route, and claimed PoE it cannot take (refs #130) #2172

Merged
jaylouisw merged 1 commit from catalogue/1119-1522 into main 2026-11-19 15:42:04 +00:00
Owner

refs #130 (records the catalogue defect found underneath this request; it does not close it)

#130 asks for a Dream Wall Pro and is still blocked - no Ubiquiti surface names UDW-PRO, and those nine surfaces were not re-walked this pass (last measured 13:25 today, nothing has changed). It spent the increment on the routed lab half of the request - "a router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN)" - and found the cheapest 5G FWA box in the catalogue could not be the gateway.

devices/teltonika/cap700.json - the Teltonika ALTOS CAP700 - was filed as an access point with a phantom power source:

field before vendor
category wireless "5G Wi-Fi 7 router" (vendor copy, wiki category "ALTOS Routers", product path /products/routers/altos)
routing no l3-forward, no l2-forward CAP700_Routes: "the router's ARP table and active IPv4 and IPv6 routes"; CAP700_WAN: "Ethernet WAN"/"Mobile WAN" under "Static DHCP DHCPv6 PPPoE"
ip route 0.0.0.0/0 % ... cannot install a route: it has no l3-forward capability now Route added: 0.0.0.0/0 via 10.0.0.1
show ip route "Default gateway is not set" over the host/redirect cache the routing table
power poe-pd CAP700_Powering_Options: barrel jack only, "can be powered by a 12 VDC power supply unit"; flyer "DC power jack socket 2-pin, 12 VDC 2A 24W" - no PoE at all
wwan1 2.5G "5G NR up to 4.0 Gbps DL / 900 Mbps UL" - 2.5G is the Ethernet port's rate, no cellular figure Teltonika prints
cli, http-server absent Interfaces: SSH 22/tcp, HTTPS 443/tcp

wwan1 also pins media: [lte, lte-a, 5g-sub6]: the vendor names 5G NR, LTE Cat 19 and 3G and never names mmWave, and 4000 Mbps is exactly MEDIA['5g-mmwave'].speedMbps, so an unpinned 4.0G radio would offer a band the vendor does not sell.

Sources (all read 2026-11-19): https://wiki.teltonika-networks.com/view/CAP700 (200, 57,164 B), /CAP700_Interfaces, /CAP700_Powering_Options, /CAP700_Routes, /CAP700_WAN, /CAP700_LAN, /CAP700_VLAN, and Teltonika's ALTOS flyer CAP700_Flyer_2026_-v1.1 (https://eshop.sectron.eu/UserFiles/File/Teltonika_ALTOS_Flyer.pdf, 200, PDF, 597,507 B, text layer). The old sourceUrl (/product/cap700/) is dead: 301 then 404 on a 2.3 MB soft-404 page - recorded in notes so the next pass does not read that 404 as a redirect. Two vendor ports (RJ11 telephony, micro-USB network interface) are named in notes as modelling boundaries - the catalogue has no telephony or USB interface type.

research/incoming/devices-teltonika-batch58.json carries the same CAP700 row and is corrected with it, so a re-import cannot put the phantom PoE back.

Gates: syntax-check 458 OK; audit-port-types clean; hardware invariants 26/0; catalogue hygiene 25/0; capability vocabulary 13/0; doc-catalog-counts 43/0 (registry doc regenerated, router 384 -> 385, wireless 219 -> 218); importer dry run - 0 rejected, 0 capability losses; run-tests 379 suites, 12,849 assertions, 0 failed.

Still missing for #130 itself, unchanged: RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming UDW-PRO, or the requester confirming they meant the UDW (devices/ubiquiti/udw.json).

refs #130 (records the catalogue defect found underneath this request; it does not close it) #130 asks for a Dream Wall Pro and is still blocked - no Ubiquiti surface names `UDW-PRO`, and those nine surfaces were not re-walked this pass (last measured 13:25 today, nothing has changed). It spent the increment on the *routed lab* half of the request - "a router/gateway node in a routed lab (NAT, DHCP, VPN, cellular WAN)" - and found the cheapest 5G FWA box in the catalogue could not be the gateway. `devices/teltonika/cap700.json` - the Teltonika ALTOS CAP700 - was filed as an access point with a phantom power source: | field | before | vendor | |---|---|---| | category | `wireless` | "5G Wi-Fi 7 **router**" (vendor copy, wiki category "ALTOS Routers", product path `/products/routers/altos`) | | routing | no `l3-forward`, no `l2-forward` | `CAP700_Routes`: "the router's ARP table and active IPv4 and IPv6 routes"; `CAP700_WAN`: "Ethernet WAN"/"Mobile WAN" under "Static DHCP DHCPv6 PPPoE" | | `ip route 0.0.0.0/0` | `% ... cannot install a route: it has no l3-forward capability` | now `Route added: 0.0.0.0/0 via 10.0.0.1` | | `show ip route` | "Default gateway is not set" over the host/redirect cache | the routing table | | power | `poe-pd` | `CAP700_Powering_Options`: barrel jack only, "can be powered by a 12 VDC power supply unit"; flyer "DC power jack socket 2-pin, 12 VDC 2A 24W" - **no PoE at all** | | `wwan1` | 2.5G | "5G NR up to 4.0 Gbps DL / 900 Mbps UL" - 2.5G is the *Ethernet* port's rate, no cellular figure Teltonika prints | | `cli`, `http-server` | absent | Interfaces: SSH 22/tcp, HTTPS 443/tcp | `wwan1` also pins `media: [lte, lte-a, 5g-sub6]`: the vendor names 5G NR, LTE Cat 19 and 3G and never names mmWave, and 4000 Mbps is exactly `MEDIA['5g-mmwave'].speedMbps`, so an unpinned 4.0G radio would offer a band the vendor does not sell. Sources (all read 2026-11-19): https://wiki.teltonika-networks.com/view/CAP700 (200, 57,164 B), `/CAP700_Interfaces`, `/CAP700_Powering_Options`, `/CAP700_Routes`, `/CAP700_WAN`, `/CAP700_LAN`, `/CAP700_VLAN`, and Teltonika's ALTOS flyer CAP700_Flyer_2026_-v1.1 (https://eshop.sectron.eu/UserFiles/File/Teltonika_ALTOS_Flyer.pdf, 200, PDF, 597,507 B, text layer). The old `sourceUrl` (`/product/cap700/`) is dead: 301 then **404 on a 2.3 MB soft-404 page** - recorded in `notes` so the next pass does not read that 404 as a redirect. Two vendor ports (RJ11 telephony, micro-USB network interface) are named in `notes` as modelling boundaries - the catalogue has no telephony or USB interface type. `research/incoming/devices-teltonika-batch58.json` carries the same CAP700 row and is corrected with it, so a re-import cannot put the phantom PoE back. Gates: syntax-check 458 OK; audit-port-types clean; hardware invariants 26/0; catalogue hygiene 25/0; capability vocabulary 13/0; doc-catalog-counts 43/0 (registry doc regenerated, router 384 -> 385, wireless 219 -> 218); importer dry run - 0 rejected, 0 capability losses; run-tests **379 suites, 12,849 assertions, 0 failed**. Still missing for #130 itself, unchanged: RJ45 and SFP+ counts and rates, which are WAN, the PoE class mix and total budget, drive bays, cellular/WAN options. Unblock, unchanged: any Ubiquiti-hosted page, datasheet, quick-start, FCC exhibit, storefront entry, KB article or controller device record naming `UDW-PRO`, or the requester confirming they meant the `UDW` (`devices/ubiquiti/udw.json`).
devices(teltonika): the ALTOS CAP700 could not route, and claimed PoE it cannot take (refs #130)
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 10s
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 57s
CI / Test (Node 22) (pull_request) Successful in 57s
CI / Test (Node 18) (pull_request) Successful in 1m2s
CI / Arm auto-merge (pull_request) Successful in 3s
3e82a6fdc2
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-19 15:37:16 +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!2172
No description provided.