From 8fce03e705cd1a3a79add157431119b6e4df52b5 Mon Sep 17 00:00:00 2001 From: Michal Date: Sun, 6 Sep 2026 01:26:38 +0100 Subject: [PATCH] PPPOE-HA: deployed to production Mechanism installed on both routers (--check clean against git on both), `interfaces pppoe pppoe0 disable` removed from vyos002, and vyos002 is out of FAULT and holding BACKUP on all six groups for the first time in 3d10h -- the lab has a real standby again. Verified on the wire rather than from state: with a tcpdump running on vyos002's bond0.51 across the commit, ZERO PADI/PADR. The peers file rendered (so it can dial the instant it is promoted) while ConditionResult stayed `no` and NRestarts 0. vyos001's live session was untouched throughout -- same MainPID 2931, same 83.106.5.72, internet 7.6-8.4ms at 0% loss. Not done, deliberately: the controlled failover drill, which interrupts the household's internet, and merging the staged Pulumi override, which lands via another agent's `pulumi up` on a branch they have checked out. --- migration/PPPOE-HA.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/migration/PPPOE-HA.md b/migration/PPPOE-HA.md index 993b7e8..d3b74a8 100644 --- a/migration/PPPOE-HA.md +++ b/migration/PPPOE-HA.md @@ -1,6 +1,8 @@ # PPPoE high availability -Proven in labsim. **Not applied to production.** +Proven in labsim. **Deployed to production 2026-09-06** — mechanism on both +routers, `pppoe0 disable` removed from vyos002, vyos002 out of FAULT and in +BACKUP. The Pulumi override (step 8) is still staged, not merged. ## What it does