Should be showing up like this:       ... View more

The reason I asked if you have any other problems is because a lot of DUP ACK's could be caused by a bad (physical) link somewhere in the chain. A bad wire, or a cable that's too long, crosstalk, ... But then I would expect you to see other problems on the site too, not just the site-to-site VPN. I'd try to test another protocol just to see if it's SMB specific.   Also, what bandwidth are the WAN links on both ends? ... View more

Are there any other issues in the site or is it just the site to site vpn? ... View more

Hmm. He didn't say the vpn on his Cisco is client vpn? In fact he didn't even say it was ipsec? ... View more

Depends on whether that's an outgoing tunnel I guess. ... View more

Okay, the behavior is as expected.   The clients are indeed sending their requests to the router 10.203.2.1.   The AP is sending requests to both 10.1.31.25 (I assume this is the internal DNS server) and 8.8.8.8.   @ccisco630 wrote:  I got another flurry of those errors at 12:12-12:13, and that is all for the day thus far. Do you mean that the errors are not continuous? From you first log I kind of assumed they were continuous as they  came in so close to each other.   It'll be harder to diagnose if they happen randomly and infrequently. Port mirroring could help to make captures for a longer time than the 20 min max supported by the dashboard. ... View more

It's a bit strange that the router gets DNS requests from the AP if the AP is not setup to use the router as DNS server.   From your comment about the clients getting their IP from the router over DHCP I take I conclude that the AP is in bridge mode, so those DNS requests can't be NATed client requests either.   My next step would be to do a packet capture on the AP's uplink and filter it for DNS queries going to the router to see what they are with wireshark.   https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Packet_Capture_Overview ... View more

Just checking to see if I understood correctly: So the clients get their DNS settings from the router over DHCP? And the router is setup to hand out it's own IP (10.203.2.1) as DNS server? The router itself is configured to use your internal DNS and 8.8.8.8? The AP is set to fixed IP settings? Or DHCP?   Can you check if your can ping your DNS server from the AP and also if it's name resolution actually works using the live tools: https://documentation.meraki.com/MR/Monitoring_and_Reporting/Using_the_MR_Live_Tool ... View more

Well the middle symbol is a router symbol, the right one firewall symbol. So it must be an MX, two for an HA setup. Not sure about the left symbol, maybe IPS or AMP?   But I see what you mean. ... View more

What are the DNS settings for the AP? Because I know it uses DNS for its cloud connection:   https://documentation.meraki.com/MR/Monitoring_and_Reporting/Alert%3A_This_device_is_having_difficulty_contacting_the_Meraki_Cloud   Is it possible that your router is handing out an IP address to the AP and at the same time it's own IP address as DNS server instead of your real DNS server or 8.8.8.8? ... View more

@AdamS wrote: That's awesome, I didn't find any in my search in October, is that picture from this year? Send a link so the brotherhood of switchmas may be born! I can't be 100% sure but I think it came from here: https://twitter.com/CaNerdIan/status/1074478844411895810   In any case it probably is from this year. Seems to be about 4 days old.     ... View more

@PhilipDAth wrote: Here is what I would do.  Start with the gaming device off.  Start a packet capture of all DNS queries.  Start up the gaming device, and then the game.  Stop the packet capture.   Now you have a list of the DNS names it needs to work.  Chances are one of them is used to login or verify that the game is legal and legit.  There is possible one or more domains used to start the actual game as well.   Now that you have these, create a firewall rule blocking these domain names using FQDN rules. https://documentation.meraki.com/MX-Z/Firewall_and_Traffic_Shaping/Firewall_Settings#FQDN_Support     I'm thinking you'll be finished the whole job in 15 minutes. That 15 minutes will be deducted from your paycheck though. ... View more

Thanks for the hunts @CarolineS!   I've been thinking of "making a wish" for a Kensington lock in the gnomes' jackets. Or would that be ingnomane?  ... View more

I love it! I love how you actually have them online. II reckon you have remote blinking mode from dashboard on?   Coincidentally, yesterday I saw a similar picture of another Christmas spanning tree. 😄     ... View more

I would try to access the local status page to troubleshoot the cloud connection problem further. I'm pretty sure it should connect to the cloud regardless of the license status. https://documentation.meraki.com/zGeneral_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page   Not sure if the LEDs are the same on the old MXs but that could give more info about what's wrong too: https://documentation.meraki.com/MX/Installation_Guides/MX64_Installation_Guide ... View more

@CarolineS wrote: @BrechtSchamp too easy this time!? Nice work! Thank you for finding the gnome! Well, maybe I just got lucky, but the clues do help. The hard part was the wait for you posting it though... I had my mind set on not losing the challenge again. ... View more

Yikes! ... View more

I FOUND THE GNOME! ... View more

@BrandonS wrote: @jdsilva wrote: It's a binary file. You cannot read it without knowing how to decode it 😞 That sounds like a challenge to me 😉 Neo, is that you? ... View more

For stacks there's more info here: https://documentation.meraki.com/MS/Stacking/Switch_Stacks#Replacing_a_Stack_Member ... View more

How much on the itchyness scale?   ... View more

As Philip already mentioned, make sure your Air Marshal settings don't see the Cisco APs as a threat.   For that go to Wireless > Air Marshal.   Either allow all rogue APs or whitelist the Cisco SSIDs.   Should be able to make it work. But it's not ideal. As you already mentioned real roaming will not work. And what if someone calls with problems connecting to the network, you'll have to figure out which network they're talking about first.   From a RRM perspective what Philip said also makes sense, if you mix them too much it will mess with the RRM algorithm. ... View more

Also, before anyone goes reaching out to Meraki support because they're missing that feature in the alerts page. It's only displayed when you actually have SSID's with self-registration splash pages. 😉 ... View more

Much will depend on whether the previous configuration was deemed safe. If it was it will just continue functioning as it was before the reboot. If not, it will rollback to the last known safe configuration and then continue functioning.   There's help page dedicated to this topic: https://documentation.meraki.com/zGeneral_Administration/Cross-Platform_Content/Behavior_during_Connection_Loss_to_Cisco_Meraki_Cloud   Take note that for MR there's a specific section at the bottom with more details regarding to operating in a "connectivity loss" state. ... View more