Can you share the tunnel VPN configuration on AWS side? Thank you ... View more

Are you doing this from the local Mac or do you utilize anything for MDM? ... View more

Ah yes - I didn't notice that...  (I tend to just look at all the Community posts, when I have time - regardless of product set 🙂) ... View more

Switch access policies are another way of saying you want to use 802.1x port authentication.  The entire 802.1x protocol is built on the concept of using RADIUS.  It's fundamental.   Meraki makes it easier by effectively providing a RADIUS server for you to use with Meraki Authentication, otherwise, you'll need to stick to the standard - and put in a RADIUS server.   You can get free RADIUS servers, like Free Radius. https://freeradius.org/  There are also cloud-based RADIUS servers, like Jump Cloud. https://jumpcloud.com/lp/cloud-radius-beansprout  ... View more

Site to site works with both VIP and MX interface IPs ... View more

Yes, but you need to deploy a RADIUS server that authenticates the device by certificate through 802.1X. That's not going to be an easy project ... ... View more

I'm getting the same problem too. It started the night I upgraded to 16.   I was able to trace it to a file size issue. After connecting to VPN, I use robocopy to create an offsite backup. When it gets to a 4GB file, it disconnects halfway through.   After reconnecting to VPN and rerunning script, it will complete, but it means I have to do it manually now. @Meraki any ideas?? ... View more

@RaphaelL   I think I found solution. There was some old configuration it was blocking it. It's working now. You're absolutely right, S2S shouldn't affect client VPN. Thank you!! ... View more

@ww  and @PhilipDAth  that did the magic. Thank you.  ... View more

Yes ... View more

@PhilipDAth Agree with you it is much better than normal client VPN.  ... View more

Two options come to my mind: Configure the WLAN-Credentials for the Devices with Meraki SM and optionally also use SM Sentry for 802.1X with EAP-TLS https://apicli.com/2021/12/13/meraki-mr-802-1x-with-azure-active-directory/ ... View more

That make sense. Thank you @PhilipDAth . We'll see if we can upgrade to 16.15   16.15 has it's own issue for non-meraki site to site VPN ... View more

This is the info support gave me in my case.   "You could be hitting a known issue on our MX15 platform which can be addressed with a backend change. Please call us during a maintenance window so we can apply this backend setting. The problem you're seeing is that the device is rebooting and thus triggering a failover, what's causing the behaviour is flow tables being very large on the MX." ... View more

We have observed the issue after upgrading our MX400 (hub) on verison16.14. Post upgrade we had observed problem where the  MX looks to performed a software initiated reboot intermittently. we also make our spare MX as primary but It did not resolve the problem. At last we had to roll back to version 14.53 and device seems to stable.   Does any one faced same issue ? or 16.14 version has a bug ?   ... View more

I've done this on many sites.  Works great. ... View more

I think you're trying to do VPN chaining. Not 100% sure it is supported by Meraki ... View more

Hello @PhilipDAth    I've reached out to Fortinet support but it looks like Fortigate only allows to set local ID on aggressive mode only not in main mode.  I know in 15.44 aggressive mode is not allowed for site to site vpn tunnel , is it same case with 16.14 ? ... View more

Hi jay_b,   if you've used postman before, then stick with it for testing of the relevant calls and parameters they use.   with regards to powershell, i wrote the one posted in the link below and just used google and postman to help me.   postman for how the calls etc are formatted and what json results are returned and then google on how to create functions and subroutines,parse json data, use arrays etc in powershell.   rgds Gary (nealgs) ... View more

@AlexP  @jguidali  I am in same boat too. I've also contacted Meraki support but they didn't help at all. Not sure where to  get help from!! ... View more

I am also not much familiar with API but I can work on it if it is solution.    Does anyone have API solution ? ... View more

@cmr That makes sense. Thank you! ... View more

Here is the issue: the far end firewall (near end is your meraki) has an IP on the interface that receives the VPN connection (the WAN interface) that is not the Public IP that the near end/meraki is connecting to (this can be because the far end firewall is double-NATed, etc) you will put the interface ip of the far end firewall as the "Remote ID" on the meraki vpn config   for example   far end: ASA in Azure, with interface IP (WAN) of 10.20.30.40, and azure public ip "resource" of 55.66.77.88   near end: meraki, vpn config with public ip = 55.66.77.88 remote id = 10.20.30.40   Normally the remote id is assumed to be the remote public ip, but if the interface ip is not the public ip, you will have to specify the interface ip as the remote id ... View more