We aren't using IKEv2 at the moment, but when we last tested it the system only would work for a single subnet behind the MX. You couldn't include multiple VLANs in the IKEv2 VPN. Sure you could configure it - but it only worked for a single subnet.
I am specifically posting my experience with Meraki Support and Meraki latest "Stable" release 15.42.1
I upgraded our "X network" MX box on this sunday at 4.30pm PST.
To start with, it's been a very poor code quality since Meraki released 15.42 and 15.42.1.
Taking some packet captures, revealed that there is connectivity and routing issues between Site-to-Site Meraki peers, so while on one location client VPN, you cannot access the resources of the another location, there are intermittent packet loss.
Since the same day we started experiencing the connectivity issues in our Client VPN. These are the behaviours.
1). I connect to our "X network" client VPN on Meraki. Connects fine. Then within one minute the VPN disconnects automatically with no error message nothing.
2). I connect to our "X network" client VPN. Connects fine. No internet works on the VPN, internal and external. I can see packets going out, but no return traffic.
3). I connect to our "X network" client VPN. Connects fine. Internal traffic does not work, external traffic works.
4). I try to connect to our "X network" client VPN. It gives me Authentication failed for the same exact credentials that are saved in my VPN profile which was previously authenticating without any issues.
I have downgraded the "X network" MX box on 14.53, and now everything works fine. This happened on both 15.42 and 15.42.1.
Same experience here as well. Meraki tech support is getting worse these days. You open a case, they ask you to call the support, and then if we wait for 30 to 45 mins to get someone, they complain about high call volume.