ohhh.. that would be tricky.. you would need to use some DDNS service or something I would think.. it would be less than ideal but it would work.  ... View more

Digging even more into my dashboard I can see even my Z3's can connect to non-Meraki VPN's so I think you should be good to go! ... View more

I can't find anything saying this is not possible.. most of the back end across the Mx's are the same except certain hardware differences. I know it works for our MX100 so I see no reason it would not work with the MX84.   You can create Site-to-site VPN tunnels between the MX appliance and a Non-Meraki VPN endpoint device under the Non-Meraki VPN peers section on the Security & SD-WAN > Configure > Site-to-site VPN page. Simply click "Add a peer" and enter the following information: A name for the remote device or VPN tunnel. The public IP address of the remote device. The subnets behind the third-party device that you wish to connect to over the VPN. 0.0.0.0/0 can also be specified to define a default route to this peer. The IPsec policy to use. The preshared secret key (PSK). Availability settings to determine which appliances in your Dashboard Organization will connect to the peer. Note that if an MX is configured with a default route (0.0.0.0/0) to a Non-Meraki VPN peer, traffic will not failover to the WAN, even if the connection goes down. ... View more

I found this script and with some modification, I think it might be able to copy some basic configs into your Meraki switches... https://github.com/meraki/automation-scripts/blob/master/copyswitchcfg.py   How useful it will be I'm not sure because whenever migrating from a catalyst switches I've always rebuilt my Meraki switches from the ground up... I figure it is a good time to clean up any configs not needed and have a fresh start... let me know if this helps ... View more

Personly I would break it down even further to individual physical locations per network. If there needs to be a change to a location that is specific for that location it gives you the ability to do so... Also having the networks broken down to physical locations will also help with reporting and troubleshooting...  You can bind several networks together with a template or use cloning to make changes.... ... View more

It would also help to know your environment... Is this a Guest/Public network? Is the splash page mainly a TOS that the users need to accept? a little more information might be helpful... ... View more

@jdsilva you would need 2 different interfaces on different subnets with static routes to make it work IE having the core router perform the routing..  ... View more

Yes @Aaron_Wilson  This is exactly what I was thinking. ... View more

There is none that I know of.... it's mainly up to the device to detect when there is a captive portal requiring sign in.. like on android or iOS.. ... View more

Are your devices in DEP and do they have a supervised profile? If they are not the SSID setting will not be enforced.   WiFi WiFi settings can be used to push out a wireless profile to your managed devices. Some example use cases for this feature are: Providing an Internet connection for your devices, but do not want to explicitly provide the SSID name or credentials to the end-user. Pushing out WPA2-Enterprise WiFI profiles with 802.1X authentication (EAP-MSCHAPv2, EAP-TLS, etc.) This can be further configured with "Trusted Certificates" that you upload, utilizing the "Credentials" feature described below   ... View more

@jdsilva  That what I was thinking but that would require a 3rd MX... I wasn't sure if there was a way using static route statements to route the traffic through the CF then depending on the CF have a statement to route it back to the MX... It would be very messy and I think the idea of a 3rd MX in concentrator mode would be the cleanest.  ... View more

The article @Nash referenced lays everything out for you very well... but keep in mind this will be a cold swap... IE there will be some downtime. I think the key thing to do is bring up your MX100 and get it pre-staged and configured... That way you can minimize your downtime. Good luck and feel free to ask any questions you have. ... View more

I don't think this is posable but it really depends on how your network and Site to Site VPN is set up... Here is a good article about all the different configurations on the MX for your site to site VPN... https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Settings You would definitely need to configure Full tunnel (default route) but routing beyond that I'm not sure... hopefully this was helpful... ... View more

Finally got a chance to get back on the forum today and this is so amazing!  I'm so glad to help out and thank you, everyone. It was so cool to meet @kYutobi @Nash and look forward to helping build this wonderful community!  ... View more

It was great to meet you @kYutobi I had a blast this week as well and look forward to the ongoing friendships that were made this week. ... View more

just saying because of thats the only Meraki device that I have used it on... ... View more

I just ordered some for my MS120 and it works  ... View more

How are you Whitelisting are you doing it on the client page or via Group Policy? On the client page, I don't think whitelisting will whitelist for content filtering.. I believe it has to be done by Group Policy in Meraki.  ... View more

What about firewall rules? have any layer 3 or layer 7 rules been changed lately ?    ... View more

Are you blocking via content filtering? did you try whitelisting a single site then try to get out so said site? ... View more

Where have you whitelisted them on the MR or MX? ... View more

I'm in the middle of a long migration from my Cisco ASA's and Catalyst Switchgear and it's going very well! One really cool thing I just found out today in the ECMS2 (Engerning Cisco Meraki Solutions) class today. There is a script to import ASA configs to your MX. Really helps to streamline the process.   Meraki MX Converter - Import ASA config files and automatically adapt rules to the target MX. This script will parse through an existing ASA config and generate Meraki MX compatible FW rules. The script supports objects(network/service). It'll build iterative or multi-source/multi-destination L3 based rules. It'll then configure the target MX network with the ruleset mapping to the new interfaces." https://github.com/wifiguru10/Meraki_MX_Converter ... View more

YA i won!!!! ... View more