Bug #4633
CARP not enabled upon creation of first CARP IP
Start date:
04/18/2015
Due date:
% Done:
100%
Estimated time:
Affected Version:
2.2
Affected Architecture:
Description
On a new system, after creating a new CARP VIP, the CARP Status gadget for the dashboard shows "Disabled".
Turns out you have to go to Status->CARP and click "Enable CARP" before CARP works.
This conflicts with standard practice of always using CARP VIPs, and nothing indicates that CARP needs to be "enabled", whatever that means.
Associated revisions
Fixes #4633 Enable carp packets to flow on the first carp interface creation. This is needed only when the system is booted up without any carp vip configured
History
#1
Updated by Chris Buechler about 4 years ago
Updated by - Project changed from pfSense Packages to pfSense
- Subject changed from CARP not enabled by default to CARP not enabled upon creation of first CARP IP
- Category set to CARP
- Status changed from New to Confirmed
- Target version set to 2.2.3
- Affected Version changed from 2.2.2 to 2.2
#2
Updated by Ermal Luçi about 4 years ago
Updated by Ermal Luçi - Status changed from Confirmed to Feedback
#3
Updated by Ermal Luçi about 4 years ago
- % Done changed from 0 to 100
Applied in changeset 6e4c8e92f8f0407468eccb4c76f4f5affc598d1d.
#4
Updated by Ermal Luçi about 4 years ago
Applied in changeset 3a09e0d96e63e5a8fafcad9199ab2c1d657d68b9.
Fixes #4633 Enable carp packets to flow on the first carp interface creation. This is needed only when the system is booted up without any carp vip configured