After upgrade CHR from 6.49.10 to 7.14.0 router unexpectedly rebooted on the end of the day.
CHR in VMware Cloud virtualization (ESXi 7.0 U2 / 7.0.2).
There were no crashes prior to this incident (in about 3 years of operation on 6.48.x - 6.49.x).
// SUP-146320

Although I don't see direct mention in changelog, but problem with IPsec with intermediate certificates finaly resolved in this version -_- Upd. If you are still getting an error after upgrade, then remove the root certificate, re-import, and correct tunnels configurations where this certificate was...

Just tested(via ProtonVPN) ROS 7.11.0 Stable on RB750GL and IPsec correctly working without intermediate certificate, although I don't see direct mention of resolving this problem in release changelog >_> Upd. If you are still getting an error after upgrade, then remove the root certificate, re-impo...

Just used the intermediate certificate... Thank you for posting this!

You're welcome!

Could you please contact us through support portal, we have fix available for this. Thanks

Create ticket SUP-120254.

There is no issues found when importing proton certs. Import of certificates is not(and never was) a problem, but is how RouterOS validate certificate chain. Previously, validation worked correctly: if there is a root certificate in system store, and the server to which the connection takes place t...

Here is certificate in DER and PEM encoding: ProtonVPN_IKE_Intermediate_CA_1.tar Right now I don't have time to conduct a test, so maybe one of the users will have time to do it before I get my hands on it myself :) Successfully tested on 7.9.1 with 2 installed certificates(IKE_Root_CA + IKE_Interm...

Sadly, Proton want me to downgrade rather than provide the intermediate certificate to verify if that fixes the problem. 1) Just curious: Was that response via support ticket or in public discussion(Redit & etc)? 2) I extracted Intermediate CA certificate from IPsec ISAKMP phase (IPsec debug ou...

Maybe its visible via CLI?

It doesn't look like.

And somehow it would be very strange, considering that other devices have corresponding items in the same GUI sections.

*) rb4011 - fixed reporting of current CPU frequency and changed default frequency to "auto";

What did I do wrong? : /

Or is it (for some unknown reason) only for rb4011 version without Wi-Fi ? o_O

After updating RB750Gr3 to 6.43rc11, I noticed that all port on local bridge became isolated to each other. Disabling HW offloading on bridge ports solve this problem, but I prefer to rollback to 6.43rc6 with HW offloading enabled.