Changes

no edit summary
Line 1: Line 1: −
{{Template:Networking_rutos_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.04.1
+
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series     = {{{series}}}
+
| name  = {{{name}}}
 +
| series = {{{series}}}
 +
}}
 
}}
 
}}
 +
{{#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_rutos_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_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
 
__TOC__
 
__TOC__
 
==Summary==
 
==Summary==
Line 10: Line 14:  
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 
| series = {{{series}}}
 
| series = {{{series}}}
 +
}}
 +
 +
{{#switch: {{{series}}}
 +
  | #default =
 +
  | TRB2 =
 +
<u><b>
 +
 +
Note:</b> Failover is additional software that can be installed from the <b>Services → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
 
}}
 
}}
    
==Failover==
 
==Failover==
{{#ifeq: {{{name}}} | RUTX08 | <b><span style="color: red;">Attention:</span></b> 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}}} Interface|Interfaces]] page.<br>|}}
   
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, 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}}}_v1.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.
Line 33: Line 44:  
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_v1.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.
Line 92: Line 103:  
</table>
 
</table>
   −
===Load Balancing===
+
==Load Balancing==
----
+
 
 
<b>Load Balancing</b> is a method of dividing traffic between multiple WAN interfaces. Load Balancing can be used to share the data load between different interfaces and increase the overall Internet speed for multiple users and connections. It is important to note that <u>Load Balancing does not increase speed for any single connection</u>. For example, if you're downloading a large file, using Load Balancing will not increase the speed of that download.
 
<b>Load Balancing</b> is a method of dividing traffic between multiple WAN interfaces. Load Balancing can be used to share the data load between different interfaces and increase the overall Internet speed for multiple users and connections. It is important to note that <u>Load Balancing does not increase speed for any single connection</u>. For example, if you're downloading a large file, using Load Balancing will not increase the speed of that download.
   Line 104: Line 115:  
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.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:
   −
<ul>
+
<table>
     <li><table><tr><td style="text-align: left; width: 70px;"><i>Wired WAN Ratio:</i></td><td style="text-align: right; width: 30px;"><b>3</b></tr></table></li>
+
     <tr>
     <li><table><tr><td style="text-align: left; width: 70px;"><i>{{{wan2}}} Ratio:</i></td><td style="text-align: right; width: 30px;"><b>2</b></tr></table></li>
+
        <td style="text-align: left; width: 150px;"><li><i>Wired WAN Ratio:</i></li></td>
</ul>
+
        <td style="text-align: right; width: 30px;"><b>3</b>
 +
    </tr>
 +
</table>
 +
<table>
 +
     <tr>
 +
        <td style="text-align: left; width: 150px;"><li><i>{{{wan2}}} Ratio:</i></li></td>
 +
        <td style="text-align: right; width: 30px;"><b>2</b></td>
 +
    </tr>
 +
</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 {{{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.png|border|class=tlt-border]]
 +
 
 +
[[File:Networking_rutos_manual_failover_load_balancing_rule_configuration.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>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>600</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.
   −
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}}}.
+
[[File:Networking_rutos_manual_failover_load_balancing_rules_policies.png|border|class=tlt-border]]
    
[[Category:{{{name}}} Network section]]
 
[[Category:{{{name}}} Network section]]

Navigation menu