<commit_before><?xml version="1.0" encoding="utf-8" ?>
<packagegui>
	<name>carpsettings</name>
	<version>0.1.0</version>
	<title>Services: CARP Settings</title>
	<configpath>['installedpackages']['carpsettings']['config']</configpath>
	<aftersaveredirect>pkg_edit.php?xml=carp_settings.xml&amp;id=0</aftersaveredirect>
	<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. 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>
	<tabs>
		<tab>
			<text>Virtual IPs</text>
			<url>firewall_virtual_ip.php</url>
		</tab>
		<tab>
			<text>CARP Settings</text>
			<url>pkg_edit.php?xml=carp_settings.xml&amp;id=0</url>
			<active/>
		</tab>
	</tabs>
	<adddeleteeditpagefields>
		<columnitem>
			<fielddescr>PFSync Enabled</fielddescr>
			<fieldname>pfsyncenabled</fieldname>
		</columnitem>
		<columnitem>
			<fielddescr>PFSync IP</fielddescr>
			<fieldname>pfsyncip</fieldname>
		</columnitem>
		<columnitem>
			<fielddescr>PFSync Interface</fielddescr>
			<fieldname>pfsyncinterface</fieldname>
		</columnitem>
	</adddeleteeditpagefields>
	<fields>
		<field>
			<name>State Synchronization Settings (pfsync)</name>
			<type>listtopic</type>
		</field>
		<field>
			<fielddescr>Synchronize States</fielddescr>
			<fieldname>pfsyncenabled</fieldname>
			<description>
				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.
				&lt;p&gt;
				This setting should be enabled on all members of a failover group.
				&lt;p&gt;
				NOTE: Clicking save will force a configuration sync if it is enabled! (see Configuration Synchronization Settings below)
			</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize Interface</fielddescr>
			<fieldname>pfsyncinterface</fieldname>
			<type>interfaces_selection</type>
			<description>
				If Synchronize States is enabled, it will utilize this interface for communication.
				&lt;br&gt;&lt;b&gt;NOTE:&lt;/b&gt;  We recommend setting this to a interface other than LAN!  A dedicated interface works the best.
				&lt;br&gt;&lt;b&gt;NOTE:&lt;/b&gt;  You must define a IP on each machine participating in this failover group.
				&lt;br&gt;&lt;b&gt;NOTE:&lt;/b&gt;  You must have an IP assigned to the interface on any participating sync nodes.
			</description>
		</field>
		<field>
			<fielddescr>pfsync Synchronize Peer IP</fielddescr>
			<fieldname>pfsyncpeerip</fieldname>
			<type>input</type>
			<description>
				Setting this option will force pfsync to synchronize its state table to this IP address.  The default is directed multicast.
			</description>
		</field>
		<field>
			<name>Configuration Synchronization Settings (XMLRPC Sync)</name>
			<type>listtopic</type>
		</field>
		<field>
			<fielddescr>Synchronize Config to IP</fielddescr>
			<fieldname>synchronizetoip</fieldname>
			<description>Enter the IP address of the firewall to which the selected configuration sections should be synchronized.
			&lt;br&gt;&lt;br&gt;NOTE: XMLRPC 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!
			&lt;br&gt;&lt;br&gt;NOTE: &lt;b&gt;Do not use the Synchronize Config to IP and password option on backup cluster members!&lt;/b&gt;
			</description>
			<type>input</type>
		</field>
		<field>
			<fielddescr>Remote System Password</fielddescr>
			<fieldname>password</fieldname>
			<description>Enter the webConfigurator password of the system entered above for synchronizing your configuration.
			&lt;br&gt;&lt;br&gt;NOTE: &lt;b&gt;Do not use the Synchronize Config to IP and password option on backup cluster members!&lt;/b&gt;</description>
			<type>password</type>
		</field>
		<field>
			<fielddescr>Synchronize Users and Groups</fielddescr>
			<fieldname>synchronizeusers</fieldname>
			<description>When this option is enabled, this system will automatically sync the users and groups over to the other CARP host when changes are made.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize rules</fielddescr>
			<fieldname>synchronizerules</fieldname>
			<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 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 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>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize IPsec</fielddescr>
			<fieldname>synchronizeipsec</fieldname>
			<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>
		<field>
			<fielddescr>Synchronize OpenVPN</fielddescr>
			<fieldname>synchronizeopenvpn</fieldname>
			<description>When this option is enabled, this system will automatically sync the OpenVPN configuration to the other CARP host when changes are made.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize DHCPD</fielddescr>
			<fieldname>synchronizedhcpd</fieldname>
			<description>When this option is enabled, this system will automatically sync the DHCP Server settings over to the other carp host when changes are made.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize Wake on LAN</fielddescr>
			<fieldname>synchronizewol</fieldname>
			<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 configuration to the other CARP host when changes are made.</description>
			<type>checkbox</type>
		</field><commit_msg>Add GUI option to CARP settings for syncing certs. It was in the backend code but not the GUI. Fixes #1316<commit_after><?xml version="1.0" encoding="utf-8" ?>
<packagegui>
	<name>carpsettings</name>
	<version>0.1.0</version>
	<title>Services: CARP Settings</title>
	<configpath>['installedpackages']['carpsettings']['config']</configpath>
	<aftersaveredirect>pkg_edit.php?xml=carp_settings.xml&amp;id=0</aftersaveredirect>
	<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. 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>
	<tabs>
		<tab>
			<text>Virtual IPs</text>
			<url>firewall_virtual_ip.php</url>
		</tab>
		<tab>
			<text>CARP Settings</text>
			<url>pkg_edit.php?xml=carp_settings.xml&amp;id=0</url>
			<active/>
		</tab>
	</tabs>
	<adddeleteeditpagefields>
		<columnitem>
			<fielddescr>PFSync Enabled</fielddescr>
			<fieldname>pfsyncenabled</fieldname>
		</columnitem>
		<columnitem>
			<fielddescr>PFSync IP</fielddescr>
			<fieldname>pfsyncip</fieldname>
		</columnitem>
		<columnitem>
			<fielddescr>PFSync Interface</fielddescr>
			<fieldname>pfsyncinterface</fieldname>
		</columnitem>
	</adddeleteeditpagefields>
	<fields>
		<field>
			<name>State Synchronization Settings (pfsync)</name>
			<type>listtopic</type>
		</field>
		<field>
			<fielddescr>Synchronize States</fielddescr>
			<fieldname>pfsyncenabled</fieldname>
			<description>
				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.
				&lt;p&gt;
				This setting should be enabled on all members of a failover group.
				&lt;p&gt;
				NOTE: Clicking save will force a configuration sync if it is enabled! (see Configuration Synchronization Settings below)
			</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize Interface</fielddescr>
			<fieldname>pfsyncinterface</fieldname>
			<type>interfaces_selection</type>
			<description>
				If Synchronize States is enabled, it will utilize this interface for communication.
				&lt;br&gt;&lt;b&gt;NOTE:&lt;/b&gt;  We recommend setting this to a interface other than LAN!  A dedicated interface works the best.
				&lt;br&gt;&lt;b&gt;NOTE:&lt;/b&gt;  You must define a IP on each machine participating in this failover group.
				&lt;br&gt;&lt;b&gt;NOTE:&lt;/b&gt;  You must have an IP assigned to the interface on any participating sync nodes.
			</description>
		</field>
		<field>
			<fielddescr>pfsync Synchronize Peer IP</fielddescr>
			<fieldname>pfsyncpeerip</fieldname>
			<type>input</type>
			<description>
				Setting this option will force pfsync to synchronize its state table to this IP address.  The default is directed multicast.
			</description>
		</field>
		<field>
			<name>Configuration Synchronization Settings (XMLRPC Sync)</name>
			<type>listtopic</type>
		</field>
		<field>
			<fielddescr>Synchronize Config to IP</fielddescr>
			<fieldname>synchronizetoip</fieldname>
			<description>Enter the IP address of the firewall to which the selected configuration sections should be synchronized.
			&lt;br&gt;&lt;br&gt;NOTE: XMLRPC 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!
			&lt;br&gt;&lt;br&gt;NOTE: &lt;b&gt;Do not use the Synchronize Config to IP and password option on backup cluster members!&lt;/b&gt;
			</description>
			<type>input</type>
		</field>
		<field>
			<fielddescr>Remote System Password</fielddescr>
			<fieldname>password</fieldname>
			<description>Enter the webConfigurator password of the system entered above for synchronizing your configuration.
			&lt;br&gt;&lt;br&gt;NOTE: &lt;b&gt;Do not use the Synchronize Config to IP and password option on backup cluster members!&lt;/b&gt;</description>
			<type>password</type>
		</field>
		<field>
			<fielddescr>Synchronize Users and Groups</fielddescr>
			<fieldname>synchronizeusers</fieldname>
			<description>When this option is enabled, this system will automatically sync the users and groups over to the other CARP host when changes are made.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize Certificates</fielddescr>
			<fieldname>synchronizecerts</fieldname>
			<description>When this option is enabled, this system will automatically sync the Certificate Authorities, Certificates, and Certificate Revocation Lists over to the other CARP host when changes are made.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize rules</fielddescr>
			<fieldname>synchronizerules</fieldname>
			<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 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 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>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize IPsec</fielddescr>
			<fieldname>synchronizeipsec</fieldname>
			<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>
		<field>
			<fielddescr>Synchronize OpenVPN</fielddescr>
			<fieldname>synchronizeopenvpn</fieldname>
			<description>When this option is enabled, this system will automatically sync the OpenVPN configuration to the other CARP host when changes are made. Using this option implies "Synchronize Certificates" as they are required for OpenVPN.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize DHCPD</fielddescr>
			<fieldname>synchronizedhcpd</fieldname>
			<description>When this option is enabled, this system will automatically sync the DHCP Server settings over to the other carp host when changes are made.</description>
			<type>checkbox</type>
		</field>
		<field>
			<fielddescr>Synchronize Wake on LAN</fielddescr>
			<fieldname>synchronizewol</fieldname>
			<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 configuration to the other CARP host when changes are made.</description>
			<type>checkbox</type>
		</field>
{'fraction_non_alphanumeric': 0.09998703991705547, 'fraction_numerical': 0.00168481078278901, 'mean_word_length': 4.917561349693251, 'pattern_counts': {'":': 0, '<': 453, '<?xml version=': 2, '>': 453, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 12}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5877497', 'n_tokens_mistral': 5181, 'n_tokens_neox': 4569, 'n_words': 1477}