This is unresolved for me, so the proof has no pudding to be in yet, but we do have a solution in the works -- and it's firmware. Bear in mind that I'm using two Meraki MXs here, one of which is not participating in Mesh, so it's a standalone site, but we still have some users who need to get to stuff, so they use the remote site's client VPN. When one person connects to the remote site's client VPN, that person gets to use port 4500 for their connection, so local MX port 4500 is in use. The local MX tries to connect the next person by using a different port (PAT), but the remote site is only expecting to see 4500, and it doesn't know what to do with a client VPN connection that doesn't come from port 4500, and so only one person can connect at a time. I saw this in pcaps and then confirmed with Meraki support. Per Meraki Support, my solution is either to downgrade to 18.1xx and then upgrade to 18.2xx or to drop temporarily from multi-core (which apparently 18.2xx introduced) to single-core and then bump back up to multi-core after that. Both require a reboot. I hope this solves it for me (and for you, too!).
... View more
