440
edits
Changes
Template:Networking rutos manual failover (view source)
Revision as of 16:31, 16 January 2024
, 16 Januaryno edit summary
{{Template:Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.05
| series = {{{series}}}
| series = {{{series}}}
| name = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
__TOC__
__TOC__
==Summary==
==Summary==
This chapter is an overview of the Failover and Load Balancing functions in {{{name}}} device.
This chapter is an overview of the Failover, VRRP functions in {{{name}}} device.
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
}}
}}
{{#switch: {{{series}}}
{{#ifeq: {{{name}}} | RUTX08 | <b><span style="color: red;">Attention:</span></b> if you're using a <b>{{{name}}} device</b>, the only way to see the Failover page is to configure at least one LAN port to act as WAN. This can be done from the Network → [[{{{name}}} Interface|Interfaces]] page.<br>
| #default =
----|}}
| TRB2 | TRB2M | OTD140 =
<u><b>
Note:</b> Failover is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
===Multiwan===
----
The <b>Failover</b> function allows you to backup your primary WAN connection in case it goes down.
The <b>Failover</b> function allows you to backup your primary WAN connection in case it goes down.
In order to set priorities, simply press left mouse click on the interface, then drag it to the 1st, 2nd or other position and then press Save & Apply.
In order to set priorities, simply press left mouse click on the interface bellow `Mode` section, then drag it to the 1st, 2nd or other position and then press Save & Apply.{{#ifeq:{{{mobile}}}|0|<br><br><b>Note:</b> You will not see any extra interfaces unless you have LAN ports configured as WAN.|}}
[[File:Networking_rutos_manual_failover_failover_interfaces_mobile_{{{mobile}}}_wifi_{{{wifi}}}.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_failover_interfaces_mobile_{{{mobile}}}_{{{dualsim}}}_{{{dualmodem}}}.png|border|class=tlt-border]]
You can drag & drop an interface in order to change its position on the list. Interfaces that are higher on the list have a higher priority than the ones that are lower, i.e., the device will always use the WAN interface with the highest priority as long as it is available. If it goes down, the device will start using the interface with the second highest priority and so on.
You can drag & drop an interface in order to change its position on the list. Interfaces that are higher on the list have a higher priority than the ones that are lower, i.e., the device will always use the WAN interface with the highest priority as long as it is available. If it goes down, the device will start using the interface with the second highest priority and so on.
<ul>
<ul>
<li><i>Network → [[{{{name}}} WAN|WAN]]</i></li>
<li><i>Network → [[{{{name}}} WAN|WAN]]</i></li>
</ul>
</ul>
===Failover Interface Configuration===
====Failover Interface Configuration====
----
----
A failover <b>Interface Configuration</b> page is used to configure how the device will determine whether an interface is online or offline. To enter an interface configuration page, click the 'Edit' button next to an interface.
A failover <b>Interface Configuration</b> page is used to configure how the device will determine whether an interface is online or offline. To enter an interface configuration page, click the 'Edit' button next to an interface.
[[File:Networking_rutos_manual_failover_interface_configuration_edit_button.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_interface_configuration_edit_button_v2.png|border|class=tlt-border]]
After this you should be redirected to the configuration page of that interface.
After this you should be redirected to the configuration page of that interface.
[[File:Networking_rutos_manual_failover_interface_configuration.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_interface_configuration_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<table class="nd-mantable">
<tr>
<tr>
<td>Interval</td>
<td>Interval</td>
<td>integer; default: <b>3</b></td>
<td>integer [1..65000]; default: <b>3</b></td>
<td>Number of seconds between each test</td>
<td>Number of seconds between each test</td>
</tr>
</tr>
<tr>
<tr>
<td>Flush connections on</td>
<td>Flush connections on</td>
<td>Connected | Disconnected | none | both; default: <b>none</b></td>
<td>Connected | Disconnected: <b>none</b></td>
<td>Flushes established connections after the selected scenario occurs to renew the priorities of configured interfaces.</td>
<td>Flushes established connections after the selected scenario occurs to renew the priorities of configured interfaces.</td>
</tr>
</tr>
<tr>
<tr>
<td>Method</td>
<td>Method</td>
<td>Ping; default: <b>Ping</b></td>
<td>Ping | Wget; default: <b>Ping</b></td>
<td>Defines how health check will be performed on this interface when determining its state.</td>
<td>Defines how health check will be performed on this interface when determining its state.</td>
</tr>
</tr>
<tr>
<tr>
<td>Track IP</td>
<td>Track IP</td>
<td>ip | hostname; default: <b>8.8.4.4,8.8.8.8</b></td>
<td>ip | hostname; default: <b>1.1.1.1,8.8.8.8</b></td>
<td>IP address(es) or hostname(s) that will be used to determine an interface's state. If the device receives no response from any of the specified hosts, the interface will be considered as 'Offline'. If this value is missing the interface is always considered up.</td>
<td>IP address(es) or hostname(s) that will be used to determine an interface's state. If the device receives no response from any of the specified hosts, the interface will be considered as 'Offline'. If this value is missing the interface is always considered up.</td>
</tr>
</tr>
<tr>
<tr>
<td>Reliability</td>
<td>Reliability</td>
<td>integer; default: <b>1</b></td>
<td>integer [1..65000]; default: <b>1</b></td>
<td>Number of hosts that must reply for the test to be considered successful. Make sure there are at least this many hosts defined in the 'Track IP' field, otherwise the interface will always be considered as 'Offline'.</td>
<td>Number of hosts that must reply for the test to be considered successful. Make sure there are at least this many hosts defined in the 'Track IP' field, otherwise the interface will always be considered as 'Offline'.</td>
</tr>
</tr>
<tr>
<tr>
<td>Count</td>
<td>Count</td>
<td>integer; default: <b>1</b></td>
<td>integer [1..65000]; default: <b>1</b></td>
<td>Number of pings to send to each host with each test.</td>
<td>Number of pings to send to each host with each test.</td>
</tr>
</tr>
<tr>
<tr>
<td>Up</td>
<td>Up</td>
<td>integer; default: <b>3</b></td>
<td>integer [1..65000]; default: <b>3</b></td>
<td>Number of successful tests required to considered an interface as 'Online'.</td>
<td>Number of successful tests required to considered an interface as 'Online'.</td>
</tr>
</tr>
<tr>
<tr>
<td>Down</td>
<td>Down</td>
<td>integer; default: <b>3</b></td>
<td>integer [1..65000]; default: <b>3</b></td>
<td>Number of failed tests required to considered an interface as 'Offline'.</td>
<td>Number of failed tests required to considered an interface as 'Offline'.</td>
</tr>
</tr>
However, Load Balancing can be used to increase the speed of multiple connections. For example, when used in a WiFi network, Load Balancing would utilize the resources of multiple WAN interfaces to handle the many various requests of different clients.
However, Load Balancing can be used to increase the speed of multiple connections. For example, when used in a WiFi network, Load Balancing would utilize the resources of multiple WAN interfaces to handle the many various requests of different clients.
Both Load Balancing and Failover cannot be used at the same time. If you wish to select Load Balancing, you can do that in the dropdown located in the top-right corner of the page:
Both Load Balancing and Failover cannot be used at the same time. If you wish to select Load Balancing, you can do that in the dropdown located under 'Mode' section:
[[File:Networking_rutos_manual_failover_load_balancing_select.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_load_balancing_select_v1.png|border|class=tlt-border]]
Below is an example of the Load Balancing page.
Below is an example of the Load Balancing page.
[[File:Networking_rutos_manual_failover_load_balancing_interfaces_mobile_{{{mobile}}}_wifi_{{{wifi}}}.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_load_balancing_interfaces_v1.png|border|class=tlt-border]]
When Load Balancing is selected, you can <b>assign ratio values</b> to WAN interfaces. The ratio value represents a percentage of traffic load that will go through an interface. For example, if you set it up like this:
When Load Balancing is selected, you can <b>assign ratio values</b> to WAN interfaces. The ratio value represents a percentage of traffic load that will go through an interface. For example, if you set it up like this:
<table>
<table>
<tr>
<tr>
<td style="text-align: left; width: 150px;"><li><i>Wired WAN Ratio:</i></li></td>
<td style="text-align: left; width: 150px;"><ul><li><i>Wired WAN Ratio:</i></li></ul></td>
<td style="text-align: right; width: 30px;"><b>3</b>
<td style="text-align: right; width: 30px;"><b>3</b></td>
</tr>
</tr>
</table>
</table>
<table>
<table>
<tr>
<tr>
<td style="text-align: left; width: 150px;"><li><i>{{{wan2}}} Ratio:</i></li></td>
<td style="text-align: left; width: 150px;"><ul><li><i>{{{wan2}}} Ratio:</i></li></ul></td>
<td style="text-align: right; width: 30px;"><b>2</b></td>
<td style="text-align: right; width: 30px;"><b>2</b></td>
</tr>
</tr>
</table>
</table>
then about 60 % (3/5) of traffic would go through the Wired WAN interface and about 40 % (2/5) would go through {{{wan2}}}. In this case if you played 100 different videos on the Internet, about 60 would be downloaded through Wired WAN and the other 40 would be downloaded via {{{wan}}}.
then about 60 % (3/5) of traffic would go through the Wired WAN interface and about 40 % (2/5) would go through {{{wan2}}}. In this case if you played 100 different videos on the Internet, about 60 would be downloaded through Wired WAN and the other 40 would be downloaded via {{{wan2}}}.
===Rules===
----
A Load Balancing/Failover <b>Rule</b> is a set of conditions that define some type of network traffic. The traffic that matches the conditions set in the rule is handled in accordance to the specified <b>Policy</b>.
There is one default rule present on the device. You can add more rules with the 'Add' button or you can customize the existing rule by clicking the 'Edit' button next to it:
[[File:Networking_rutos_manual_failover_load_balancing_rules_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_load_balancing_rule_configuration_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Protocol</td>
<td>all | tcp | udp | icmp | esp; default: <b>all</b></td>
<td>Protocol to match this rule.</td>
</tr>
<tr>
<td>Source address</td>
<td>ip/netmask; default: <b>none</b></td>
<td>Source IP addresses to match this rule.</td>
</tr>
<tr>
<td>Destination address</td>
<td>ip/netmask; default: <b>0.0.0.0/0</b></td>
<td>Destination IP addresses to match this rule.</td>
</tr>
<tr>
<td>Sticky</td>
<td>off | <span style="color: #20C0D7;"><b>on</b></span>; default: <b>off</b></td>
<td>If turned on, traffic from the same source IP address that previously matched this rule within the sticky timeout period will use the same WAN interface.</td>
</tr>
<tr>
<td><span style="color: #20C0D7;">Sticky timeout</span></td>
<td>integer [1..1000000]; default: <b>none</b></td>
<td>Timeout in seconds.</td>
</tr>
<tr>
<td>Policy assigned</td>
<td>default (Load Balancing) | default (Failover) | Unreachable (Reject) | Blackhole (Drop) | Default (Use main routing table) | custom; default: <b>default (Failover)</b></td>
<td>Selects the policy to apply to traffic that matches the conditions of this rule. You can create custom Load Balancing/Failover policies in the section below.</td>
</tr>
</table>
====Policies====
----
A <b>Policy</b> dictates what the the device should do when some network traffic matches the condition defined in a Failover/Load Balancing rule. There are two policies by default, one for Load Balancing, the other for Failover. You may create custom policies that use different interfaces for Failover/Load Balancing scenarios.
[[File:Networking_rutos_manual_failover_load_balancing_rules_policies_v1.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Member used</td>
<td>wan {{!}} wwan {{!}} mobile wan; default: <b>all</b></td>
<td>For a network interface to be used in mwan3, it must be defined as a member, which can then be used in policies.</td>
</tr>
<tr>
<td>Last Resort</td>
<td>Unreachable (reject) {{!}} Blackhole (drop) {{!}} Default (use main routing table); default: <b>Unreachable</b></td>
<td>Determine the fallback routing behavior if all WAN members in the policy are down.</td>
</tr>
</table>
{{Template:Networking_rutos_manual_vrrp
| series = {{{series}}}
| name = {{{name}}}
}}
[[Category:{{{name}}} Network section]]
[[Category:{{{name}}} Network section]]
