Difference between revisions of "Load Balancing Rules/Policies examples"
| (10 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
==Introduction== | ==Introduction== | ||
| Line 12: | Line 11: | ||
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 in the top-right corner of the page: | ||
| − | [[File: | + | [[File:Networking_rutos_manual_failover_load_balancing_select.png|border|class=tlt-border]] |
| − | |||
| − | |||
| − | |||
| − | |||
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should '''turn on "Advanced WebUI" mode'''. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI. | If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should '''turn on "Advanced WebUI" mode'''. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI. | ||
| − | [[File: | + | [[File:Networking rutx manual webui basic advanced mode v1.gif|border|class=tlt-border]] |
| + | ---- | ||
==Prerequisites== | ==Prerequisites== | ||
| Line 30: | Line 26: | ||
==Preparation== | ==Preparation== | ||
| + | |||
As mentioned in Prerequisites, you will need to configure a VLAN on the RUT device, detailed instructions on how to configure it can be found on this page: '''[[VLAN Set Up]]''' | As mentioned in Prerequisites, you will need to configure a VLAN on the RUT device, detailed instructions on how to configure it can be found on this page: '''[[VLAN Set Up]]''' | ||
Everything else we will configure along the way. | Everything else we will configure along the way. | ||
===Topology=== | ===Topology=== | ||
| − | + | ||
| − | + | Placeholder | |
==Configurating RUTX12 device== | ==Configurating RUTX12 device== | ||
| − | |||
| − | + | We will start with the RUTX12 configuration. We will configure '''RUTX12''' traffic from '''LAN''' port 1 to go through '''SIM1''' and traffic from '''LAN''' port 2 to go through '''SIM2'''. To complete this configuration you will require to have '''one VLAN configurated already'''. Let's begin by navigating to your device's '''WebUI → Network → Failover'''. On this page you will need to configure two new rules, to do so at the bottom you can find the '''ADD NEW INSTANCE''' section, where input the name for a rule and press the button '''ADD'''. | |
| + | [[File:Networking rut configuration mwan new rule v1.jpg|border|class=tlt-border|1100px]] | ||
| − | + | In the topology, you can see that the second '''LAN''' port has an IP of '''192.168.3.0/24''', we will configure the first rule accordingly for this port. | |
---- | ---- | ||
| − | + | ===LAN2 configuration=== | |
| − | * ''' | + | |
| − | * ''' | + | [[File:Networking rut configuration mwan new policy v1.jpg|border|class=tlt-border|1100px]] |
| + | |||
| + | * '''Source address''' - input your '''VLAN''' network address in this example '''192.168.3.0/24''' | ||
| + | * '''Destination address''' - leave '''0.0.0.0/0''' here, since we want to use this rule when navigating '''anywhere''' from '''LAN2''' port | ||
| + | * '''Policy assigned''' - pick the policy on which you have set up for '''mob1s2a1''' | ||
| + | * '''Policy''' - here we will need to create two Policies (both of them for Load Balancing), like in the example create one rule for '''mob1s1a1''' and one for '''mob1s2a1'''. Once they are created assign '''mob1s2a1''' to this '''Rule'''. | ||
| − | + | After setting everything up Save the configuration. | |
| + | ---- | ||
===LAN1 configuration=== | ===LAN1 configuration=== | ||
| − | - | + | |
| + | [[File:Networking rut configuration mwan new rule lan v1.jpg|border|class=tlt-border|1100px]] | ||
| + | |||
* '''Source address''' - input your '''LAN''' network address in this example '''192.168.1.0/24''' | * '''Source address''' - input your '''LAN''' network address in this example '''192.168.1.0/24''' | ||
* '''Destination address''' - leave '''0.0.0.0/0''' here, since we want to use this rule when navigating '''anywhere''' from '''LAN1''' port | * '''Destination address''' - leave '''0.0.0.0/0''' here, since we want to use this rule when navigating '''anywhere''' from '''LAN1''' port | ||
* '''Policy assigned''' - pick the policy on which you have set up for '''mob1s1a1''' | * '''Policy assigned''' - pick the policy on which you have set up for '''mob1s1a1''' | ||
| − | |||
| − | |||
| − | + | Here we will not be creating new Policies since we already did that on the '''LAN2''' configuration. | |
| − | + | ||
| − | + | After setting everything up Save the configuration. And after that '''Enable''' the Load Balancing for '''mob1s1a1''' and '''mob1s2a1''' interfaces. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | After setting everything up Save the configuration. | ||
| − | |||
For RUTX12 the configuration is finished, if you are not planning to configure another device (with one modem) skip to the '''Testing the Configuration''' section. | For RUTX12 the configuration is finished, if you are not planning to configure another device (with one modem) skip to the '''Testing the Configuration''' section. | ||
| − | + | ||
| − | |||
| − | |||
==Configurating Device with one modem== | ==Configurating Device with one modem== | ||
| + | |||
In this section, we will configure a device unlike '''RUTX12''' with one modem. We will configure all of the traffic from the '''LAN1''' port to go through '''SIM1''' and all of the traffic from the '''LAN2''' port will go through WiFi WAN (you can use regular Wired WAN instead). | In this section, we will configure a device unlike '''RUTX12''' with one modem. We will configure all of the traffic from the '''LAN1''' port to go through '''SIM1''' and all of the traffic from the '''LAN2''' port will go through WiFi WAN (you can use regular Wired WAN instead). | ||
Once again we will start the configuration by '''configuring''' '''LAN2''' port traffic, keep in mind that the '''LAN2''' port is configurated as '''VLAN 192.168.3.0/24'''. | Once again we will start the configuration by '''configuring''' '''LAN2''' port traffic, keep in mind that the '''LAN2''' port is configurated as '''VLAN 192.168.3.0/24'''. | ||
| + | ---- | ||
| + | ===LAN2 configuration=== | ||
| + | |||
| + | [[File:Networking rut configuration mwan new policy rut2 v1.jpg|border|class=tlt-border|1100px]] | ||
| + | |||
| + | * '''Source address''' - input your '''VLAN''' network address in this example '''192.168.3.0/24''' | ||
| + | * '''Destination address''' - leave '''0.0.0.0/0''' here, since we want to use this rule when navigating '''anywhere''' from '''LAN2''' port | ||
| + | * '''Policy assigned''' - pick the policy on which you have set up for '''Wireless WAN''' or '''Wired WAN''' | ||
| + | * '''Policy''' - here we will need to create two Policies (both of them for Load Balancing), like in the example create one rule for '''mob1s1a1''' and one for '''Wireless WAN''' or '''Wired WAN'''. Once they are created assign '''Wired WAN''' to this '''Rule'''. | ||
| − | + | After setting everything up Save the configuration. | |
| − | |||
| − | |||
| − | |||
| − | |||
---- | ---- | ||
| − | |||
===LAN1 configuration=== | ===LAN1 configuration=== | ||
| − | - | + | |
| + | [[File:Networking rut configuration mwan new policy rut2 wwan v1.jpg|border|class=tlt-border|1100px]] | ||
| + | |||
* '''Source address''' - input your '''LAN''' network address in this example '''192.168.1.0/24''' | * '''Source address''' - input your '''LAN''' network address in this example '''192.168.1.0/24''' | ||
* '''Destination address''' - leave '''0.0.0.0/0''' here, since we want to use this rule when navigating '''anywhere''' from '''LAN1''' port | * '''Destination address''' - leave '''0.0.0.0/0''' here, since we want to use this rule when navigating '''anywhere''' from '''LAN1''' port | ||
| − | * '''Policy assigned''' - pick the policy on which you have set up for ''' | + | * '''Policy assigned''' - pick the policy on which you have set up for '''mob1s1a1''' |
| − | + | ||
| − | + | Here we will not be creating new Policies since we already did that on the '''LAN2''' configuration. | |
| + | After setting everything up Save the configuration. And after that '''Enable''' the Load Balancing for '''mob1s1a1''' and '''Wireless WAN/Wired WAN''' interfaces. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Testing Configuration== | ==Testing Configuration== | ||
| + | |||
In order to test if the configuration if it's working we will use TCP Dump, TCP Dump will let us capture traffic that goes through each interface of the device. | In order to test if the configuration if it's working we will use TCP Dump, TCP Dump will let us capture traffic that goes through each interface of the device. | ||
===Installing TCP Dump on RUT=== | ===Installing TCP Dump on RUT=== | ||
| − | + | ||
Firstly, you will need to connect to the '''RUT''' device's '''CLI/SSH'''. You can connect the '''RUT''' device CLI via WebUI by navigating to '''Services → CLI'''. Log in to '''CLI''' with the user name '''root''' and the router's admin password. | Firstly, you will need to connect to the '''RUT''' device's '''CLI/SSH'''. You can connect the '''RUT''' device CLI via WebUI by navigating to '''Services → CLI'''. Log in to '''CLI''' with the user name '''root''' and the router's admin password. | ||
| Line 121: | Line 114: | ||
To test if TCP Dump has been installed on your device execute the command ''tcpdump'' | To test if TCP Dump has been installed on your device execute the command ''tcpdump'' | ||
| + | ---- | ||
| + | ===Testing the configuration via TCPDUMP=== | ||
| − | + | The simplest way to test the configuration via '''tcpdump''' would be to use two commands from the same device. The first one would be ping to google DNS (from 192.168.1.1 and 192.168.3.1 IPs) and the other would be to '''tcpdump''' the correct interface. I will be using the setup of '''Configurating Device with one modem''' for this example, the '''RUTX12''' testing is almost identical. | |
| − | |||
| − | The simplest way to test the configuration via '''tcpdump''' would be to use two commands from the same device. The first one would be ping to google DNS (from 192.168.1.1 and 192.168.3.1 IPs) and the other would be to '''tcpdump''' the correct interface. I will be using the setup of '''Configurating | ||
We will do this by opening two instances of your device's '''CLI/SSH''', to access it, login to one of the routers' WebUI and navigate to '''Services → CLI'''. Log in to CLI with the user name '''root''' and the router's admin password (Open two instances of CLI). | We will do this by opening two instances of your device's '''CLI/SSH''', to access it, login to one of the routers' WebUI and navigate to '''Services → CLI'''. Log in to CLI with the user name '''root''' and the router's admin password (Open two instances of CLI). | ||
| − | In the first instance, we will let the ping command which will send ICMP requests to '''8.8.8.8''' from '''192.168. | + | In the first instance, we will let the ping command which will send ICMP requests to '''8.8.8.8''' from '''192.168.3.1(VLAN IP)'''. The command for this will be used: '''''ping -I 192.168.3.1 8.8.8.8''''' |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | On the second instance, we will run TCPDUMP on interface '''wlan0''' to capture if packets are coming through '''WiFi WAN'''. The command for this will be used: '''''tcpdump -i wlan0''''' | |
| − | |||
| − | |||
Revision as of 12:41, 14 December 2022
Main Page > General Information > Configuration Examples > Router control and monitoring > Load Balancing Rules/Policies examplesIntroduction
In this example, we will examine Load Balancing rules and policies and we will set up rules where all traffic from one LAN port will be going through the Mobile interface and all the traffic from the second port will be going through the Wireless WAN/Wired WAN or the Second Sim card (if used with RUTX12).
Load Balancing 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 Load Balancing does not increase speed for any single connection. For example, if you're downloading a large file, using Load Balancing will not increase the speed of that download.
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:
If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI.
Prerequisites
- RUTX12 device or any other RUT device
- 2 SIM cards or other WAN alternatives (WiFi WAN or regular LAN cable connected to WAN port)
- At least one end device (PC, Laptop, Tablet, Smartphone) to configure the routers
- At least one VLAN configurated on a device
Preparation
As mentioned in Prerequisites, you will need to configure a VLAN on the RUT device, detailed instructions on how to configure it can be found on this page: VLAN Set Up Everything else we will configure along the way.
Topology
Placeholder
Configurating RUTX12 device
We will start with the RUTX12 configuration. We will configure RUTX12 traffic from LAN port 1 to go through SIM1 and traffic from LAN port 2 to go through SIM2. To complete this configuration you will require to have one VLAN configurated already. Let's begin by navigating to your device's WebUI → Network → Failover. On this page you will need to configure two new rules, to do so at the bottom you can find the ADD NEW INSTANCE section, where input the name for a rule and press the button ADD.
In the topology, you can see that the second LAN port has an IP of 192.168.3.0/24, we will configure the first rule accordingly for this port.
LAN2 configuration
- Source address - input your VLAN network address in this example 192.168.3.0/24
- Destination address - leave 0.0.0.0/0 here, since we want to use this rule when navigating anywhere from LAN2 port
- Policy assigned - pick the policy on which you have set up for mob1s2a1
- Policy - here we will need to create two Policies (both of them for Load Balancing), like in the example create one rule for mob1s1a1 and one for mob1s2a1. Once they are created assign mob1s2a1 to this Rule.
After setting everything up Save the configuration.
LAN1 configuration
- Source address - input your LAN network address in this example 192.168.1.0/24
- Destination address - leave 0.0.0.0/0 here, since we want to use this rule when navigating anywhere from LAN1 port
- Policy assigned - pick the policy on which you have set up for mob1s1a1
Here we will not be creating new Policies since we already did that on the LAN2 configuration.
After setting everything up Save the configuration. And after that Enable the Load Balancing for mob1s1a1 and mob1s2a1 interfaces. For RUTX12 the configuration is finished, if you are not planning to configure another device (with one modem) skip to the Testing the Configuration section.
Configurating Device with one modem
In this section, we will configure a device unlike RUTX12 with one modem. We will configure all of the traffic from the LAN1 port to go through SIM1 and all of the traffic from the LAN2 port will go through WiFi WAN (you can use regular Wired WAN instead). Once again we will start the configuration by configuring LAN2 port traffic, keep in mind that the LAN2 port is configurated as VLAN 192.168.3.0/24.
LAN2 configuration
- Source address - input your VLAN network address in this example 192.168.3.0/24
- Destination address - leave 0.0.0.0/0 here, since we want to use this rule when navigating anywhere from LAN2 port
- Policy assigned - pick the policy on which you have set up for Wireless WAN or Wired WAN
- Policy - here we will need to create two Policies (both of them for Load Balancing), like in the example create one rule for mob1s1a1 and one for Wireless WAN or Wired WAN. Once they are created assign Wired WAN to this Rule.
After setting everything up Save the configuration.
LAN1 configuration
- Source address - input your LAN network address in this example 192.168.1.0/24
- Destination address - leave 0.0.0.0/0 here, since we want to use this rule when navigating anywhere from LAN1 port
- Policy assigned - pick the policy on which you have set up for mob1s1a1
Here we will not be creating new Policies since we already did that on the LAN2 configuration.
After setting everything up Save the configuration. And after that Enable the Load Balancing for mob1s1a1 and Wireless WAN/Wired WAN interfaces.
Testing Configuration
In order to test if the configuration if it's working we will use TCP Dump, TCP Dump will let us capture traffic that goes through each interface of the device.
Installing TCP Dump on RUT
Firstly, you will need to connect to the RUT device's CLI/SSH. You can connect the RUT device CLI via WebUI by navigating to Services → CLI. Log in to CLI with the user name root and the router's admin password.
Now execute these commands one at a time:
opkg update
opkg install tcpdump
To test if TCP Dump has been installed on your device execute the command tcpdump
Testing the configuration via TCPDUMP
The simplest way to test the configuration via tcpdump would be to use two commands from the same device. The first one would be ping to google DNS (from 192.168.1.1 and 192.168.3.1 IPs) and the other would be to tcpdump the correct interface. I will be using the setup of Configurating Device with one modem for this example, the RUTX12 testing is almost identical.
We will do this by opening two instances of your device's CLI/SSH, to access it, login to one of the routers' WebUI and navigate to Services → CLI. Log in to CLI with the user name root and the router's admin password (Open two instances of CLI).
In the first instance, we will let the ping command which will send ICMP requests to 8.8.8.8 from 192.168.3.1(VLAN IP). The command for this will be used: ping -I 192.168.3.1 8.8.8.8
On the second instance, we will run TCPDUMP on interface wlan0 to capture if packets are coming through WiFi WAN. The command for this will be used: tcpdump -i wlan0
