| Age | Commit message (Collapse) | Author |
|---|
|
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 <noreply@anthropic.com>
|
|
core.fileMode is false in this repo (Windows checkout), so the earlier
commit recorded every checks/*.sh, lib/common.sh, and render.sh as
100644. render.sh skips non-executable files silently, so without this
the deployed page would render with zero rows.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
|
Replace the single-file prototype with independently-addable check
scripts (checks/*.sh) that each emit JSONL rows, a shared helper lib,
and one orchestrator/renderer (render.sh) that groups rows by section
and writes the static status page. A broken check script now shows up
as a down/warn row instead of crashing the whole render.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
