summaryrefslogtreecommitdiffstats
path: root/usr/local/pkg
diff options
context:
space:
mode:
authorChris Buechler <cmb@pfsense.org>2008-02-14 02:31:20 +0000
committerChris Buechler <cmb@pfsense.org>2008-02-14 02:31:20 +0000
commit4762e200708461a53a36df317b43eb935d979057 (patch)
treefa8719553e82cf0a168f1fb492afcc0ea3a7a050 /usr/local/pkg
parent27e45e65e5f51f2e23aced42983d2d97941eb588 (diff)
downloadpfsense-4762e200708461a53a36df317b43eb935d979057.zip
pfsense-4762e200708461a53a36df317b43eb935d979057.tar.gz
touch up text
Ticket #1644
Diffstat (limited to 'usr/local/pkg')
-rw-r--r--usr/local/pkg/carp_settings.xml34
1 files changed, 17 insertions, 17 deletions
diff --git a/usr/local/pkg/carp_settings.xml b/usr/local/pkg/carp_settings.xml
index 6505d83..ed61630 100644
--- a/usr/local/pkg/carp_settings.xml
+++ b/usr/local/pkg/carp_settings.xml
@@ -10,7 +10,7 @@
<!-- Menu is where this packages menu will appear -->
<menu>
<name>CARP (failover)</name>
- <tooltiptext>CARP is a tool to help achieve system redundancy, by having multiple computers creating a single, virtual network interface between them, so that if any machine fails, another can respond instead, and/or allowing a degree of load sharing between systems. CARP is an improvement over the Virtual Router Redundancy Protocol (VRRP) standard. It was developed after VRRP was deemed to be not free enough because of a possibly-overlapping Cisco patent.</tooltiptext>
+ <tooltiptext>CARP is a tool to help achieve system redundancy, by having multiple computers creating a single, virtual network interface between them, so that if any machine fails, another can respond instead. CARP is an improvement over the Virtual Router Redundancy Protocol (VRRP) standard. It was developed after VRRP was deemed to be not free enough because of a possibly-overlapping Cisco patent.</tooltiptext>
<section>Firewall</section>
<configfile>carp_settings.xml</configfile>
</menu>
@@ -73,37 +73,37 @@
<fieldname>pfsyncpeerip</fieldname>
<type>input</type>
<description>
- Setting this option will force pfSync to synchronize its stable tables to this IP address. The default is directed multicast.
+ Setting this option will force pfsync to synchronize its stable table to this IP address. The default is directed multicast.
</description>
</field>
<field>
<fielddescr>Synchronize rules</fielddescr>
<fieldname>synchronizerules</fieldname>
- <description>When this option is enabled, this system will automatically sync the firewalls rules over to the other carp when changes are made..</description>
+ <description>When this option is enabled, this system will automatically sync the firewall rules to the other CARP host when changes are made..</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize Firewall Schedules</fielddescr>
<fieldname>synchronizeschedules</fieldname>
- <description>When this option is enabled, this system will automatically sync the firewall schedules over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the firewall schedules to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize aliases</fielddescr>
<fieldname>synchronizealiases</fieldname>
- <description>When this option is enabled, this system will automatically sync the aliases over to the other carp when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the aliases over to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize nat</fielddescr>
<fieldname>synchronizenat</fieldname>
- <description>When this option is enabled, this system will automatically sync the nat rules over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the NAT rules over to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
- <fielddescr>Synchronize ipsec</fielddescr>
+ <fielddescr>Synchronize IPsec</fielddescr>
<fieldname>synchronizeipsec</fieldname>
- <description>When this option is enabled, this system will automatically sync the ipsec rules over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the IPsec configuration to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<!--
@@ -115,47 +115,47 @@
</field>
-->
<field>
- <fielddescr>Synchronize Wake on Lan</fielddescr>
+ <fielddescr>Synchronize Wake on LAN</fielddescr>
<fieldname>synchronizewol</fieldname>
- <description>When this option is enabled, this system will automatically sync the WOL settings over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the WoL configuration to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize Static Routes</fielddescr>
<fieldname>synchronizestaticroutes</fieldname>
- <description>When this option is enabled, this system will automatically sync the Static Route settings over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the Static Route configuration to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize Load Balancer</fielddescr>
<fieldname>synchronizelb</fieldname>
- <description>When this option is enabled, this system will automatically sync the Load Balancer settings over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the Load Balancer configuration to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize Virtual IPs</fielddescr>
<fieldname>synchronizevirtualip</fieldname>
- <description>When this option is enabled, this system will automatically sync the Virtual IP (minus proxyarp) settings over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the CARP Virtual IPs to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize traffic shaper</fielddescr>
<fieldname>synchronizetrafficshaper</fieldname>
- <description>When this option is enabled, this system will automatically sync the traffic shaper rules over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the traffic shaper configuration to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize DNS Forwarder</fielddescr>
<fieldname>synchronizednsforwarder</fieldname>
- <description>When this option is enabled, this system will automatically sync the DNS Forwarder hosts/domains over to the other carp host when changes are made.</description>
+ <description>When this option is enabled, this system will automatically sync the DNS Forwarder configuration to the other CARP host when changes are made.</description>
<type>checkbox</type>
</field>
<field>
<fielddescr>Synchronize to IP</fielddescr>
<fieldname>synchronizetoip</fieldname>
- <description>Enter the IP address of the firewall you would like to synchronize your rules to.</description>
+ <description>Enter the IP address of the firewall you are synchronizing with.</description>
<type>input</type>
- <note>Note: CARP sync is currently only supported over http connections - make sure the remote system's WebGUI protocol is set to this! Also note that you will not use the Synchronize to IP and password option on backup cluster members!</note>
+ <note>Note: CARP sync is currently only supported over connections using the same protocol and port as this system - make sure the remote system's port and protocol are set accordingly! Also note that you will not use the Synchronize to IP and password option on backup cluster members!</note>
</field>
<field>
<fielddescr>Remote System Password</fielddescr>
OpenPOWER on IntegriCloud