Load Settings Balancing Mikrotik – Failed Over (Recursive Gateway)

This time the admin wants to share about the Mikrotik Balancing Load Settings again. The case study is similar to previous articles, namely related to load balancing. This article provides more tips to those of you who have 2 internet sources at home or in boarding houses, but the internet conditions are unstable.

New!

Setting Load Balancing 2 ISP Using PCC + Fail Over + Recursive Gateway Router Mikrotik

Okay, maybe I’ll tell you a little first why I want to share these tips.

At present, in my boarding house there are enough internet facilities for daily use. It’s just that the stability is lacking. In a few minutes there was a unreachable condition to the internet.

This condition makes me disturbed when I use it for meetings, browsing, and gaming.

The idea emerged to hold the second internet source. To deal with unstable conditions I backup with a GSM modem.

This GSM modem is only used when the Mikrotik Router detects the first internet source unreachable.

Making a GSM modem as a backup is very effective for reducing quota consumption. Although still buying a quota, but the user will be small when the condition of the first internet source is still available.

Check the gateway

This feature is available on Mikrotik when making an entry route. Used to check reachable / unreachable goals of gateway.

Resursive gateway

This technique is actually a bit tricky when we set in the proxy. Generally to make routes to the internet we will set:

• DST-ADDRESS = 0.0.0.0/0
• Gateway = 192.168.1.1 (IP modem)

However, this resursive gateway will be made 2 entry routes. Like this:

1. Check the gateway to one of the public IP addresses on the internet to reach 0.0.0.0/0, through the target scope.
2. Check the Gateway to DST-ADDRESS used by the previous entry through the IP Modem Gateway.

Full version of IP Routes:

Manuscript:

/ip route
add check-gateway=ping disabled=no distance=1 dst-address=0.0.0.0/0 gateway=8.8.8.8 routing-table=main scope=20 suppress-hw-offload=no target-scope=30
add check-gateway=ping disabled=no distance=2 dst-address=1.1.1.1/32 gateway=192.168.1.1 routing-table=main scope=31 suppress-hw-offload=no target-scope=12
add check-gateway=ping disabled=no distance=1 dst-address=8.8.8.8/32 gateway=192.168.0.1 routing-table=main scope=30 suppress-hw-offload=no target-scope=11
add check-gateway=ping disabled=no distance=2 dst-address=0.0.0.0/0 gateway=1.1.1.1 routing-table=main scope=20 suppress-hw-offload=no target-scope=31

That’s all sharing related to the Mikrotik Balancing Load Settings. If there are comments and suggestions, you can stay below.

Admin Lukmanlab, Devops engineer, site reliability engineer, system administrator.