The OVPN service is unstable, and it will cause a Kernel crashes after 2,3 hours of uptime.
SUP-96432

Observed this also here on a heX S. Version 7.7 ran flawlessly for weeks without any interruption, but 7.8 is an instability improvement concerning OVPN. :-(

Regards,
bronco

...five years after the first post in this thread and still no band steering for wifi. Does development still happen at Mikrotik generally or is there only bug-fixing on a daily basis? Hoping that the clients will do a correct selection of the wifi band to use leaves the hands of the administrator b...

Ok... thanks. Understood. But I said about UDP. It is one of the most important feature in v7....
Still not working in any v7 version....

So we can sum it up: v7.2 kills OVPN server functionality entirely, UDP mode is still not working and TCP mode isn't working anymore!

Hi there, OpenVPN is not working anymore - log: 21:24:37 ovpn,info ovpn-out_1: initializing... 21:24:37 ovpn,info ovpn-out_1: connecting... 21:24:38 ovpn,info ovpn-out_1: using encoding - AES-256-CBC/SHA256 21:24:38 ovpn,info ovpn-out_1: connected 21:24:38 ovpn,info ovpn-out_1: terminating... - expl...

Thank you chaos74, that was one of my intetions when starting this thread. And MultipathTCP is of course not limited to LTE use only, you can use it for any kind of network media link. Unfortunately it seems that nobody at MikroTik takes any feature requests seriously (as we can see e.g. in the Open...

We all need full functional OpenVPN ... m.b. with special extension card, is ok .. but is needed :) Some boards like the hexS already even have more crypto hardware accelleration than supported by Mikrotik software. So there's no need for extra hardware, just more source code has to be written or r...

+1 SHA256
+1 UDP

Hello mrz, would you please be so kind and share your knowledge with us. What is the reason, that currently there is only hardware encryption for IPsec and not for the other cryptographic stuff? Currently there is specific reason for this. maybe in the future you will see HW encryption not only for ...

Hello msatter, nobody ever mentioned ECB, therefore AES-256-CBC would be my preferred cipher, I totally agree with you in that point. I also agree with you that AES 128/256 is the same algorithm for IPsec and OpenVPN, but according to MikroTik's datasheet for the hEX S, encrpytion offloading for IPs...

OpenVPN uses as OpenSSL as a cipher library for several reasons, therefore the mentioned OpenSSL encryption engine should speed up OpenVPN (ovpn), cause crypto hardware engines usually are much faster than plain software-based algorithms. What do you mean by "OpenSSL encryption"? What ciph...

Hey mada3k,

I totally agree with you, but Mikrotik states only that there is IPSec encryption accelleration (compared to the datasheet of hEX S),
so I assume that there is no OpenSSL hardware encryption engine support

Greets,
bronco

Hello, the crypto engine of the MT7621 chipset (used for example in the hEX S model) supports by far more than only IPsec. According to the SDK for the MT7621 chipset there is even OpenSSL support via an OpenSSL engine that is already available in the SDK as a kernel module (look at page 215 and fol...

I wonder which set is smaller:
MPTCP-enabled sites
IPv6-enabled sites
(probably the first one)

You're probably right, but I think the comparison doesn't really match, since MPTCP's goals are in parts different from IPv6'...

What you're thinking about is pretty much an entirely new thing which would use MPTCP as part of its solution - namely, that it would silently terminate a tcp socket locally in order to originate a new mptcp stream outbound, and then forward the data between the two sockets transparently. In fact, ...

Is there anything in the specification that allows a NAT router to silently create multi-path TCP sessions to some remote host which supports it, but bond them back into a single vanilla TCP stream for clients? MPTCP handles TCP connections transparently, the application using the TCP stream doesn'...

Hello,

is there a chance to add Multipath TCP according to RFC 6824 in a future version?
There is already a linux kernel refernce implementation available: see http://multipath-tcp.org/ and https://github.com/multipath-tcp


Best regards,
bronco

You can still try to load the PPP interface by going into the /port firmware menu and set the ignore-driect-ip-firmware to yes and reboot the router.

Hello uldis,
thank you very much, I'll try that

Regards,
bronco

i suppose the firmware of your ZTE MF823 is uncompatible with the RouterBoard 433GL. Hello Mobicell, this is a pitty, since the ZTE MF823 shows up in the mikrotik wiki in the section of supported 4G devices. :? Therefore a little note would be cool so that other users won't rush into this anymore.....

That's absolutely right, you can get some informations this 'fetch' call /tool fetch url=http://192.168.0.1/index.html#status but unfortunately I don't see the advance here in comparison to browsing the status page of the lte usb stick with my favourite web browser directly. There seems to be no way...

RouterBoard 433GL, RouterOS 6.23 with ZTE MF 823 LTE USB stick Hello guys, with a few manual tweaks I managed to get my lte usb stick running (using the dhcp client for the lte device, removing the sim pin or feeding the sim pin via the usb stick web interface (sic!)). All the ip stuff works pretty...