Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/KevinCruz-cell/Redes-de-comunicaciones-/llms.txt

Use this file to discover all available pages before exploring further.

The dashboard gives you a unified view of your router’s health and activity. It pulls live data over SSH and displays system metrics, network state, and log output without requiring you to open a terminal. Navigate to /dashboard after logging in to access the dashboard.
The dashboard connects to your OpenWrt router via SSH on every page load and on each polling interval. Make sure the router is reachable on the configured IP address before opening this page.

​
Dashboard panels

The dashboard is divided into several data panels, each populated by a dedicated API endpoint.

System info

General system information retrieved via getSystemInfo(), including hostname, firmware version, architecture, and kernel version.

CPU and memory

Real-time CPU usage percentage (via top -bn1) and memory consumption in megabytes (via free -m).

Firewall rules

Active iptables chains and rules retrieved with iptables -L -n -v, showing packet and byte counters for each rule.

Routing table

The kernel routing table fetched via ip route show, displaying all active routes with gateway, interface, and metric.

System log (syslog)

The last 100 lines of the OpenWrt system log, read using logread | tail -100.

Kernel log (dmesg)

The last 100 kernel ring buffer messages from dmesg | tail -100, useful for diagnosing hardware events.

Process list

All running processes on the router, fetched with ps aux | head -100, showing PID, CPU, memory, and command.

Real-time stats

Live CPU usage, used/total memory, load averages, active connections, and uptime — refreshed automatically via /api/dashboard/realtime.

​
Commands used

Each panel maps to one or more shell commands executed over SSH:
PanelCommand
CPU usagetop -bn1 | grep 'Cpu(s)' | awk '{print $2}' | cut -d'%' -f1
Memory usedfree -m | grep Mem | awk '{print $3}'
Memory totalfree -m | grep Mem | awk '{print $2}'
Load averagecat /proc/loadavg | cut -d' ' -f1-3
Uptimecat /proc/uptime | awk '{print int($1/3600)"h "int(($1%3600)/60)"m"}'
Active connectionsnetstat -an | grep ESTABLISHED | wc -l
Firewall rulesiptables -L -n -v
Routing tableip route show
System loglogread | tail -100
Kernel logdmesg | tail -100
Process listps aux | head -100

​
Real-time stats endpoint

The /api/dashboard/realtime endpoint returns a JSON object with live router metrics. The dashboard polls this endpoint periodically to keep the stats panel current. 
{
  "status": "success",
  "data": {
    "cpu": "3.2",
    "memory": "42",
    "memory_total": "128",
    "load": "0.12 0.08 0.05",
    "connections": "7",
    "uptime": "2h 34m"
  }
}

​
Other dashboard API endpoints

EndpointDescription
GET /api/dashboard/dataFull system info snapshot
GET /api/dashboard/firewalliptables rules
GET /api/dashboard/routesKernel routing table
GET /api/dashboard/syslogLast 100 syslog entries
GET /api/dashboard/kernelLast 100 dmesg entries
GET /api/dashboard/processesRunning process list
GET /api/dashboard/realtimeLive CPU, memory, load, connections, uptime
All endpoints return a JSON envelope with status ("success" or "error") and a data field containing the raw command output as a string. 
{
  "status": "success",
  "data": "..."
}
If a panel shows no data, check that the SSH session is authenticated and that the router is running the expected OpenWrt tools (iptables, logread, dmesg). Some minimal firmware builds omit these utilities.

Build docs developers (and LLMs) love

Get started for freeTalk to us