Better logging of security. Like the Cisco firepower (Because Meraki's Why it happened it weak) The ability to have unique keys per site. Security best practice 101 is to NEVER REUSE A PASSWORD. VPN Setup that does not require me to write an special rule to limit traffic to another site. IKEv2 Support.....(yeah so far your solution works but it is actually weak in its proposal areas.) I replaced an ASA 5505 with a Meraki MX65. So far I have not seen any major advantages to the MX65 EXCEPT webfiltering. The downside is I can't see true web traffic. Its funny they include this as a features however don't give you the ability to truely audit that feature.... on the firepower from cisco... and Barracuda web filter appliances I can see FAR FAR MORE. These were test out devices and so far Meraki is not living up to parts of its hype. ... View more

We have a ASA at our home office. I would like to be able to use a MX64(Remote Site 1) and MX 65 (Remote Site 2) to create a VPN tunnel back to our home office. I see that I can add a non meraki remote peer and I can get 1 site to connect up. However It seems that when I installed the second MX it has the options for the remote peer from the first VPN. The MX looks to be very functional in terms of the VPN usage we want however I now want to use another MX pointing back to my ASA. Maybe I am not understanding how the configuration works with these.... ... View more

I appreciate the suggestion. I am not looking for a different solution yet. If I were to go with another solution it would be additional Cisco ASA's with Firepower modules. ... View more