Hi,
What is the average time for the carp failover to kick in... i.e. how
much time does it take for the backup to become master and start
serving requests and vice versa? Is the timing parameter configurable?
I have both the WAN and LAN gw as carp ip.
Version2.0-RC1 (i386)
built on Thu Mar 17
On Thu 30 Jun 2011 12:12:55 NZST +1200, Volker Kuhlmann wrote:
A reboot cleared the packages are being updated in thebackground
status, all packages have been installed and I haven't detected any
other misbehaviour.
So only a minor glitch in the updater.
Thanks,
Volker
--
Volker Kuhlmann
I have an internal (LAN) IP address of 10.2.67.11 and an external (WAN) IP of
10.2.66.15
What is the best way to ensure that I do not NAT packets from 10.2.66.15 to
10.2.67.11 but still retaining a firewall
Is there a How to of how I would achieve this
I am running PFSense RC2 (latest update)
As I am a newbie, how actually do I do this? And, how do I make sure that
ougoing packets to the Internet get PAT applied via the WAN NIC? (But it
doesn't effect incoming packets?
This is an internal firewall that is going to be used to protect a higher
classified network. The WAN connection
What is the average time for the carp failover to kick in... i.e. how
much time does it take for the backup to become master and start
serving requests and vice versa? Is the timing parameter configurable?
I have both the WAN and LAN gw as carp ip.
I as a human have never been faster then the
I think we're discussing timeouts related to OSI levels 2 or 3. A
physical disconnect is of course immediate, but i think other factors
should be considered, like watchdog style errors, ping timeouts, and
transport layer failures.
I hope we can document points of failure and expected delays
On Sat, Jul 2, 2011 at 4:34 AM, Shibashish shi...@gmail.com wrote:
Hi,
What is the average time for the carp failover to kick in... i.e. how
much time does it take for the backup to become master and start
serving requests and vice versa?
Immediate if it's expected (i.e. you reboot the
