From a034c6724381b172ba4b6d36357682c44f18b8de Mon Sep 17 00:00:00 2001 From: batsumaru <> Date: Wed, 1 Jul 2026 16:52:22 +0900 Subject: Add pf visibility and a wg-quick watcher check, add a neutral row status checks/pf.sh reports pf enabled/disabled, state table usage (warn/down as it nears the configured limit), and the loaded filter/nat rule count, then lists each active rule as its own row for at-a-glance visibility into what's actually being enforced. Those rule rows use a new "info" status (gray square) rather than "ok" - they're not a health check on any individual rule, so a green square there would misleadingly imply otherwise. render.sh maps info -> gray; anything else still falls back to red. checks/wg-watcher.sh checks the route-monitor process wg-quick spawns to react to WAN interface/address changes - it isn't rc.d-managed, so there's no `service status` for it, hence the new proc_running helper in lib/common.sh (pgrep -f based). Co-Authored-By: Claude Sonnet 5 --- statuspage/checks/wg-watcher.sh | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100755 statuspage/checks/wg-watcher.sh (limited to 'statuspage/checks/wg-watcher.sh') diff --git a/statuspage/checks/wg-watcher.sh b/statuspage/checks/wg-watcher.sh new file mode 100755 index 0000000..9351afd --- /dev/null +++ b/statuspage/checks/wg-watcher.sh @@ -0,0 +1,14 @@ +#!/bin/sh +# checks/wg-watcher.sh +# wg-quick's background route monitor (spawned by `wg-quick up wg0` to +# react to WAN interface/address changes) isn't rc.d-managed, so there's +# no `service ... status` for it. If it dies, wg0 itself stays up - the +# kernel interface doesn't depend on it - but the box stops reacting to +# WAN IP changes (e.g. a DHCP lease renewal) until wg-quick is restarted. +set -eu + +DIR=$(dirname "$0") +. "$DIR/../lib/common.sh" + +STATUS=$(proc_running "route -n monitor") +json_line "host services" "wg-quick watcher" "" "$STATUS" -- cgit v1.3