Document: toggled interfaces must not carry a CARP VIP #5

New issue

Closed

opened 2026-10-18 17:14:41 -07:00 by eric · 0 comments

eric commented

2026-10-18 17:14:41 -07:00

Owner

Severity: Medium · Location: 10-wancarp:155-159 (config comment), README Configuration section

The config comment offers 'lan' and 'opt1' as example aliases. If a listed interface has a CARP VIP, taking it down on the BACKUP:

puts that VHID into INIT, so it can never become MASTER through that interface;
raises the node's demotion counter (net.inet.carp.ifdown_demotion_factor), which skews elections on every other VHID.

That can break failover, including maintenance-mode failover.

Suggested fix:

State in the README and the config comment that no toggled interface may carry a CARP VIP.
Optionally, add a dry-run preflight check that warns when a listed alias has a CARP VIP.

**Severity:** Medium · **Location:** `10-wancarp:155-159` (config comment), README Configuration section The config comment offers `'lan'` and `'opt1'` as example aliases. If a listed interface has a CARP VIP, taking it down on the BACKUP: - puts that VHID into INIT, so it can never become MASTER through that interface; - raises the node's demotion counter (`net.inet.carp.ifdown_demotion_factor`), which skews elections on every other VHID. That can break failover, including maintenance-mode failover. **Suggested fix:** - State in the README and the config comment that no toggled interface may carry a CARP VIP. - Optionally, add a dry-run preflight check that warns when a listed alias has a CARP VIP.

eric added the

bug

label

2026-10-18 17:14:41 -07:00

eric referenced this issue from a commit

2026-10-18 17:32:02 -07:00

docs: forbid CARP VIPs on toggled interfaces; flag them in dry-run

eric closed this issue

2026-10-18 17:32:02 -07:00

eric referenced this issue

2026-10-18 17:32:18 -07:00

Pre-release live HA test plan #11