RUT240 Load Balancing: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
No edit summary
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Template: Networking_rut_manual_load_balancing
==Summary==
<!------------------------DEVICE----------------------->
 
| name  = RUT240
Load balancing lets users create rules that divide traffic between different interfaces. This chapter is an Overview of the Load Balancing function in RUT routers.
| series = RUT2XX
 
}}
==Policies==
 
The '''Policies''' section contains Load Balancing policies. One default configuration named '''Balanced''' is already in place. You can edit this default policy or create a new custom one.
 
 
[[Image:Network load balancing policies.PNG|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.PNG|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.
 
==Rule==
 
The '''Rule''' section contains '''Load Balancing''' rules. One default rule named default_rule is already in place. You can edit it or create a new custom one.
 
[[Image:Networking rut manual load balancing rule.png|border]]
 
If you want to add a rule, simply write a name, press '''Add''' button and then you will be redirected to the '''Configuration window'''. In order to configure an existing rule, click the '''Edit''' button located next to it, after which you will be redirected to the '''Configuration window'''.
 
[[Image:Networking rut manual load balancing rule edit.png|border]]
 
<table class="nd-mantable">
    <tr>
        <th>Field name</th>
      <th>Value</th>
      <th>Description</th>
    </tr>
    <tr>
      <td>Source address</td>
      <td>Default: '''""'''</td>
      <td>IP address from which data will be transmitted</td>
    </tr>
    <tr>
      <td>Source port</td>
      <td>Default: '''""'''</td>
      <td>Port that will be used for transmission.</td>
    </tr>
    <tr>
      <td>Destination address</td>
      <td>Default: '''0.0.0.0/0'''</td>
      <td>Matches outgoing traffic to this IP or range of IPs only</td>
    </tr>
    <tr>
      <td>Destination port</td>
      <td>Default: '''""'''</td>
      <td>Port that will be used for transmission at the destination.</td>
    </tr>
    <tr>
      <td>Protocol</td>
      <td>Default: '''all'''</td>
      <td>Specifies to which protocol the rule should apply. All vailable options are presented in the table below</td>
    </tr>
    <tr>
      <td>Policy assigned</td>
      <td>Default: '''balanced'''</td>
      <td><Defines to which policy the rule should be assigned/td>
    </tr>
 
</table>
 
Protocol options are presented below:
 
<table class="nd-othertables">
    <tr>
        <th width="250">Option name</th>
      <th width="250">Port</th>
      <th width="250">Protocol</th>
<th width="400">Description</th>
    </tr>
    <tr>
      <td>ip</td>
      <td>0</td>
      <td>IP</td>
<td>Internet protocol, pseudo protocol number</td>
    </tr>
    <tr>
      <td>#hopopt</td>
      <td>0</td>
      <td>HOPOT</td>
<td>IPv6 Hop-by-Hop Option</td>
    </tr>
    <tr>
      <td>icmp</td>
      <td>1</td>
      <td>ICMP</td>
<td>Internet control message protocol</td>
    </tr>
    <tr>
      <td>igmp</td>
      <td>2</td>
      <td>IGMP</td>
<td>Internet Group Management</td>
    </tr>
    <tr>
      <td>ggp</td>
      <td>3</td>
      <td>GGP</td>
<td>Gateway-gateway protocol</td>
    </tr>
    <tr>
      <td>ipencap</td>
      <td>4</td>
      <td>IP-ENCAP</td>
<td>IP encapsulated in IP (officially ``IP'')</td>
    </tr>
    <tr>
      <td>st</td>
      <td>5</td>
      <td>ST</td>
<td>ST datagram mode</td>
    </tr>
    <tr>
      <td>tcp</td>
      <td>6</td>
      <td>TCP</td>
<td>Transmission control protocol</td>
    </tr>
    <tr>
      <td>egp</td>
      <td>8</td>
      <td>EGP</td>
<td>Exterior gateway protocol</td>
    </tr>
    <tr>
      <td>igp</td>
      <td>9</td>
      <td>IGP</td>
<td>Any private interior gateway</td>
    </tr>
    <tr>
      <td>pup</td>
      <td>12</td>
      <td>PUP</td>
<td>PARC universal packet protocol</td>
    </tr>
    <tr>
      <td>udp</td>
      <td>17</td>
      <td>UDP</td>
<td>User datagram protocol</td>
    </tr>
    <tr>
      <td>hmp</td>
      <td>20</td>
      <td>HMP</td>
<td>Host monitoring protocol</td>
    </tr>
    <tr>
      <td>xns-idp</td>
      <td>22</td>
      <td>XNS-IDP</td>
<td>Xerox NS IDP</td>
    </tr>
    <tr>
      <td>rdp</td>
      <td>27</td>
      <td>RDP</td>
<td>Reliable datagram protocol</td>
    </tr>
    <tr>
      <td>iso-tp4</td>
      <td>29</td>
      <td>ISO-TP4</td>
<td>ISO Transport Protocol class 4</td>
    </tr>
    <tr>
      <td>xtp</td>
      <td>36</td>
      <td>XTP</td>
<td>Xpress Transfer Protocol</td>
    </tr>
    <tr>
      <td>ddp</td>
      <td>37</td>
      <td>DDP</td>
<td>Datagram Delivery Protocol</td>
    </tr>
    <tr>
      <td>idpr-cmtp</td>
      <td>38</td>
      <td>IDPR-CMTP</td>
<td>IDPR Control Message Transport</td>
    </tr>
    <tr>
      <td>ipv6</td>
      <td>41</td>
      <td>IPv6</td>
<td>Internet Protocol, version 6</td>
    </tr>
    <tr>
      <td>ipv6-route</td>
      <td>43</td>
      <td>IPv6-Route</td>
<td>Routing Header for IPv6</td>
    </tr>
    <tr>
      <td>ipv6-frag</td>
      <td>44</td>
      <td>IPv6-Frag</td>
<td>Fragment Header for IPv6</td>
    </tr>
    <tr>
      <td>idrp</td>
      <td>45</td>
      <td>IDRP</td>
<td>Inter-Domain Routing Protocol</td>
    </tr>
    <tr>
      <td>rsvp</td>
      <td>46</td>
      <td>RSVP</td>
<td>Reservation Protocol</td>
    </tr>
    <tr>
      <td>gre</td>
      <td>47</td>
      <td>GRE</td>
<td>General Routing Encapsulation</td>
    </tr>
    <tr>
      <td>esp</td>
      <td>50</td>
      <td>IPSEC-ESP</td>
<td>Encap Security Payload</td>
    </tr>
    <tr>
      <td>ah</td>
      <td>51</td>
      <td>IPSEC-AH</td>
<td>Authentication Header</td>
    </tr>
    <tr>
      <td>skip</td>
      <td>57</td>
      <td>SKIP</td>
<td>SKIP</td>
    </tr>
    <tr>
      <td>ipv6-icmp</td>
      <td>58</td>
      <td>IPv6-ICMP</td>
<td>ICMP for IPv6</td>
    </tr>
    <tr>
      <td>ipv6-nonxt 59</td>
      <td>59</td>
      <td>IPv6-NoNxt</td>
<td>No Next Header for IPv6</td>
    </tr>
    <tr>
      <td>ipv6-opts</td>
      <td>60</td>
      <td>IPv6-Opts</td>
<td>Destination Options for IPv6</td>
    </tr>
    <tr>
      <td>rspf</td>
      <td>73</td>
      <td>RSPF CPHB</td>
<td>Radio Shortest Path First</td>
    </tr>
    <tr>
      <td>vmtp</td>
      <td>81</td>
      <td>VMTP</td>
<td>Versatile Message Transport</td>
    </tr>
    <tr>
      <td>eigrp</td>
      <td>88</td>
      <td>EIGRP</td>
<td>Enhanced Interior Routing Protocol</td>
    </tr>
    <tr>
      <td>ospf</td>
      <td>89</td>
      <td>OSPFIGP</td>
<td>Open Shortest Path First IGP</td>
    </tr>
    <tr>
      <td>ax.25</td>
      <td>93</td>
      <td>AX.25</td>
<td>AX.25 frames</td>
    </tr>
    <tr>
      <td>ipip</td>
      <td>94</td>
      <td>IPIP</td>
<td>IP-within-IP Encapsulation Protocol</td>
    </tr>
    <tr>
      <td>etherip</td>
      <td>97</td>
      <td>ETHERIP</td>
<td>Ethernet-within-IP Encapsulation</td>
    </tr>
    <tr>
      <td>encap</td>
      <td>98</td>
      <td>ENCAP</td>
<td>Yet Another IP encapsulation</td>
    </tr>
    <tr>
      <td>#</td>
      <td>99</td>
      <td>-</td>
<td>Any private encryption scheme</td>
    </tr>
    <tr>
      <td>pim</td>
      <td>103</td>
      <td>PIM</td>
<td>Protocol Independent Multicast</td>
    </tr>
    <tr>
      <td>ipcomp</td>
      <td>108</td>
      <td>IPCOMP</td>
<td>IP Payload Compression Protocol</td>
    </tr>
    <tr>
      <td>vrrp</td>
      <td>112</td>
      <td>VRRP</td>
<td>Virtual Router Redundancy Protocol</td>
    </tr>
    <tr>
      <td>l2tp</td>
      <td>115</td>
      <td>L2TP</td>
<td>Layer Two Tunneling Protocol</td>
    </tr>
    <tr>
      <td>isis</td>
      <td>124</td>
      <td>ISIS</td>
<td>IS-IS over IPv4</td>
    </tr>
    <tr>
      <td>sctp</td>
      <td>132</td>
      <td>SCTP</td>
<td>Stream Control Transmission Protocol</td>
    </tr>
    <tr>
      <td>fc</td>
      <td>133</td>
      <td>FC</td>
<td>Fibre Channel</td>
    </tr>
 
</table>
 
[[Category:RUT240 WebUI]]

Revision as of 13:36, 22 January 2020

Main Page > EOL Products > RUT240 > RUT240 Manual > RUT240 WebUI > RUT240 Network section > RUT240 Load Balancing

Summary

Load balancing lets users create rules that divide traffic between different interfaces. This chapter is an Overview of the Load Balancing function in RUT routers.

Policies

The Policies section contains Load Balancing policies. One default configuration named Balanced is already in place. You can edit this default policy or create a new custom one.



To configure a Policy, click the Edit button located next to it, after which you will be redirected to the Configuration window.



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.

Rule

The Rule section contains Load Balancing rules. One default rule named default_rule is already in place. You can edit it or create a new custom one.

If you want to add a rule, simply write a name, press Add button and then you will be redirected to the Configuration window. In order to configure an existing rule, click the Edit button located next to it, after which you will be redirected to the Configuration window.

Field name Value Description
Source address Default: "" IP address from which data will be transmitted
Source port Default: "" Port that will be used for transmission.
Destination address Default: 0.0.0.0/0 Matches outgoing traffic to this IP or range of IPs only
Destination port Default: "" Port that will be used for transmission at the destination.
Protocol Default: all Specifies to which protocol the rule should apply. All vailable options are presented in the table below
Policy assigned Default: balanced <Defines to which policy the rule should be assigned/td>

Protocol options are presented below:

Option name Port Protocol Description
ip 0 IP Internet protocol, pseudo protocol number
#hopopt 0 HOPOT IPv6 Hop-by-Hop Option
icmp 1 ICMP Internet control message protocol
igmp 2 IGMP Internet Group Management
ggp 3 GGP Gateway-gateway protocol
ipencap 4 IP-ENCAP IP encapsulated in IP (officially ``IP)
st 5 ST ST datagram mode
tcp 6 TCP Transmission control protocol
egp 8 EGP Exterior gateway protocol
igp 9 IGP Any private interior gateway
pup 12 PUP PARC universal packet protocol
udp 17 UDP User datagram protocol
hmp 20 HMP Host monitoring protocol
xns-idp 22 XNS-IDP Xerox NS IDP
rdp 27 RDP Reliable datagram protocol
iso-tp4 29 ISO-TP4 ISO Transport Protocol class 4
xtp 36 XTP Xpress Transfer Protocol
ddp 37 DDP Datagram Delivery Protocol
idpr-cmtp 38 IDPR-CMTP IDPR Control Message Transport
ipv6 41 IPv6 Internet Protocol, version 6
ipv6-route 43 IPv6-Route Routing Header for IPv6
ipv6-frag 44 IPv6-Frag Fragment Header for IPv6
idrp 45 IDRP Inter-Domain Routing Protocol
rsvp 46 RSVP Reservation Protocol
gre 47 GRE General Routing Encapsulation
esp 50 IPSEC-ESP Encap Security Payload
ah 51 IPSEC-AH Authentication Header
skip 57 SKIP SKIP
ipv6-icmp 58 IPv6-ICMP ICMP for IPv6
ipv6-nonxt 59 59 IPv6-NoNxt No Next Header for IPv6
ipv6-opts 60 IPv6-Opts Destination Options for IPv6
rspf 73 RSPF CPHB Radio Shortest Path First
vmtp 81 VMTP Versatile Message Transport
eigrp 88 EIGRP Enhanced Interior Routing Protocol
ospf 89 OSPFIGP Open Shortest Path First IGP
ax.25 93 AX.25 AX.25 frames
ipip 94 IPIP IP-within-IP Encapsulation Protocol
etherip 97 ETHERIP Ethernet-within-IP Encapsulation
encap 98 ENCAP Yet Another IP encapsulation
# 99 - Any private encryption scheme
pim 103 PIM Protocol Independent Multicast
ipcomp 108 IPCOMP IP Payload Compression Protocol
vrrp 112 VRRP Virtual Router Redundancy Protocol
l2tp 115 L2TP Layer Two Tunneling Protocol
isis 124 ISIS IS-IS over IPv4
sctp 132 SCTP Stream Control Transmission Protocol
fc 133 FC Fibre Channel
Retrieved from "https://wiki.teltonika-networks.com/index.php?title=RUT240_Load_Balancing&oldid=53446"