Feature Request: Route Based VPN

[mimugmail]

You cant compare Linux/Iptables with OPNsense cause FreeBSD Vanilla also can achieve Route based IPsec

[dragon2611]

You cant compare Linux/Iptables with OPNsense cause FreeBSD Vanilla also can achieve Route based IPsec

I'm sure it can, but I happen to be more familiar with Linux and iptables than I am with BSD/ PF, where I need a route based VPN to land on a virtual router I tend to use Linux to do it.  It just so happens to be what works for me in that situation.

Also there was a typo in my previous post it should have said now not "know"

[pkernstock]

With certain users, it's always that one feature we don't have. We can't be good at everything all the time. :)

I know that many projects, OPNsense is no exception here, can not statisfy the need of just everyone around the globe. My intention was just raising a bit attention to this feature request - maybe for any priorisation for kind of roadmaps or so.

Probably crowdfunding-stuff would be great here. I'm an individual, OPNsense would be for private usage and I do not have enough resources to contribute tons of money to fund this alone :) (I would, if I could)

[Dasch]

Now, in 19.1.4 there is a feature called ipsec vti.
Is it possible to do a route based vpn with this?
An how to set it up? I read on pfsense tutorial that there has to be a /30 subnet for tunnel ip. But it is not possible to enter a /30 in the settings like it is mentioned in the tutorial (https://docs.netgate.com/pfsense/en/latest/vpn/ipsec/ipsec-routed.html).
Do you know how to do right?

[mimugmail]

https://github.com/opnsense/docs/blob/master/source/manual/how-tos/ipsec-s2s-route.rst
https://github.com/opnsense/docs/blob/master/source/manual/how-tos/ipsec-s2s-route-azure.rst