Use this file to discover all available pages before exploring further.
The dashboard aggregates five live data feeds from the router: the system log, kernel messages, running processes, active firewall rules, and the current routing table. Each view is fetched on demand by calling its API endpoint, which opens an SSH session to the router, runs the relevant command, and returns the raw text output.All log endpoints are available under /api/dashboard/ and are consumed by the main dashboard at /dashboard.
Endpoint:GET /api/dashboard/syslogCommand:logread | tail -100Returns the last 100 entries from the OpenWrt system log (logread reads from the ring buffer maintained by the syslog-ng or logd daemon).
Tue May 19 10:23:11 2026 daemon.notice netifd: wan (eth0.2): sending update to dependentsTue May 19 10:23:11 2026 daemon.notice netifd: Interface 'wan' is now upTue May 19 10:23:14 2026 daemon.info dnsmasq[1234]: read /etc/hosts - 2 addressesTue May 19 10:23:14 2026 daemon.info dnsmasq[1234]: using nameserver 8.8.8.8#53
Each line includes a timestamp, facility/severity level, the process that emitted the message, and the message itself. This log is the first place to check after configuration changes or connectivity drops.
Endpoint:GET /api/dashboard/kernelCommand:dmesg | tail -100Returns the last 100 lines of the kernel ring buffer. This log captures hardware events, driver messages, and low-level network interface state changes.
[ 0.000000] Linux version 5.15.137 (builder@openwrt) ...[ 2.310452] eth0: renamed from wan[ 2.418903] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready[ 12.003821] br-lan: port 1(eth1) entered forwarding state
Timestamps in brackets are seconds since boot. Use this view when troubleshooting hardware issues, driver errors, or unexpected interface resets.
Endpoint:GET /api/dashboard/processesCommand:ps aux | head -100Lists up to 100 running processes on the router, including CPU and memory usage per process.
Use this view to verify that expected services (like netifd, dnsmasq, or dropbear) are running, or to identify processes consuming unexpected resources.
Endpoint:GET /api/dashboard/firewallCommand:iptables -L -n -v | head -100Returns the first 100 lines of the active iptables ruleset with packet and byte counters (-v), numeric addresses (-n), and all chains across all tables.
Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0 142 9834 ACCEPT all -- br-lan * 0.0.0.0/0 0.0.0.0/0 0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:22
The pkts and bytes counters show how much traffic has matched each rule since the counters were last reset.
Endpoint:GET /api/dashboard/routesCommand:ip route showReturns the router’s full IPv4 routing table as reported by the kernel.
default via 203.0.113.1 dev eth0.2 proto dhcp src 203.0.113.100 metric 10192.168.10.0/24 dev br-lan proto kernel scope link src 192.168.10.1203.0.113.0/24 dev eth0.2 proto dhcp scope link src 203.0.113.100
Each line shows the destination network, the outgoing interface, the next-hop gateway, and the route source (e.g. dhcp, kernel, static). Unlike the firewall and process views, this endpoint returns the full output without a line limit.
All log views are embedded in the main dashboard at /dashboard.
1
Open the dashboard
Navigate to /dashboard. You must be logged in.
2
Select a log panel
Each log type is displayed in its own panel. Click a panel header or tab to load the corresponding data. The dashboard fetches data on demand — nothing is cached between page loads.
3
Refresh a view
To get updated output, reload the panel or refresh the page. Log data is fetched live each time from the router.
All data originates from the router itself. If the SSH connection to the router fails, the API returns a 500 error and the dashboard panel shows an error message instead of log data.
The application includes a development utility at /logs/postgresql for browsing local PostgreSQL log files.
PostgreSQL log viewer
The log viewer reads .log files from the hardcoded path C:\Program Files\PostgreSQL\17\data\log on the machine running the Laravel application. It lists available log files sorted by modification time and displays the content of the selected file.Navigate to /logs/postgresql and select a log file from the dropdown to view its contents. This view shows the application server’s local PostgreSQL logs — it has no connection to the OpenWrt router.
This page is configured for a Windows development environment. The log directory path C:\Program Files\PostgreSQL\17\data\log is hardcoded in PostgresLogController. If the directory does not exist on the server, the page shows an error. This feature is a development aid and is not related to router management.
