<br/><?=gettext("When the number of state entries exceeds this value, adaptive scaling begins. All timeout values are scaled linearly with factor (adaptive.end - number of states) / (adaptive.end - adaptive.start).");?>
<br/><?=gettext("When reaching this number of state entries, all timeout values become zero, effectively purging all state entries immediately. This value is used to define the scale factor, it should not actually be reached (set a lower state limit, see below).");?>
<br/>
<spanclass="vexpl"><?=gettext("Note: Leave this blank for the default(0).");?></span>
<strong><?=gettext("start");?></strong></br>
<?=gettext("When the number of state entries exceeds this value, adaptive scaling begins. All timeout values are scaled linearly with factor (adaptive.end - number of states) / (adaptive.end - adaptive.start).");?><br/>
<strong><?=gettext("end");?></strong></br>
<?=gettext("When reaching this number of state entries, all timeout values become zero, effectively purging all state entries immediately. This value is used to define the scale factor, it should not actually be reached (set a lower state limit, see below).");?>
<br/>
<strong><?=gettext("Note: Leave this blank for the default(0).");?></strong>
</div>
</td>
</tr>
<tr>
<tdwidth="22%"valign="top"class="vncell"><?=gettext("Firewall Maximum States");?></td>
<strong><?=gettext("Maximum number of connections to hold in the firewall state table.");?></strong>
<br/>
<spanclass="vexpl"><?=gettext("Note: Leave this blank for the default. On your system the default size is:");?><?=default_state_size()?></span>
<?=gettext("Note: Leave this blank for the default. On your system the default size is:");?><?=default_state_size()?>
</div>
</td>
</tr>
<tr>
<tdwidth="22%"valign="top"class="vncell"><?=gettext("Firewall Maximum Table Entries");?></td>
<tdwidth="78%"class="vtable">
<td><aid="help_for_maximumtableentries"href="#"class="showhelp"><iclass="fa fa-info-circle"></i></a><?=gettext("Firewall Maximum Table Entries");?></td>
<strong><?=gettext("Disable reply-to on WAN rules");?></strong>
<br/>
<?=gettext("With Multi-WAN you generally want to ensure traffic leaves the same interface it arrives on, hence reply-to is added automatically by default. ".
"When using bridging, you must disable this behavior if the WAN gateway IP is different from the gateway IP of the hosts behind the bridged interface.");?>
<strong><?=gettext("Disable Negate rule on policy routing rules");?></strong>
<br/>
<?=gettext("With Multi-WAN you generally want to ensure traffic reaches directly connected networks and VPN networks when using policy routing. You can disable this for special purposes but it requires manually creating rules for these networks");?>
<strong><?=gettext("When enabled, this automatically creates additional NAT redirect rules for access to port forwards on your external IP addresses from within your internal networks.");?></strong>
<br/><br/>
<?=gettext("The NAT + proxy mode uses a helper program to send packets to the target of the port forward. It is useful in setups where the interface and/or gateway IP used for communication with the target cannot be accurately determined at the time the rules are loaded. Reflection rules are not created for ranges larger than 500 ports and will not be used for more than 1000 ports total between all port forwards. Only TCP and UDP protocols are supported.");?>
...
...
@@ -548,62 +534,64 @@ endif; ?>
<?=gettext("The pure NAT mode uses a set of NAT rules to direct packets to the target of the port forward. It has better scalability, but it must be possible to accurately determine the interface and gateway IP used for communication with the target at the time the rules are loaded. There are no inherent limits to the number of ports other than the limits of the protocols. All protocols available for port forwards are supported.");?>
<br/><br/>
<?=gettext("Individual rules may be configured to override this system setting on a per-rule basis.");?>
<strong><?=gettext("Enables the automatic creation of additional NAT redirect rules for access to 1:1 mappings of your external IP addresses from within your internal networks.");?></strong>
<br/><br/>
<?=gettext("Note: Reflection on 1:1 mappings is only for the inbound component of the 1:1 mappings. This functions the same as the pure NAT mode for port forwards. For more details, refer to the pure NAT mode description above.");?>
<br/><br/>
<?=gettext("Individual rules may be configured to override this system setting on a per-rule basis.");?>
</div>
</td>
</tr>
<tr>
<tdwidth="22%"valign="top"class="vncell"><?=gettext("Enable automatic outbound NAT for Reflection");?></td>
<strong><?=gettext("Automatically create outbound NAT rules which assist inbound NAT rules that direct traffic back out to the same subnet it originated from.");?></strong>
<br/>
<?=gettext("Required for full functionality of the pure NAT mode of NAT Reflection for port forwards or NAT Reflection for 1:1 NAT.");?>
<br/><br/>
<?=gettext("Note: This only works for assigned interfaces. Other interfaces require manually creating the outbound NAT rules that direct the reply packets back through the router.");?>