From 3bba1fa10966948048b1bce88616de7cb139fc8f Mon Sep 17 00:00:00 2001 From: Scott Ullrich Date: Sat, 12 Mar 2005 17:03:53 +0000 Subject: * Do not ask for CARP pfsync ip, use the optional interfaces ip * Use optional interface IP for pfsync interface simplifying configuration --- packages/carp_settings.xml | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'packages/carp_settings.xml') diff --git a/packages/carp_settings.xml b/packages/carp_settings.xml index b52b96a0..f18accb3 100644 --- a/packages/carp_settings.xml +++ b/packages/carp_settings.xml @@ -62,17 +62,11 @@ PFSync transfers state insertion, update, and deletion messages between firewalls. Each firewall sends these messages out via multicast on a specified interface, using the PFSYNC protocol (IP Protocol 240). It also listens on that interface for similar messages from other firewalls, and imports them into the local state table. checkbox - - Synchronize IP Address - pfsyncip - PFSync IP Address - input - Synchronize Interface pfsyncinterface interfaces_selection - If Synchronize State is enabled, it will utilize this interface for communication. NOTE! You must define a IP on each machin participating in this failver group. + If Synchronize State is enabled, it will utilize this interface for communication. NOTE! You must define a IP on each machin participating in this failver group. NOTE: You must have an IP assigned to the interface on any participating sync nodes. Load Balancing -- cgit v1.2.3