IPSec VTI

36fc2361959b56bad15a97bdeff62b5f.jpg

It is exotic in the market for MikroTik devices. Ok, maybe not so much now as it was a couple of years ago, but still most MikroTik users demand OpenVPN or Wireguard, not IPsec.

so, if IPSEC is that exotic, please tell me why there is so many threads about it and why is mikrotik working hard on supporting hw-acceleration for IPSEC wherever possible and why is mikrotik improving their ipsec implementation all the time?

how do you know, what types of vpn are being requested by mikrotik users? do you have access to usage statistics, have you spoken to mikrotik employees who know the stats?

i think you may be captured in your perspective a bit.

Well, just like you judge the demand for VTI by the number of forum threads about it, I judge the demand for OpenVPN and Wireguard by their respective threads on the forum. Those numbers are way higher than for VTI.

Don’t understand me wrong, I also need VTI here for one specific purpose, but I can understand that not every request can be granted.
Also, I think part of those that want VTI will realize only after it has been implemented that in fact they require other unimplemented protocols as well to match what others demand from them (like NHRP).

wait, I never said VTI would have a higher demand/forum thread count than OpenVPN or Wireguard.
We were talking about IPSEC in general, which you downplayed.

Again, I do not want to accept VTI being referred to as “granting/responding to every request”. That always sound to me like people would be requesting mikrotik to support some arbitrary, exotic alien technology nobody uses. But as I mentioned earlier, VTI is widely used and supported and IMHO vastly superior to what mikrotik is doing currently.

i sincerely hope that they’ll implement it one day.

regarding the other protocols you mentioned, like NHRP, I can’t tell, I just want interfaces :stuck_out_tongue:

When you think that VTI just means “standard IPsec tunnel but with virtual interfaces instead of policies on existing interfaces”: that is not really true, read back above to e.g. explanation by “doneware”.
Sure it is handy to have a virtual interface for your tunneled traffic, but MikroTik already supports that: IPIP over IPsec transport.
That works with other standard routers. Same for GRE over IPsec transport, that has the advantage of also supporting IPv6, Multicast etc.
But that still is not the same as VTI.

as I have mostly interop inconveniences with fortigates, I can’t resort to ip-ip or gre, as these often can’t be hw offloaded on the smaller fortigate models, whereas IPSEC VTI can.

Well, apologies, OpenWRT again :slight_smile: :
https://openwrt.org/docs/guide-user/services/vpn/strongswan/site2site#route-based_vpns

Every device used with OpenWRT has VTI support… So I don´t think VTI is exotic in the market of home/soho routers for power users!

On “enterprise” routers/firewalls/toasters VTI is a long established feature by every vendor I know of.

I´m optimistic however: MT brought a lot of great new features with ROS7. I will probably live to see VTI, not only BFD and ISIS.

IS-IS is probably a feature requested by a large (potential) customer. I see no reason why MikroTik developers would suddenly decide to add another routing protocol (while the coding of the existing routing protocols is not finished) just by themselves. So sales has come by and said “we can sell 10000 routers when we have IS-IS”.

Similarly, when sales would come by and say “we can sell 100000 additional routers when we have IPsec VTI” it probably will be in the next beta.
As indeed, the underlying open source IPsec software already supports it, it is just a matter of writing the proper RouterOS configuration layer.
(unless of course they have forked the software 15 years ago and did not track the development, but I do not think that is the case as other “newer” IPsec features like IKEv2 got added in that timeframe)

yeah well, I’ve just switched back to a Fortigate 60F from my RB5009 and I’m not looking back.
Very sad but I was just fed up of the IPSEC implementation in ROS. Route based IPSEC is such a charm to work with!

I’m not considering putting ROS routers anywhere in the near future where I need IPSEC, not as long as routed IPSEC is non-existent in ROS.

Agreed.. IPsec without VTI is terrible.
I really don’t understand why it is not available yet. ALL VPN’s I use and manage ( about 2000, I work for some governmental agency ) are route based.

eur
Yeah, that´s a nice device, but that would cost any end user around 1k EUR with just the basic license.
The RB5009 comes for 25% of that price! Also the 60F has only 1 Gbps ports.

sure, that’s why I bought the RB5009 in the first place.
but it turned out that different features were more important than like having an SFP+ port.
also, I bought mine used for EUR 350. Also, you can get a 40F which is still as powerful (if not more powerful) as a RB5009 and that is obtainable well under 1k.

ok, this is it people, no plans but they’ll “consider it”.

bye bye for good for any edge routers, mikrotik…

Hello,
Thank you for contacting MikroTik Support.
At the moment there are no plans to change IPSEC functionality, thanks for your request we will consider such implementation.
Best regards,
Oskars K.

Yeah mine too, but they are GRE/IPsec which provides the same functionality. With MikroTik routers that works well. It is only the cross-manufacturer support that is a problem.

Joininig the request for the IPsec VTI feature. Needs as air.

Well, I tried again using a support desk request, but the status still is “At the moment, there is no plan to add this functionality,., but we will see if it can be supported in the future.”

Thanks for updating this post pe1chl. I’ve come across posts several times that you helped the community and me.

Where do you make this resource request? Is it open? Maybe the community will fill their box with requests. LOL…

I don’t know if I’m unique, but I always look at the changelogs of the beta versions and there’s never the gold feature. Maybe with the pleas they will listen.

A tip if you really need a VTI interface in your business: open a support ticket and describe a genuine use case that could motivate Mikrotik to move forward with developing this. Just posting in this user forum won’t probably accomplish much.

Well, as I wrote I filed it as a support desk feature request. Anyone can do that. It may be more effective than adding “+1” here.
Not as a business case, but it would help me to have this for our VPN tunnel to Microsoft Azure.
Now, I use a small dedicated Linux VM on our ESXi server, maybe I’ll try to make it a container.
But the configuration in libreswan is so trivially simple (and I think *swan also originally was the base for RouterOS IPsec) that I hope that MikroTik would at some time add it and save me an external IP, which is quite scarce in our /29 network.