ut (we have CARP IPs
>for two LANs and a WAN, and both IPv4 and IPv6, on two virtualized
>routers).
>>
>> --
>>
>> Steve Yates
>> ITS, Inc.
>>
>> -Original Message-
>> From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of
>A
: [pfSense] CARP Demotion Not Working
An update on this, if the master node is rebooted during a failure, the
secondary node takes cover correctly and remains the master as would be
expected.
This makes me think that the priority is set correctly but the second
node for some reason isn't honoring t
and a
WAN, and both IPv4 and IPv6, on two virtualized routers).
--
Steve Yates
ITS, Inc.
-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Andrew Kester
Sent: Friday, November 3, 2017 10:49 AM
To: list@lists.pfsense.org
Subject: Re: [pfSense] CARP Demotion N
An update on this, if the master node is rebooted during a failure, the
secondary node takes cover correctly and remains the master as would be
expected.
This makes me think that the priority is set correctly but the second
node for some reason isn't honoring the advskew set by the master
Hi List,
I'm having an issue with CARP preempt. I have two pfSense machines
running 2.4.1-RELEASE. CARP fails over all individual IPs correctly,
but doesn't preempt correctly in the case of a single failure.
On both machines, I've checked that net.inet.carp.preempt is enabled.
The master
