Load Balancing over Multiple Gateways
The typical situation where you got one router and want to connect to two ISPs:
<Picture comes here>
Of course, you want to do load balancing. There are several ways how to do it. Depending on the particular situation, you may find one best suited for you.
Policy Routing based on Client IP Address
If you have a number of hosts, you may group them by IP addresses. Then, send the traffic out through Gateway 1 or 2 depending on the source IP address.
Let us assume we use for our workstations IP addresses from network 192.168.100.0/24. The IP addresses are assigned as follows:
- 192.168.100.1-127 are used for Group A workstations
- 192.168.100.128-253 are used for Group B workstations
- 192.168.100.254 is ised for the router.
All workstations have IP configuration with the IP address from the relevant group, they all have network mask 255.255.255.0, and the default gateway 192.168.100.254
We will talk about DNS servers later.
Next, we need to configure policy routing. We have workstations devided into groups, where we can reffer to them using subnet addressing:
- Group A is 192.168.100.0/25, i.e., addresses 192.168.100.0-127
- Group B is 192.168.100.128/25, i.e., addresses 192.18.100.128-255
If you do not understand this, take the TCP/IP Basics course, or, look for some resources about subnetting on the Internet!
Adding Mangle Rules =
We need to add two IP Firewall Mangle rules to mark the packets originated from Group A or B workstations.
For Group A, start with specifying Chain forward and Src. Address 192.168.100.0/25:
Next, specify the Action mark routing and add New Routing Mark GroupA.
It is a good practice to add a comment as well. Your mangle rules might be interesting for someone else and for yourself as well after some time.
For Group B, specify
- Chain forward and Src. Address 192.168.100.128/25
- Action mark routing and New Routing Mark GroupB
All IP traffic coming from workstations is marked with the routing marks GroupA or GroupB. We can use these marks in the routing table.
Configuring Routes
We should specify two default routes (destination 0.0.0.0/0) with appropriate routing marks and gateways:
This thing is not going to work, unless you do masquerading for your LAN! The simpliest way to it is by adding one NAT rule for Src. Address 192.168.100.0/24 and Action masquerade: