Changes

1,848 bytes added , 23 April

no edit summary

Line 1: Line 1: −

{{Template: ~~Networking_rutos_manual_fw_disclosure~~

+

{{Template: Networking_device_manual_fw_disclosure

−

| ~~fw_version~~ = {{{series}}}~~{{#ifeq:~~{{{name}}}|~~RUT241|M~~|}}~~_R_00.07.01~~

+

| series = {{{series}}}

−

| ~~series~~ = {{{~~series~~}}}

+

| name = {{{name}}}

+

| fw_version ={{Template: Networking_device_manual_latest_fw

+

| series = {{{series}}}

+

| name = {{{name}}}

+

}}

−

{{#ifeq: {{{series}}} | RUT9 | Note: [[{{{name}}} WAN (legacy WebUI)|click here]] for the old style WebUI (FW version ~~RUT9XX_R_00.06.08.5~~ and earlier) user manual page.|}}{{#ifeq: {{{series}}} | RUT2 |

+

{{#ifeq: {{{series}}} | RUT9 | Note: [[{{{name}}} WAN (legacy WebUI)|click here]] for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.|}}

−

~~{{#switch: {{{name}}}~~

+

{{#ifeq: {{{series}}} | RUT2 | Note: [[{{{name}}} WAN (legacy WebUI)|click here]] for the old style WebUI (FW version {{Template: Networking_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.|}}

−

~~| RUT241 =~~

−

~~| #default =~~

−

Note: [[{{{name}}} WAN (legacy WebUI)|click here]] for the old style WebUI (FW version ~~RUT2XX_R_00.01.14.4~~ and earlier) user manual page.}}

−

|}}

__TOC__

==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

Line 18: Line 18:

}}

−

~~==Failover==~~

+

{{#switch: {{{series}}}

−

{{#~~ifeq~~: {{{~~name~~}}} | ~~RUTX08~~ | ~~Attention:~~<~~/span~~> ~~if you're using a {{{name}}} device~~~~, 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}}} ~~Interfaces~~|~~Interfaces~~]] page.

+

| #default =

−

----~~|}}~~

+

| TRB2 | TRB2M | OTD140 =

+

+

Note: Failover is additional software that can be installed from the System → [[{{{name}}} Package Manager|Package Manager]] page.

+

}}

+

===Multiwan===

+

----

The Failover 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| Note: You will not see any extra interfaces unless you have LAN ports configured as WAN.|}}

−

[[File:~~Networking_rutos_manual_failover_failover_interfaces~~.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.

Line 32: Line 39:

<ul>

−

~~<li>Network → [[{{{name}}} Interfaces|Interfaces]]</li>~~

<li>Network → [[{{{name}}} WAN|WAN]]</li>

</ul>

−

===Failover Interface Configuration===

+

====Failover Interface Configuration====

----

A failover Interface Configuration 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.

−

[[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]]

Line 59: Line 65:

<tr>

<td>Interval</td>

−

<td>integer; default: 3</td>

+

<td>integer [1..65000]; default: 3</td>

<td>Number of seconds between each test</td>

</tr>

<tr>

<td>Flush connections on</td>

−

<td>Connected | Disconnected ~~| none | both; default~~: none</td>

+

<td>Connected {{!}} Disconnected {{!}} Interface up {{!}} Interface down: none</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.<ul>

+

<li>Conected/Disconected - used when internet connection appears/disappears</li>

+

<li>Interface up/Interface down - used when internet cable is plugged/unplugged</li></ul></td>

</tr>

<tr>

<td>Method</td>

−

<td>Ping; default: Ping</td>

+

<td>Ping | Wget; default: Ping</td>

<td>Defines how health check will be performed on this interface when determining its state.</td>

</tr>

<tr>

<td>Track IP</td>

−

<td>ip | hostname; default: 8.8.4.4,8.8.8.8</td>

+

<td>ip | hostname; default: 1.1.1.1,8.8.8.8</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>

<td>Reliability</td>

−

<td>integer; default: 1</td>

+

<td>integer [1..65000]; default: 1</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>

<td>Count</td>

−

<td>integer; default: 1</td>

+

<td>integer [1..65000]; default: 1</td>

<td>Number of pings to send to each host with each test.</td>

</tr>

<tr>

−

<td>integer; default: 3</td>

+

<td>integer [1..65000]; default: 3</td>

<td>Number of successful tests required to considered an interface as 'Online'.</td>

</tr>

<tr>

−

<td>integer; default: 3</td>

+

<td>integer [1..65000]; default: 3</td>

<td>Number of failed tests required to considered an interface as 'Offline'.</td>

</tr>

Line 105: Line 113:

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.

−

[[File:~~Networking_rutos_manual_failover_load_balancing_interfaces~~.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 assign ratio values 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:

Line 117: Line 125:

<table>

<tr>

−

<td style="text-align: left; width: 150px;"><li>Wired WAN Ratio:</li></td>

+

<td style="text-align: left; width: 150px;"><ul><li>Wired WAN Ratio:</li></ul></td>

−

<td style="text-align: right; width: 30px;">3

+

</tr>

</table>

<table>

<tr>

−

<td style="text-align: left; width: 150px;"><li>{{{wan2}}} Ratio:</li></td>

+

<td style="text-align: left; width: 150px;"><ul><li>{{{wan2}}} Ratio:</li></ul></td>

</tr>

Line 136: Line 144:

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~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_failover_load_balancing_rules_v1.png|border|class=tlt-border]]

−

[[File:~~Networking_rutos_manual_failover_load_balancing_rule_configuration~~.png|border|class=tlt-border]]

+

[[File:Networking_rutos_manual_failover_load_balancing_rule_configuration_v1.png|border|class=tlt-border]]

Line 155: Line 163:

<td>ip/netmask; default: none</td>

<td>Source IP addresses to match this rule.</td>

+

</tr>

+

<tr>

+

<td>Destination address</td>

+

<td>ip/netmask; default: 0.0.0.0/0</td>

+

<td>Destination IP addresses to match this rule.</td>

</tr>

<tr>

Line 163: Line 176:

<tr>

<td>Sticky timeout</td>

−

<td>integer [1..1000000]; default: ~~600~~</td>

+

<td>integer [1..1000000]; default: none</td>

<td>Timeout in seconds.</td>

</tr>

Line 172: Line 185:

</tr>

</table>

+

====Policies====

+

----

+

A Policy 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]]

+

+

<tr>

+

<th>Field</th>

+

<th>Value</th>

+

<th>Description</th>

+

</tr>

+

<tr>

+

<td>Member used</td>

+

<td>wan {{!}} wwan {{!}} mobile wan; default: all</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: Unreachable</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]]

Vainius.l

Administrators

8,949

edits

Changes

Template:Networking rutos manual failover (view source)

Revision as of 10:59, 23 April 2024