I guess they could sell some of their time to configure it for you.  Engineering time.   Otherwise, it's part of your licence that you pay for.  The only question is who will spend the time to make the configuration change. ... View more

We had Meraki for 3 years and switched to FortiNet, and we still have home offices on Meraki. There is a learning curve as those things are 10x more capable and feature rich, but also more complex. They do have cloud mnagement as well, but if a device comes with gig ports, it's pushing  gig. I've been pushing ~300  clients through 2x 1gig uplinks with a FortiGate 60F (~$1000) without any problems. ... View more

That sounds right. I agree they need to just let you make the static routes needed.   They do have something called VPN exclusions now that might help in some situations. If only I could figure out a rule to exclude everything except a certain IP. Then it would be doable but a stupid way to do it. ... View more

A low comment says they were able to configure this, but did not test it. ... View more

Intel x86 CPU's are top secret information apparently. The smaller models are built using various models of SoC like Broadcom.   On the MX models I've pulled the cases off they have serial ports on the motherboard where you can watch the bootup sequence in plaintext, alternatively just pull the heatsink off and look. ... View more

LOL, that is a lot, Sophos can do as many as there are physical ports on the device (minus 1 for LAN and one for HA if you are using it).  I'm sure Meraki will move to more (3 or 4) but it may well only be on the newer MXx5 devices... ... View more

Thank you, this is exactly what we were experiencing. The MX record is associated with the 1:Many NAT and the O365 server on the outside is expecting to only receive from that IP, so it denies anything from the WAN IP of the Merak. I confirmed this from the headers in the email that was being sent as the source was the WAN IP of the Meraki. Thank you for the information. ... View more

I'm guessing EE have got IPv6 to IPv4 working properly then, which is good 👍 ... View more

Has anyone taken a look at the Meraki.com page today?   https://meraki.cisco.com/product-category/security-sd-wan/ ... View more

Hello,   as the new firmware is in Beta and doesn't support some features like multicast over LAN, Could you please tell me, how long does it take to get a productive version of MX16.x Firmware? We need to run anyconnect on our devices but as long as the firmware Beta version is, we can not use it in the production world.   Best Regards!       ... View more

You'll need to open a support ticket and ask them to enable the NO-NAT mode feature.  Then you'll see it. ... View more

I will retire my MX equipment before we see a VPN client.  I was a long time Cisco command line guy, made the jump to Meraki and this VPN client thing really bit me.  Who would have thought Cisco would charge this much for equipment and not provide a proper VPN client.         I will never recommend Meraki because of this, Cisco failed horribly on this piece.        ... View more

Also you can't configure IPSec vpn  between two MX if the WAN ports have private IPs. The MX will not negotiate IPSec unless the port has internet connection, the port status will show failure until it gets internet connection. Hence, if you have two sites connected via MPLS then you can't have VPN between them since the WAN ports don't have internet connection. ... View more

@DBesa  I sell / support both Meraki, ASA, and Sourcefire solutions for customers.  In your case I would have recommended keeping the ASA for VPN, and simply moving your primary internet traffic over to Meraki.   I have several customers that still maintain support on their aging ASA5515-ASA5525 firewalls just to provide Anyconnect VPN continuity to their user base, while they have upgraded to Meraki for the default network exit point.  It is very simple to point a few routes over to the ASA for Anyconnect and L2L VPN, while keeping the default route pointed at the MX appliance.  This provides the best of both worlds, easy cloud managed security with deep VPN solution offerings from the ASA.   Think of the ASA as the swiss army knife that you really don't want to be stranded on a deserted island without, while the Meraki is the sleek speedboat that gets you where you want to go in style.   Not to speak for Cisco too much on the matter, but I am sure that they are well aware of how quickly their ASA business would dry up if they supported Anyconnect on Meraki.  I also believe they would experience a massive load of support tickets on their cloud platform that they do not currently have to manage.   Anyconnect has an update schedule that keeps pace with Microsoft updates, while Meraki has a quarterly update schedule.  It is unlikely that an appliance deployed software package which requires frequent updates and supports thousands of different settings would be a good fit for a cloud managed appliance. ... View more