Packet Capture Overview Change: Added "IPSec VPN" description. This is huge - always missed not being able to packet capture on NMVPN tunnels! ... View more

Ah that will be the difference then. 99% of our deployments will have the public IP directly on the interface. ... View more

That's strange, I've just looked at a few different Orgs and for MX devices those 2 columns are all displaying the devices correct WAN 1 and WAN 2 IP. ... View more

What about if you add instead the Uplink IP (Port 1) and (Port 2) columns? ... View more

Organization > Overview > Devices (tab) > Use settings cog to add 'Public IP' column   I believe this should give you a view of what you want. ... View more

What exactly do you mean by "all IP ranges configured on the dashboard" ? ... View more

Yes, latest here: Release 1.54.0 · meraki/dashboard-api-python · GitHub ... View more

To provide an update, after troubleshooting with support they were seeing the first request go to the desired nameserver, but not subsequent subdomain queries. After they checked internally this is apparently intended behaviour and the wildcard examples in the API documentation is just extremely misleading. ... View more

How is this still the only place that 18.212 exists 🤣 ... View more

Sounds like it! I have some running IOS-XE 17.12.3 and they work with the config history. ... View more

There is config history 😊   Configuration History - Cisco Meraki Documentation ... View more

Not quite sure why you would give yourself this headache and instead just deploy it in routed mode from the start? ... View more

Using Tags to Manage MR Access Points - Cisco Meraki Documentation   We have used it in the past to change the VLAN tag an SSID uses. See above documentation. ... View more

Congrats to the winners! ... View more

Definitely do it this way otherwise you need to faff around and disable WAN 2 on the Spare, strip out WAN 2 credentials from the Primary, reboot, turn around and touch your toes, hop on one leg 3 times and then it will let you add in the VIP on WAN 1 again. 🤣 ... View more

I can see it now, thank you! ... View more

I FOUND THE GNOME! Solved: rename camera - The Meraki Community ... View more

I've got one step further, in that there is a second API call required to then bind the split DNS profile to a network: Create Organization Appliance Dns Split Profiles Assignments Bulk Create - Meraki Dashboard API v1 - Cisco Meraki Developer Hub   Alas it still didn't work and support were unable to help due to: "As this feature is still in its early stages of development and we currently do not have any documentation surrounding the requirements for the feature we will need to await later releases of the feature from our development team."   I will wait some more months and see what happens.   ... View more

Thank you @Caleb-Engle! 😀 ... View more

@Hannah-C wrote: Alert Config and Notifications Change: New article.   Is this 'Configure alerts' button/feature available now? I do not see it when I am navigating to the Organization>Alerts page under our Org? ... View more

Weird. Can they link to some documentation that describes this behaviour? Having ignoring the flow preference rule? ... View more

Documentation states the following: "Clients will send DNS requests to the LAN interface of the MX, which will then proxy those requests to the DNS server(s) configured for its primary Internet uplink."   So, unless you set WAN 2 as the primary uplink then clients using a flow preference to use WAN 2 will actually be using WAN 1 DNS.   Alternatively, you can change DHCP settings and set your own preferred DNS servers to the clients (e.g. Google or Umbrella), rather than using the configured uplink ones. ... View more

Nice, good find! Now we just need an in-built alert for when these system resources go over a certain threshold... ... View more