Hi @words 

Thanks for posting in our business forum.

I cannot rule out the possibility that this is a config issue if you don't paste the config of the other site.

I am not seeing problem notifications recently about the IKEv2.

oops yes, I should have posted the Meraki side, here you are

Basically, I'm not changing any of these, just changing from IKE1 to IKE2 on both sides. Once I do this the VPN tunnel no longer connects.

Hi @words 

Thanks for posting in our business forum.

Port mirroring and Wireshark. Need to see the negotiation.

How to capture packets using Wireshark on SMB router or switch

How to Use Port Mirror to Capture Packets in the Controller

  @Clive_A the thing is, it doesn't even try to connect, I check the log on both side when I switch to IKEv2 and nothing, no attempts made..

Hi @words 

Thanks for posting in our business forum.

For real? Did you verify this by Wireshark? If I don't have any details from you, just a single line about it, you said it does not work, I don't really have a clue or suggestion for you.

I cannot send a single line to the dev and ask them in this way. This is not proper and wasting their time.

Fact should be, regardless the compatibility or any other possible reasons, the IPsec should initiate anyway. Have you verified it it does not even send the very first IPsec packet?

  @Clive_A thank you, this fixed the issue.

Is this an error in the particular firmware I'm using or in general?

Hi @words 

Thanks for posting in our business forum.

words wrote

  @Clive_A thank you, this fixed the issue.

Is this an error in the particular firmware I'm using or in general?

Omada shares the same concept in VPN configuration. So, it should be a generic problem with the Meraki. Not sure how Meraki system works but seems the test team Wireshark found out the Phase 1 did not get through. So, usually, it is a key exchange issue.