forked from eworm-de/routeros-scripts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Dual-Ethernet_Load-Balancing-and-Failover
50 lines (42 loc) · 3 KB
/
Dual-Ethernet_Load-Balancing-and-Failover
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# Before detailed example overview, in a setup where we have private IP addresses behind the public IP, we should configure source NAT:
/ip firewall nat
add chain=srcnat action=masquerade out-interface=WAN1
add chain=srcnat action=masquerade out-interface=WAN2
# Let`s start with marking traffic with a firewall mangle rule, so we will have everything preconfigured when we go to the routing section:
/ip firewall mangle
add chain=output connection-state=new connection-mark=no-mark action=mark-connection new-connection-mark=GL-Inet out-interface=WAN1
add chain=output connection-mark=GL-Inet action=mark-routing new-routing-mark=to_GL-Inet out-interface=WAN1
add chain=output connection-state=new connection-mark=no-mark action=mark-connection new-connection-mark=Metal out-interface=WAN2
add chain=output connection-mark=Metal action=mark-routing new-routing-mark=to_Metal out-interface=WAN2
# We will split the routing configuration into three parts. First, we will configure Host1 and Host2 as a destination address in the routing section:
/ip route
add dst-address=8.8.8.8 scope=10 gateway=172.17.40.1
add dst-address=8.8.4.4 scope=10 gateway=172.18.40.1
# Now configure routes that will be resolved recursively, so they will only be active when they are reachable with ping:
/ip route
add distance=1 gateway=8.8.8.8 routing-mark=to_GL-Inet check-gateway=ping
add distance=2 gateway=8.8.4.4 routing-mark=to_GL-Inet check-gateway=ping
# Configure similar recursive routes for the second gateway:
/ip route
add distance=1 gateway=8.8.4.4 routing-mark=to_Metal check-gateway=ping
add distance=2 gateway=8.8.8.8 routing-mark=to_Metal check-gateway=ping
# Adding Multiple Hosts
# In the case where Host1 and Host2 fail, the corresponding link is considered failed too. In this section, we will use two additional hosts for redundancy.
# In our example, we will use OpenDNS servers Host1B (208.67.222.222) and Host2B (208.67.220.220):
/ip route
add dst-address=8.8.8.8 gateway=172.17.40.1 scope=10
add dst-address=208.67.222.222 gateway=172.17.40.1 scope=10
add dst-address=8.8.4.4 gateway=172.18.40.1 scope=10
add dst-address=208.67.220.220 gateway=172.18.40.1 scope=10
# Then, let's create destinations to "virtual" hops to use in further routes. We will use 10.10.10.1 and 10.20.20.2 as an example, but you can use different ones, be sure they do not override other configured IP addresses in your setup:
/ip route
add dst-address=10.10.10.1 gateway=8.8.8.8 scope=10 target-scope=10 check-gateway=ping
add dst-address=10.10.10.1 gateway=208.67.222.222 scope=10 target-scope=10 check-gateway=ping
add dst-address=10.20.20.2 gateway=8.8.4.4 scope=10 target-scope=10 check-gateway=ping
add dst-address=10.20.20.2 gateway=208.67.220.220 scope=10 target-scope=10 check-gateway=ping
# Do not forget to add routes with routing marks:
/ip route
add distance=1 gateway=10.10.10.1 routing-mark=to_GL-Inet
add distance=2 gateway=10.20.20.2 routing-mark=to_GL-Inet
add distance=1 gateway=10.20.20.2 routing-mark=to_Metal
add distance=2 gateway=10.10.10.1 routing-mark=to_Metal