Changes

no edit summary
Line 20: Line 20:  
{{#switch: {{{series}}}
 
{{#switch: {{{series}}}
 
   | #default =
 
   | #default =
   | TRB2 =  
+
   | TRB2 | TRB2M | OTD140 =  
 
<u><b>
 
<u><b>
   Line 39: Line 39:     
<ul>
 
<ul>
    <li><i>Network → [[{{{name}}} Interfaces|Interfaces]]</i></li>
   
     <li><i>Network → [[{{{name}}} WAN|WAN]]</i></li>
 
     <li><i>Network → [[{{{name}}} WAN|WAN]]</i></li>
 
</ul>
 
</ul>
Line 47: Line 46:  
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_v1.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">
Line 71: Line 70:  
     <tr>
 
     <tr>
 
         <td>Flush connections on</td>
 
         <td>Flush connections on</td>
         <td>Connected | Disconnected: <b>none</b></td>
+
         <td>Connected {{!}} Disconnected {{!}} Interface up {{!}} Interface down: <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.<ul>
 +
            <li><b>Conected/Disconected</b> - used when internet connection appears/disappears</li>
 +
            <li><b>Interface up/Interface down</b> - used when internet cable is plugged/unplugged</li></ul></td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 112: 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.
 
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.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:
Line 124: Line 125:  
<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>
 
         <td style="text-align: right; width: 30px;"><b>3</b></td>
 
     </tr>
 
     </tr>
Line 130: Line 131:  
<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>
Line 143: 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:
 
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]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 175: Line 176:  
     <tr>
 
     <tr>
 
         <td><span style="color: #20C0D7;">Sticky timeout</span></td>
 
         <td><span style="color: #20C0D7;">Sticky timeout</span></td>
         <td>integer [1..1000000]; default: <b>600</b></td>
+
         <td>integer [1..1000000]; default: <b>none</b></td>
 
         <td>Timeout in seconds.</td>
 
         <td>Timeout in seconds.</td>
 
     </tr>
 
     </tr>
Line 189: Line 190:  
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.
 
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.png|border|class=tlt-border]]
+
[[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
 
{{Template:Networking_rutos_manual_vrrp

Navigation menu