FullMikroTik MTCRE - Failover, Ptp Addressing, Interface Based Routing (Episode 6)

Hello and welcome! In this video we will be looking at how to implement basic failover routing on RouterOS. We will be checking out Point-to-Point addressing, how to use interface-based routes, how Check Gateway works and how to configure manual failover with route distances.

Timestamps:
📕00:00 - Introduction
📕00:29 - Failover Overview
📕03:22 - Point-to-Point addressing
📕06:36 - Interface-based Routing
📕12:06 - Check Gateway
📕14:57 - Manual Failover with Distance

Support the Channel:

Social Media:

MTCRE Playlist:

MTCNA Playlist:

Thanks again for watching

[TheNetworkBerg]

NB - Interface based routing only works for Ptp configurations, trying to do this on a link where multiple hosts can reside will not work.

Reference Material:

[diwasbhatta]

such a underrated youtube channel..this channel desearves to be very famous within IT students

[gyorgykovacs]

You infected me, I fell in love with Mikrotik and routing. ;) Your passion to routing is impressing me. I had the same feelings when i started to learn programming(C, C++, Java) 6 years ago. It’s an inexplicable feeling when we see behind things and put together the details and understand how things work. You helped me to begin to understand this networking world as well. And thank you for your selflessness in sharing your valuable knowledge with us. People like you make this world a better place

[soroushsarkari]

Thanks for your wonderful channel and videos 🙏🏻

[IronTrela]

I like your videos so much. Which software you use for network design at the beginning of the video? Keep up the good work!

[kresimirpecar]

If we have for eg. vDSL router for ISP1 and LTE router for ISP2, if we want to have ISP2 as an failover (no PPPoE), we should make ether2 WAN, so ether1 is WAN1 and ether2 is WAN2, we asign them IP addresses, then remaining ports go to bridge and we enable dhcp server for that bridge. Then we can make static routes to WAN1 and WAN2 IP addresses, put distance for WAN1 to 1 and 10 for WAN2. Also we need to masquerade for each WAN IP so if traffic want to leave via WAN1 it will be NATed for WAN1 IP, and if it wants to leave via WAN2 it will be NATed for WAN2 IP.

I hope i understand correctly.

Great video as always, short so you can keep someone attention but educational. Maybe it's better to have more shorter videos than few longer ones.

[alimibrahem]

Very very thanksful man, you are a wesome..!. However, the amazing thing that i wounder how you do is how you can combin the eve topology with the winbox..? So when you disconnect the line the winbox session is quickly response to that..?
Please can you tell us how we can do that..?

[jasonvanwyngaard]

Thoroughly enjoy your channel. Seen very elaborate failover setups using mangle. Why use that instead of what you've demonstrated?

[DimitriPappas]

Great content as always. I do think it would be awesome if you could cover Ptp addressing in a bit more thorough detail at some point, as you barely skimmed the surface of that topic enough for anyone to really grasp how to implement it properly, and to be honest I don't quite understand the implementation you showed (with 100.64.0.253 as an address and 100.64.0.1 as the network/peer - these IP's are not adjacent with each other, so how does this even work exactly?). Could ANY IP be used as the network IP even if it shares nothing in common with the primary IP address? I also didn't know about /31's until now, or that we can even use /32 with peer as network address to establish a link. Until now I've just used /30's but that seems a bit wasteful for cases where a /31 or /32 configuration would work just fine. Your video did prompt me to try read up a bit more about this on the mikrotik forums for some answers, but I feel like this is still quite an uncomfortable/grey area. It it seems /31's are actually discouraged because of incompatibilities between different vendors/standards, particularly when it comes to dynamic routing protocols like OSPF, and surprisingly it seems Mikrotik are somewhat behind with their implementations/compatibility with /31 and /32 ptp which surprises me a bit given their prominence & speciality in the field of routing. Hoping to therefore hear your thoughts & sentiments on this in more depth and whether you think it's even worth using /31 and /32, especially in production/enterprise environments? Cheers! :)

[biki]

what if i have server behind my router, when main ISP is down server will be visible under different ip from second ISP, is there any clever way to make it work?

[berry]

can we send bandwidth from city A to city B with mikrotik..

[matej_stepan]

The hardest thing about failover is to determine it. Check gateway is not a great option for internet use because it checks the gateway not the internet. I have several IPs just for check fail purposes.