OpenWrtHub

CONNECTING_TO_NODES…

Managing a single OpenWrt router is straightforward. Managing 50 geographically distributed nodes is a logistical and security challenge. OpenWrtHub was built as an open-source alternative to proprietary controllers.

The Problem

Network deployments in rural areas or client facilities require remote maintenance, firmware upgrades, and bandwidth monitoring. Using SSH into each device individually does not scale.

The Solution: MQTT Topology

Instead of exposing SSH ports to the public internet (a massive security risk), OpenWrtHub reverses the communication flow.

1. A daemon running on the router (ubus bridge) publishes the node status (CPU, RAM, active interfaces) to a central MQTT broker.
2. The central server processes these payloads and stores them in Redis/PostgreSQL.
3. From the dashboard, the administrator can push commands (e.g., wifi down, reboots, package upgrades) which routers consume as subscribers of the broker.

[OpenWrt Router] ---> (TLS Publish) ---> [MQTT Broker] <--- (Subscribe) <--- [Python Backend]
                                                                                |
                                                                          [Web Dashboard]

The Result: Complete fleet control without exposing a single port in the client’s firewall.