Hey guys- good questions! I remember asking myself the same question and what
helped me was reading the RFC for VRRP/CARP. essentially when the old master
domes back up it will pick up the changes because there will already be a
master running on the pvid, what used to be the slave.
To be
On 16/02/2014 20:25, Joel Robison wrote:
Hey guys- good questions! I remember asking myself the same question
and what helped me was reading the RFC for VRRP/CARP. essentially when
the old master domes back up it will pick up the changes because there
will already be a master running on the
Hi Brian and Joel,
I resolved the sync issue today in my environment, I just supplied the IP
address of primary(Master) server in the secondary(Slave) server's pfsync
config in the section for syncing state tables (I already had the sync
state table enabled on secondary server), now if the master
See your link http://www.openbsd.org/faq/pf/carp.html
It's all in there.
-- Jim
On Feb 16, 2014, at 12:03, rajan agarwal rajanagarwa...@gmail.com wrote:
I was about to post the same question. Thanks Brian, been facing a problem
with this in my 2 pfsense setup.
On Sun, Feb 16, 2014
On 17/02/2014 14:33, Jim Thompson wrote:
See your link http://www.openbsd.org/faq/pf/carp.html
Yes I've read it. As far as I can see, it talks about state change
messages and state table updates only. I see nothing about
re-synchronising the entire state table; if that happens, under what
On 2/17/2014 12:17 PM, Brian Candler wrote:
I don't know whether the version of pf in pfsense/FreeBSD 8.3 implements
this. If this functionality has been in there since the introduction of
pfsync then presumably it does.
Also: pfsense optionally lets you configure an IP to unicast state
Greetings list,
A few days ago I finally found time to upgrade my ageing pfSense 2.1-RC0
at home to 2.1 final. Since that upgrade I've noticed that pfSense
doesn't seem to be handling state killing on failed gateways very well.
A bit of background: I live in a rural location with poor
On Mon, Feb 17, 2014 at 11:35 AM, Chris Bagnall
pfse...@lists.minotaur.cc wrote:
Greetings list,
A few days ago I finally found time to upgrade my ageing pfSense 2.1-RC0 at
home to 2.1 final. Since that upgrade I've noticed that pfSense doesn't seem
to be handling state killing on failed
