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/lib/common.sh | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'statuspage/lib') diff --git a/statuspage/lib/common.sh b/statuspage/lib/common.sh index d063e07..dcc26f5 100755 --- a/statuspage/lib/common.sh +++ b/statuspage/lib/common.sh @@ -47,3 +47,11 @@ port_check() { jail_status() { jls -j "$1" >/dev/null 2>&1 && echo "ok" || echo "down" } + +# proc_running PATTERN +# Prints "ok" or "down" depending on whether any process's command line +# matches PATTERN (pgrep -f). For ad-hoc background processes that +# aren't rc.d-managed, so there's no `service ... status` for them. +proc_running() { + pgrep -f "$1" >/dev/null 2>&1 && echo "ok" || echo "down" +} -- cgit v1.3