load balancing and failover on mikrotik from generic router with ppoe and static connection

RouterOS General
21

that’s just what I wanted to say, ‘add check-gateway option (ping or arp) for all four routes’ if I ping e.g. gateway 192.168.1.1 this will always be up even without connection from wisp1

22

That’s common problem. Because even with lines connected directly to router, availability of gateway doesn’t guarantee anything, because it can be dead right after that. That’s why people came up with more advanced solutions, like the one in linked thread.

23

for the failover I modified the routes as you suggested I added these rules and the screenshot of how the routes changed.

/ip route
add dst-address=88.149.128.12 gateway=192.168.1.1 scope=10
add dst-address=8.8.8.8 gateway=192.168.8.1 scope=10

/ip route
add distance=1 gateway=88.149.128.12 routing-mark=wan1 check-gateway=ping
add distance=2 gateway=8.8.8.8 routing-mark=wan1 check-gateway=ping

/ip route
add distance=1 gateway=8.8.8.8 routing-mark=wan2 check-gateway=ping
add distance=2 gateway=88.149.128.12 routing-mark=wan2 check-gateway=ping

routes changes.png
In your opinion, is everything correct?
I don’t understand if the first rule in the list screenshot, automatically created by the bridge, should be maintained or deleted.

24

I don’t use this config often, but it seems ok. First route is probably from dhcp client, and it’s what RB itself will use, if it needs to access internet. You can disable it and add same two routes like you have for wan1 and wan2, but without routing mark, and it will give you the same failover.

25

I tried, unfortunately it doesn’t work, the wifi connects for a few seconds and then disconnects, same thing for ethernet connections.

26

Try to provide more details, what exactly did and didn’t work?

  • Original config without recursive routes
  • Recursive routes for clients
  • Recursive routes for router
27

I went back to the default bridge configuration, because I couldn’t connect to mikrotik via cable or wifi.
I can’t clearly tell you what doesn’t work, but on mikrotik I did this: I deleted the failover routes back to the previous configuration (as you can see in the previous screenshot) and then to the default ones but it still didn’t work.
So I assume there is some problem with the rules in the firewall.