forked from eworm-de/routeros-scripts
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathMikroTik Routing Failover.rsc
60 lines (49 loc) · 3.36 KB
/
MikroTik Routing Failover.rsc
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
51
52
53
54
55
56
57
58
59
# From: https://help.mikrotik.com/docs/pages/viewpage.action?pageId=26476608
# Create pseudo-addresses virtually bound to interfaces:
/ip/address
add address=192.168.8.1 interface=ether1 network=192.168.8.1
add address=192.168.1.1 interface=lte1 network=192.168.1.1
# 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=ether1
add chain=srcnat action=masquerade out-interface=lte1
#Let`s start with marking traffic with configuring routing tables and firewall mangle rules, so we will have everything preconfigured when we go to the routing section:
/routing/table
add fib name=to_ETHER
add fib name=to_LTE
/ip/firewall/mangle
add chain=output connection-state=new connection-mark=no-mark action=mark-connection new-connection-mark=ETHER_conn out-interface=ether1
add chain=output connection-mark=ETHER_conn action=mark-routing new-routing-mark=to_ETHER out-interface=ether1
add chain=output connection-state=new connection-mark=no-mark action=mark-connection new-connection-mark=LTE_conn out-interface=lte1
add chain=output connection-mark=LTE_conn action=mark-routing new-routing-mark=to_LTE out-interface=lte1
# We will split the routing configuration into three parts. First, we will configure Host1 and Host2 as destination addresses in the routing section:
/ip/route/
add dst-address=8.8.8.8 scope=10 gateway=192.168.8.1
add dst-address=8.8.4.4 scope=10 gateway=192.168.1.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-table=to_ETHER check-gateway=ping
add distance=2 gateway=8.8.4.4 routing-table=to_ETHER check-gateway=ping
# Configure similar recursive routes for the second gateway:
/ip/route/
add distance=1 gateway=8.8.4.4 routing-table=to_LTE check-gateway=ping
add distance=2 gateway=8.8.8.8 routing-table=to_LTE 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=192.168.8.1 scope=10
add dst-address=208.67.222.222 gateway=192.168.8.1 scope=10
add dst-address=8.8.4.4 gateway=192.168.1.1 scope=10
add dst-address=208.67.220.220 gateway=192.168.1.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-table=to_ETHER
add distance=2 gateway=10.20.20.2 routing-table=to_ETHER
add distance=1 gateway=10.20.20.2 routing-table=to_LTE
add distance=2 gateway=10.10.10.1 routing-table=to_LTE