31,703
edits
Changes
Template:Networking rut manual load balancing legacy (view source)
Revision as of 14:15, 3 June 2021
, 14:15, 3 June 2021Created page with "{{Template: Networking_rutos_manual_fw_disclosure | fw_version = {{#switch: {{{series}}} | RUT2XX = {{{series}}}_R_00.01.13 | RUT9XX = {{{series}}}_R_00.06.07}} | series..."
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version = {{#switch: {{{series}}}
| RUT2XX = {{{series}}}_R_00.01.13
| RUT9XX = {{{series}}}_R_00.06.07}}
| series = {{{series}}}
}}
<i><b>Note</b>: this user manual page is for {{{name}}}'s old WebUI style available in earlier FW versions. <b>[[{{{name}}} Load Balancing|Click here]]</b> for information based on the latest FW version.</i>
__TOC__
==Summary==
<b>Load Balancing</b> provides the possibility create policies and rules that divide traffic between different interfaces.
This chapter of the user manual provides an overview of the Load Balancing page for {{{name}}} devices.
==Policies==
The '''Policies''' section contains Load Balancing policies. One default policy named '''Balanced''' is already in place. You can edit this default policy or create a new custom policy.
[[Image:Network load balancing policies v1.PNG|border|class=tlt-border]]
To configure a Policy, click the '''Edit''' button located next to it, after which you will be redirected to the Configuration window.
[[Image:Network load balancing policies configuration v1.PNG|border|class=tlt-border]]
As you can see from the image above, the configuration is very simple. You can assign
ratio values to WAN interfaces. The ratio values represent a percentage of load that
will go through an interface. For example, in the default configuration 3 parts of
traffic will go through the Mobile interface and 2 parts will go through the Wired
interface, which means roughly 60% (3/5) of data will be transferred through Mobile,
40% (2/5) through Wired. If the ratios would be different, say Mobile: 5, Wired: 10, then
33% (5/15) of data would be transferred through Mobile, and 66% (10/15) would go through Wired.
==Rules==
The '''Rules''' section contains Load Balancing rules. One default rule named
'''default_rule''' is already in place. You can edit this default rule or create a new custom rule.
[[Image:Network load balancing rules.PNG|border|class=tlt-border]]
To configure a rule, click the '''Edit''' button located next to it, after which you will be redirected to the Configuration window.
[[Image:Network load balancing rules configuration v1.PNG|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Source address</td>
<td>ip; Default: '''none'''</td>
<td>Source IP address. Can be specified in CIDR notation (eg "192.168.1.0/24" without quotes).</td>
</tr>
<tr>
<td>Source port</td>
<td>number; Default: '''none'''</td>
<td>Source port number. May be entered as a single or multiple ports (eg "21" or "80,443" without quotes).</td>
</tr>
<tr>
<td>Destination address</td>
<td>ip; Default: '''0.0.0.0/0'''</td>
<td>Destination IP address. Can be specified in CIDR notation (eg "192.168.1.0/24" without quotes).</td>
</tr>
<tr>
<td>Destination port</td>
<td>number; Default: '''none'''</td>
<td>Destination port number. May be entered as a single or multiple ports (eg "21" or "80,443" without quotes).</td>
</tr>
<tr>
<td>Protocol</td>
<td>all | ip | #hopopt | icmp | igmp | ggp | ipencap | st | tcp | egp | igp | pup | udp | hmp | xns | rdp | iso | xtp | ddp | idpr | ipv6 | ipv6 | ipv6 | idrp | rsvp | gre | esp | ah | skip | ipv6 | ipv6 | ipv6 | rspf | vmtp | eigrp | ospf | ax | ipip | etherip | encap | pim | ipcomp | vrrp | l2tp | isis | sctp | fc; Default: '''all'''</td>
<td>Which protocol to use.</td>
</tr>
<tr>
<td>Policy assigned</td>
<td>policies; Default: '''balanced'''</td>
<td>Policy to use for this rule.</td>
</tr>
</table>
[[Category:{{{name}}} Network section (legacy)]]
| fw_version = {{#switch: {{{series}}}
| RUT2XX = {{{series}}}_R_00.01.13
| RUT9XX = {{{series}}}_R_00.06.07}}
| series = {{{series}}}
}}
<i><b>Note</b>: this user manual page is for {{{name}}}'s old WebUI style available in earlier FW versions. <b>[[{{{name}}} Load Balancing|Click here]]</b> for information based on the latest FW version.</i>
__TOC__
==Summary==
<b>Load Balancing</b> provides the possibility create policies and rules that divide traffic between different interfaces.
This chapter of the user manual provides an overview of the Load Balancing page for {{{name}}} devices.
==Policies==
The '''Policies''' section contains Load Balancing policies. One default policy named '''Balanced''' is already in place. You can edit this default policy or create a new custom policy.
[[Image:Network load balancing policies v1.PNG|border|class=tlt-border]]
To configure a Policy, click the '''Edit''' button located next to it, after which you will be redirected to the Configuration window.
[[Image:Network load balancing policies configuration v1.PNG|border|class=tlt-border]]
As you can see from the image above, the configuration is very simple. You can assign
ratio values to WAN interfaces. The ratio values represent a percentage of load that
will go through an interface. For example, in the default configuration 3 parts of
traffic will go through the Mobile interface and 2 parts will go through the Wired
interface, which means roughly 60% (3/5) of data will be transferred through Mobile,
40% (2/5) through Wired. If the ratios would be different, say Mobile: 5, Wired: 10, then
33% (5/15) of data would be transferred through Mobile, and 66% (10/15) would go through Wired.
==Rules==
The '''Rules''' section contains Load Balancing rules. One default rule named
'''default_rule''' is already in place. You can edit this default rule or create a new custom rule.
[[Image:Network load balancing rules.PNG|border|class=tlt-border]]
To configure a rule, click the '''Edit''' button located next to it, after which you will be redirected to the Configuration window.
[[Image:Network load balancing rules configuration v1.PNG|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>field name</th>
<th>value</th>
<th>description</th>
</tr>
<tr>
<td>Source address</td>
<td>ip; Default: '''none'''</td>
<td>Source IP address. Can be specified in CIDR notation (eg "192.168.1.0/24" without quotes).</td>
</tr>
<tr>
<td>Source port</td>
<td>number; Default: '''none'''</td>
<td>Source port number. May be entered as a single or multiple ports (eg "21" or "80,443" without quotes).</td>
</tr>
<tr>
<td>Destination address</td>
<td>ip; Default: '''0.0.0.0/0'''</td>
<td>Destination IP address. Can be specified in CIDR notation (eg "192.168.1.0/24" without quotes).</td>
</tr>
<tr>
<td>Destination port</td>
<td>number; Default: '''none'''</td>
<td>Destination port number. May be entered as a single or multiple ports (eg "21" or "80,443" without quotes).</td>
</tr>
<tr>
<td>Protocol</td>
<td>all | ip | #hopopt | icmp | igmp | ggp | ipencap | st | tcp | egp | igp | pup | udp | hmp | xns | rdp | iso | xtp | ddp | idpr | ipv6 | ipv6 | ipv6 | idrp | rsvp | gre | esp | ah | skip | ipv6 | ipv6 | ipv6 | rspf | vmtp | eigrp | ospf | ax | ipip | etherip | encap | pim | ipcomp | vrrp | l2tp | isis | sctp | fc; Default: '''all'''</td>
<td>Which protocol to use.</td>
</tr>
<tr>
<td>Policy assigned</td>
<td>policies; Default: '''balanced'''</td>
<td>Policy to use for this rule.</td>
</tr>
</table>
[[Category:{{{name}}} Network section (legacy)]]