andreas/vanlink
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

post-check: failover check warns only on link without NM connection; retry, stub-nmcli tests

Browse Source 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KqhjP7nud5gdBg25zCiRk9
This commit is contained in:
andreas
2026-09-23 19:11:55 -04:00
co-authored by Claude Sonnet 5
parent 2601472576
commit 698f9ee446
3 changed files with 78 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -22,7 +22,7 @@ shows, read-only, what the provisioning would do. `--post-check` reports the las
Live WAN state: `cat /run/van-failover/state.json` lists each WAN with `device`, `connection`,
`present` (device and connection both resolved), `up`, `healthy`, `active` (holds the best default
route) and `route_metric`. `present: false` for an existing device is a problem; `--post-check` warns.
route) and `route_metric`. An unplugged or out-of-range uplink (`present: false`, no carrier) is expected in a van; `present: false` on a device that has link is the actionable case (not handed to NM yet, or its profile is missing), and `--post-check` warns about exactly that.
Known limitation: there is no boot-time recovery yet. If power is lost during an apply, the new
config boots ungated and the status file still says `running`; `--apply-network` then refuses to run