I have set up a new ISP dedicated line at one of our locations. The ISP has given me static IPs in the form of Public WAN and Public LAN. Can someone assist me with configuring my MX95 to function so that we can use the Public IPs addressed to us but keep the internal NATing that is already set up? I have set up the WAN connection on MX with the listed information and and able able to reach out to the internet; however, I would like to make use of the static IPs provided to us. WAN Information IPv4 WAN IP Address: 45.88.123.0 IPv4 CR IP Address: 45.88.123.2 IPv4 AR IP Address: 45.88.123.1 IPv4 WAN Subnet Mask: 255.255.255.252 IPv4 Default Gateway: 45.88.123.1 LAN Information IPv4 LAN IP Address: 45.33.105.72 IPv4 Subnet Mask: 255.255.255.248 IPv4 Usable IP: 5 *IPs changed for privacy ... View more

This is going to be a very specific question, but Meraki support has been giving me the run around without solid solutions, so I am going to ask here to see if anyone has any recommendations.  My company is cutting ties from a MSP managing our MXs (SD-WANs) at all our locations (networks). We purchased all new devices and licenses to replace our current set-up. The goal is to replace all our current devices and licenses owned by the MSP with these new devices and licenses owned by my company.  In addition, our MSP set our organization up as a per-device licensing model. We would like to switch to what the majority of users have, co-termination license model. From speaking with Meraki support, it is not possible to switch a an Organization, within an account, from a per-device license model to a co-termination license model, even if purchasing all new licenses for every device.  The solution posited from support is to create an identical Organization, configured the same as the current Organization, and migrate all the devices over. After having done this and labbing the transition, I have found that Meraki requires VPN set-ups between Organizations to be created as "Non-Meraki VPN peers" even if they are both Meraki MX devices. They are not able to use the AutoVPN feature between Organizations. The problem I run into with this is that we are hoping to slowly migrate our Organization over one network at a time, as our I.T. team is centrally located and cannot be at all locations within my company at once. This creates the main problem; the "Non-Meraki VPN peer" does not account for MXs that use dynamic public IPs, and therefore have changing IPs. We have a few locations that are not static IPs, and I do not want to lose connectivity when they switch IPs. Our sites have to be able to VPN with each other. I admit that this could come down to me not fully understating the IKEv2 ability to connect via hostname. I've read the KBAs but it still is not clear to me how to use Local ID and Remote ID. In addition, this can get very complicated trying to handle the two Organizations with same subnets not conflicting with each other.    Right now I feel stuck. I am not sure how to move forward with this migration. If anyone has any recommendations, I would greatly appreciate it.  ... View more

When I update the firmware of my Meraki MX100 SD-WAN Security Appliance from it's current version of MX 16.16.9 to 17.10.2 it seems to work fine, except for this strange issue. Any web search for a new website takes an unusually long time to reach. After the first time, however, any subsequent loading of the web site (or any site within the web site's domain) runs at normal loading speeds. I assume this is due to DNS caching.  I have tried updating to 17.10.4 and have experienced the same issues.  When calling Meraki tech support, they recommended me rolling back to 16.16.9 (which is what it is currently at). Has anyone else experienced this issue, and/or has found a solution to this? ... View more