Unfortunately for some and fortunately for others it is not a joke. IS-IS is in development but disabled for wider public in v7.12. Stay tuned, its coming soon.
All I can say is FANTASTIC!!! I won’t ask for any concrete information but I do hope its at least IPv4 functionally capable for production use within a years time. OSPF is, always has been and always will be an utterly shit protocol for ISP and especially WISP environments. It’s just completely the wrong protocol for it and does not allow growth and implementation that matches reality. So the sooner I can dump it in favor of IS-IS for backhaul the better
yep, it’s in 7.13b1. I’ve got it up in the lab. pretty straight forward, although I’m having some issue with it forgetting disabled or removed routes. but it does bring routes up so that’s step 1! Also, no BFD toggle, BFD is essential for ISIS.
depends. and ‘virtual links’ is a big ambiguous. IS-IS requires an ethernet-like layer2 interface, it wont run over IPIP or Wireguard for example, but it will certainly work over anything that looks like layer2, EOIP tunnels, VPLS, WDS, etc.
It’s a trade off. Having to build an IP layer to run your dynamic routing for OSPF or BGP for example really makes you a ‘hybrid’ network, ie you have static IP configurations that enable the dynamic routing. IS-IS removes that, you have some interface templates but otherwise you’re just interface routing. Configuration, once well planned, is very very simple.
I am looking forward to try IS-IS over primarily Zerotier tunnels (Layer 2). Either than, or VXLAN tunnels (over Layer 3 tunnels). Not to keen on maintaining OpenVPN tap tunnels.
When you are just looking for a routing protocol that can do routing in a MikroTik environment, e.g. for VPN, you can just as well use eBGP.
It works quite well and is easy to configure (although in v7 not as easy as in v6). Once you get the hang of it, you get it working in 5 minutes.
yes, and we do this, prefer it to OSPF (way faster…)
but, it’s still static subnets and ptp configurations etc.
IS-IS is basically setting up the instance and interface templates and it will just work and you can change costs etc as needed to direct traffic but it just works. That’s one thing that’s very very attractive about it, no messing up subnets, tracking /29s, no MTU mismatches, unlike OSPF it does differential updates so topology changes to rock the boat.