Why would they code it themselves when they use GPL Software, they can simply work with OpenVPN to integrate it, or do it all by themselves, Either way, that makes no sense, why reinvent the wheel when your wheel is worse than the original in performance and functionality.AFAIK, mikrotik doesn't use the default openvpn server/client software. All of those you mentioned, use the original openvpn software, thus having UDP is only natural, but for MT to implement it, they would have to re-code from scratch. If for them is more pain than gain, i can see why this decision has been made, but i think they just don't realise the benefits that they will get. Not sure also what is stoping them from using native openvpn server/client. Maybe a better explanation from MT would clear things up ?Mikrotik will not implement this. I asked 5 years ago.
They give a reason of openvpn being hard to develop, bad coding ang so forth, yet UBIQ has implemented it and PfSense has as well.
Mikrotik has nice features and neat stuff.
Except for UDP Openvpn with compression.
They give and excuse that it's too hard, yet it's not to hard because UBIQ, Vyatta, DDWRT, PfSense and so on have done it. So If they can why can't mikrotik?
Simple, Mikrotik frankly doesn't care to do the work their competitors have because they sell a lot of wireless and don't need to.
If thats not the reason, then they need better developers.
I can compile openvpn on many linux distros, freebsd, openbsd in a matter of minutes and yet MikroTik can't figure this out.
I wonder if mikrotik has Asked the developers of OpenVPN for help?
Epic Fail. Bonehead Maneuver. Exercise in Futility.
Hey MikroTik. If there is a complete logical explanation as to why you chose to create your own instead of work with OpenVPN to use what they have already create and have working well, please point me and everyone else to it, or post it.