Changes

no edit summary
Line 1: Line 1:  +
{{Template: Networking_rutxxx_manual_fw_disclosure
 +
| fw_version = {{{series}}}_R_00.06.08.2
 +
| series    = {{{series}}}
 +
}}
 
==Summary==
 
==Summary==
   Line 27: Line 31:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Protocol</td>
 
       <td>Protocol</td>
       <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td>
+
       <td>Static {{!}} DHCP {{!}} PPPoE; default: '''DHCP'''</td>
 
       <td>The protocol used by the WAN interface</td>
 
       <td>The protocol used by the WAN interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>IPv4 address</td>
 
       <td>IPv4 address</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>Your router’s address on the WAN network</td>
 
       <td>Your router’s address on the WAN network</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>IPv4 netmask</td>
 
     <td>IPv4 netmask</td>
         <td>ip; Default: '''255.255.255.0'''</td>
+
         <td>ip; default: '''255.255.255.0'''</td>
 
         <td>Netmask defines how "large" a network is</td>
 
         <td>Netmask defines how "large" a network is</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>IPv4 gateway</td>
 
     <td>IPv4 gateway</td>
         <td>ip; Default: " "</td>
+
         <td>ip; default: <b>none</b></td>
 
         <td>The address where the router will send all the outgoing traffic</td>
 
         <td>The address where the router will send all the outgoing traffic</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>IPv4 broadcast</td>
 
     <td>IPv4 broadcast</td>
         <td>ip; Default: " "</td>
+
         <td>ip; default: <b>none</b></td>
 
         <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
 
         <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Use custom DNS servers</td>
 
     <td>Use custom DNS servers</td>
         <td>ip; Default: " "</td>
+
         <td>ip; default: <b>none</b></td>
 
         <td>When the router needs to resolve a hostname (“www.google.com”, “www.cnn.com”, etc.) to an IP address, it will forward all the DNS requests to the gateway. By entering custom DNS servers the router will take care of the host name resolution. You can enter multiple DNS servers to provide redundancy in case one of the servers fails</td>
 
         <td>When the router needs to resolve a hostname (“www.google.com”, “www.cnn.com”, etc.) to an IP address, it will forward all the DNS requests to the gateway. By entering custom DNS servers the router will take care of the host name resolution. You can enter multiple DNS servers to provide redundancy in case one of the servers fails</td>
 
     </tr>
 
     </tr>
Line 71: Line 75:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Disable NAT</td>
 
       <td>Disable NAT</td>
       <td>yes {{!}} no; Default: '''no'''</td>
+
       <td>yes {{!}} no; default: '''no'''</td>
 
       <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
 
       <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Override MAC address</td>
 
       <td>Override MAC address</td>
       <td>mac; Default: '''router's mac'''</td>
+
       <td>mac; default: '''router's mac'''</td>
 
       <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer</td>
 
       <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Override MTU</td>
 
     <td>Override MTU</td>
         <td>integer [0..1500]; Default: '''1500'''</td>
+
         <td>integer [0..1500]; default: '''1500'''</td>
 
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td>
 
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Use gateway metric</td>
 
     <td>Use gateway metric</td>
         <td>integer; Default: '''0'''</td>
+
         <td>integer; default: '''0'''</td>
 
         <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
 
         <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
 
     </tr>
 
     </tr>
Line 108: Line 112:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Protocol</td>
 
       <td>Protocol</td>
       <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td>
+
       <td>Static {{!}} DHCP {{!}} PPPoE; default: '''DHCP'''</td>
 
       <td>The protocol used by the WAN interface</td>
 
       <td>The protocol used by the WAN interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Hostname to send when requesting DHCP</td>
 
       <td>Hostname to send when requesting DHCP</td>
       <td>ip {{!}} hostname; Default: '''router's hostname'''</td>
+
       <td>ip {{!}} hostname; default: '''router's hostname'''</td>
 
       <td>Host name to which the DHCP request will be sent to</td>
 
       <td>Host name to which the DHCP request will be sent to</td>
 
     </tr>
 
     </tr>
Line 132: Line 136:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Disable NAT</td>
 
       <td>Disable NAT</td>
       <td>yes {{!}} no; Default: '''no'''</td>
+
       <td>yes {{!}} no; default: '''no'''</td>
 
       <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
 
       <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Use broadcast flag</td>
 
       <td>Use broadcast flag</td>
       <td>yes {{!}} no; Default: '''no''' </td>
+
       <td>yes {{!}} no; default: '''no''' </td>
 
       <td>Required for certain ISPs (Internet Service Providers), e.g. Charter with DOCSIS 3</td>
 
       <td>Required for certain ISPs (Internet Service Providers), e.g. Charter with DOCSIS 3</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Use default gateway</td>
 
     <td>Use default gateway</td>
         <td>yes {{!}} no; Default: '''yes'''</td>
+
         <td>yes {{!}} no; default: '''yes'''</td>
 
         <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td>
 
         <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Use DNS servers advertised by peer</td>
 
     <td>Use DNS servers advertised by peer</td>
         <td>yes {{!}} no; Default: '''no'''</td>
+
         <td>yes {{!}} no; default: '''yes'''</td>
 
         <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td>
 
         <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Use custom DNS servers</td>
 
       <td>Use custom DNS servers</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td>
 
       <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Use gateway metric</td>
 
       <td>Use gateway metric</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority </td>
 
       <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Client ID to send when requesting DHCP</td>
 
     <td>Client ID to send when requesting DHCP</td>
         <td>string; Default: " "</td>
+
         <td>string; default: <b>none</b></td>
 
         <td>Client ID which will be sent when requesting a DHCP lease</td>
 
         <td>Client ID which will be sent when requesting a DHCP lease</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Vendor class to send when requesting DHCP</td>
 
     <td>Vendor class to send when requesting DHCP</td>
         <td>string; Default: " "</td>
+
         <td>string; default: <b>none</b></td>
 
         <td>Vendor class which will be sent when requesting a DHCP lease</td>
 
         <td>Vendor class which will be sent when requesting a DHCP lease</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Override MAC address</td>
 
     <td>Override MAC address</td>
         <td>mac; Default: '''router's mac'''</td>
+
         <td>mac; default: '''router's mac'''</td>
 
         <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer</td>
 
         <td>Override MAC address of the WAN interface. For example, your ISP (Internet Service Provider) gives you a static IP address and it might also bind it to your computers MAC address (i.e., that IP will only work with your computer but not with your router). In this field you can enter your computer’s MAC address and fool the gateway in to thinking that it is communicating with your computer</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Override MTU</td>
 
     <td>Override MTU</td>
         <td>integer [0..1500]; Default: '''1500'''</td>
+
         <td>integer [0..1500]; default: '''1500'''</td>
 
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td>
 
         <td>Maximum Transmission Unit (MTU) – specifies the largest possible size of a data packet</td>
 
     </tr>
 
     </tr>
Line 200: Line 204:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Protocol</td>
 
       <td>Protocol</td>
       <td>Static {{!}} DHCP {{!}} PPPoE; Default: '''DHCP'''</td>
+
       <td>Static {{!}} DHCP {{!}} PPPoE; default: '''DHCP'''</td>
 
       <td>The protocol used by the WAN interface</td>
 
       <td>The protocol used by the WAN interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>PAP/CHAP username</td>
 
       <td>PAP/CHAP username</td>
       <td>string; Default: " "</td>
+
       <td>string; default: <b>none</b></td>
 
       <td>The username that you use to connect to your carrier’s network </td>
 
       <td>The username that you use to connect to your carrier’s network </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>PAP/CHAP password</td>
 
     <td>PAP/CHAP password</td>
         <td>string; Default: " "</td>
+
         <td>string; default: <b>none</b></td>
 
         <td>The password that you use to connect to your carrier’s network </td>
 
         <td>The password that you use to connect to your carrier’s network </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Access concentrator</td>
 
     <td>Access concentrator</td>
         <td>string; Default: " "</td>
+
         <td>string; default: <b>none</b></td>
 
         <td>The name of the access concentrator. Leave empty to auto detect</td>
 
         <td>The name of the access concentrator. Leave empty to auto detect</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Service name</td>
 
     <td>Service name</td>
         <td>string; Default: " "</td>
+
         <td>string; default: <b>none</b></td>
 
         <td>The name of the service. Leave empty to auto detect</td>
 
         <td>The name of the service. Leave empty to auto detect</td>
 
     </tr>
 
     </tr>
Line 239: Line 243:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Disable NAT</td>
 
       <td>Disable NAT</td>
       <td>yes {{!}} no; Default: '''no'''</td>
+
       <td>yes {{!}} no; default: '''no'''</td>
 
       <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
 
       <td>Toggles Network Address Translation (NAT) on or off for the selected network interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Use default gateway</td>
 
       <td>Use default gateway</td>
       <td>yes {{!}} no; Default: '''yes'''</td>
+
       <td>yes {{!}} no; default: '''yes'''</td>
 
       <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td>
 
       <td>Uses the default gateway obtained through DHCP. If left unchecked, no default route is configured</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Use gateway metric</td>
 
     <td>Use gateway metric</td>
         <td>integer; Default: '''0'''</td>
+
         <td>integer; default: '''0'''</td>
 
         <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
 
         <td>The WAN configuration by default generates a routing table entry. In this field you can alter the metric of that entry. Higher metric means higher priority</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Use DNS servers advertised by peer</td>
 
     <td>Use DNS servers advertised by peer</td>
         <td>yes {{!}} no; Default: '''yes'''</td>
+
         <td>yes {{!}} no; default: '''yes'''</td>
 
         <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td>
 
         <td>Uses DNS servers obtained from DHCP. If left unchecked, the advertised DNS server addresses are ignored</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Use custom DNS servers</td>
 
       <td>Use custom DNS servers</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td>
 
       <td>Lets you chose your own preferred DNS servers. This field only becomes visible if '''Use DNS servers advertised by peer''' field is unchecked</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>LCP echo failure threshold</td>
 
       <td>LCP echo failure threshold</td>
       <td>integer; Default: '''0'''</td>
+
       <td>integer; default: '''0'''</td>
 
       <td>Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures</td>
 
       <td>Presumes peer to be dead after given amount of LCP echo failures. Leave it at 0 to ignore failures</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>LCP echo interval</td>
 
     <td>LCP echo interval</td>
         <td>integer; Default: '''5'''</td>
+
         <td>integer; default: '''5'''</td>
 
         <td>Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold</td>
 
         <td>Sends LCP echo requests at the given interval in seconds. This function is only effective in conjunction with failure threshold</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Inactivity timeout</td>
 
     <td>Inactivity timeout</td>
         <td>integer; Default: '''0'''</td>
+
         <td>integer; default: '''0'''</td>
 
         <td>Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection</td>
 
         <td>Close inactive connection after the given amount of seconds. Leave it at 0 to persist connection</td>
 
     </tr>
 
     </tr>
Line 295: Line 299:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>IP address</td>
 
       <td>IP address</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>An alternate IP address used to reach the router by a device(s) that resides in the router's LAN but has a different subnet</td>
 
       <td>An alternate IP address used to reach the router by a device(s) that resides in the router's LAN but has a different subnet</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Netmask</td>
 
       <td>Netmask</td>
       <td>ip; Default: '''255.255.255.0'''</td>
+
       <td>ip; default: '''255.255.255.0'''</td>
 
       <td>Netmask defines how "large" a network is</td>
 
       <td>Netmask defines how "large" a network is</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Gateway</td>
 
     <td>Gateway</td>
         <td>ip; Default: " "</td>
+
         <td>ip; default: <b>none</b></td>
 
         <td>A gateway is a network node that connects two networks using different protocols together</td>
 
         <td>A gateway is a network node that connects two networks using different protocols together</td>
 
     </tr>
 
     </tr>
Line 327: Line 331:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>IP Broadcast</td>
 
       <td>IP Broadcast</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
 
       <td>IP broadcasts are used by BOOTP and DHCP clients to find and send requests to their respective servers</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>DNS</td>
 
       <td>DNS</td>
       <td>ip; Default: " "</td>
+
       <td>ip; default: <b>none</b></td>
 
       <td>A separate DNS server to be used by the IP Alias address</td>
 
       <td>A separate DNS server to be used by the IP Alias address</td>
 
     </tr>
 
     </tr>
Line 351: Line 355:  
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Health monitor interval</td>
 
       <td>Health monitor interval</td>
       <td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; Default: '''10 sec.'''</td>
+
       <td>Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; default: <b>5 sec.</b></td>
       <td>The interval at which health checks are performed</td>
+
       <td>The interval at which health checks are performed.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Health monitor ICMP host(s)</td>
 
       <td>Health monitor ICMP host(s)</td>
       <td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; Default: '''8.8.4.4'''</td>
+
       <td>ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; default: <b>8.8.8.8</b></td>
       <td>Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)</td>
+
       <td>Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Health monitor ICMP timeout</td>
 
     <td>Health monitor ICMP timeout</td>
         <td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; Default: '''3 sec.'''</td>
+
         <td>1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; default: <b>1 sec.</b></td>
         <td>The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes)</td>
+
         <td>The frequency at which ICMP requests will be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes).</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Attempts before failover</td>
 
     <td>Attempts before failover</td>
         <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''</td>
+
         <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td>
         <td>The number of failed ping attempts after which the connection is to be declared as “'''down'''” </td>
+
         <td>The number of failed ping attempts before the connection is to be declared as "down". </td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Attempts before recovery</td>
 
     <td>Attempts before recovery</td>
         <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''</td>
+
         <td>1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; default: <b>3</b></td>
         <td>The number of successful ping attempts after which the connection is to be declared as “'''up'''”</td>
+
         <td>The number of successful ping attempts before the connection is to be declared as "up".</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Execute command</td>
 +
        <td>yes {{!}} no; default: <b>no</b></td>
 +
        <td>Executes a user specified command when the WAN fails over to this interface.</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Command</td>
 +
        <td>string; default: <b>none</b></td>
 +
        <td>A command that will executed when the WAN fails over to this interface.</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
Line 384: Line 398:  
<b>Additional notes</b>:
 
<b>Additional notes</b>:
 
<ul>
 
<ul>
<li>Failover configuration field's default values may differ based on WAN type.</li>
+
    <li>Failover configuration field's default values may differ based on WAN type.</li>
 +
    <li>The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down.</li>
 
</ul>
 
</ul>
   −
<ul>
+
==UDP Broadcast Relay==
    <li>
+
 
The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down.
+
The <b>UDP Broadcast Relay</b> will listen for broadcast traffic on the specified port and relay that traffic to the specified interface(s).
     </li>
+
 
</ul>
+
[[File:Networking_rut_manual_wan_udp_broadcast_relay.png|border|class=tlt-border]]
 +
 
 +
<table class="nd-mantable">
 +
    <tr>
 +
        <th>Field</th>
 +
      <th>Value</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td>Enable</td>
 +
      <td>on | off; default: <b>off</b></td>
 +
      <td>Turns UDP Broadcast Relay on or off.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Port</td>
 +
      <td>integer [0..65535]; default: <b>none</b></td>
 +
      <td>UDP port to listen for broadcast traffic.</td>
 +
    </tr>
 +
    <tr>
 +
      <td>Interfaces</td>
 +
      <td>network interface(s); default: <b>none</b></td>
 +
      <td>The interface(s) to which the traffic will be redirected to.</td>
 +
     </tr>
 +
</table>
 +
 
 +
[[Category:{{{name}}} Network section]]

Navigation menu