Monitor Teltonika · OpenWrt with an agent that reports to one console.
RutOS on RUTX and similar ARM routers, OpenWrt 21+. Cellular signal, operator, SIM and data counters in every heartbeat. Survives sysupgrade. BE AI investigates when something fails; a person approves the fix.
install
One line, from the company's install page.
Run in the router's shell. It fetches the signed binary, verifies the checksum, installs the service and connects. Run it again any time; it never overwrites the machine's identity.
wget -O - https://hub.[yourdomain]/install/inst_…/openwrt.sh | sh
Outbound 443 to the hub only. No inbound rule, no VPN, no SNMP community.
what the agent watches on Teltonika · OpenWrt
CellularRSSI, RSRP, RSRQ, SINR, operator, network type, SIM state, bands, temperature and byte counters, from the router's own API.
procd servicesEnabled services that are not running, restart proposed and approved.
Loglogread on demand, capped.
ReachabilityPing the carrier gateway, the VPN peer, head office.
Survives sysupgradePaths are added to the upgrade keep-list; the service comes back on its own.
Not for 16 MB flashRUT2xx and RUT9xx do not have room for the 6 MB binary; RUTX and larger do.
questions
Before you put it on Teltonika.
Which models?
Teltonika RUTX11 verified on RutOS 7.22; other RUTX and TRB models with ARMv7 should work. OpenWrt 21 and later on ARMv7. [Confirm before publishing.]
Does it need the carrier to allow inbound?
No. One outbound HTTPS connection, which is what a 4G SIM with a private address can do.
Put BE Hub on ten machines this week.
A pilot takes an afternoon: one install link, your own approvals, your own data. Uninstall the agent and you are out.