We might also need to go back to IKEv1. In the new MX19.x Firmware i can see a lot of Bugfixes regarding Third Party VPNs - I hope the Fixes get backported to the MX18.x Firmware so I can try if a new 18.x Firmware fixes the IKEv2 Problems. ... View more

We seem to have exactly the same Problem. I also have a Case open (12167713) but no Fix/Workaround so far.   We remove and re-add the Network Tag on the affected Site-to-Site VPN Peer to get it going again for 24-48hrs. ... View more

Yeah might try to downgrade to IKEv1 and hope that this fixes it. Unfortunately the other Side is a Partner and not under our control or we would already have deployed a MX.   Let's see if Support comes up with a fix or workaround. ... View more

For us this is only related to one (of three total) IPsec IKEv2 Peers with a Single Network but this seems to have started with the latest MX 18.211.3 Firmware.   We tried running a Ping via our Monitoring System to the Remote Network to keep the IPSec Tunnel up - but no luck so far. After 1 or 2 Days max the Phase 2 part of the Tunnel always crashes and no Traffic is being forwarded. ... View more

Any news regarding this? We seem to be having the same Issue with a IPSec IKEv2 Tunnel with a FortiGate Peer on the MX 18.211.3. We have a Case open (12167713) but not a Solution yet.   We need to remove and re-add the Network Tag for the specific VPN Peer to get the Tunnel working again as a Workaround for now. ... View more

Same for us. Thousands of Events regarding the Snort Rule mentioned in the first Post.   I have switched to Detection instead of Prevention for now till this is fixed. So far "disabling" the IDS or putting it into Detection Mode only seems to fix the Problem. ... View more