That’s good news! I’m going to mark GreenMan’s reply as the “solution” so other can more easily find it in the future. Cheers! ... View more

>We have noticed that when using real time conference software - Zoom and TEAMs, the audio quality and image is really poor,   I have seen this before a long time ago.  It was related to the firmware version.  I think there was an issue handling fragmented packets.   I agree with @cmr .  Go 18.107.9. ... View more

I didn't find a straightforward solution using Meraki MX since it lacks this feature.However, I previously managed this task with legacy Cisco ASA firewalls :). The workaround involves manually creating objects at the Meraki organization level for each CIDR and organizing them into object groups for each country or region, then setting up corresponding firewall rules. For instance, you can explore IP CIDR or range by country using resources like this example: https://github.com/herrbischoff/country-ip-blocks   Another consideration for the most secure approach is to eliminate this attack surface altogether and replace direct access with VPN connectivity. ... View more

We recently upgraded our MX250 HA pair to 18.107.5 and "touch wood" we haven't had any issues ... View more

out of interest what firmware version are you running? ... View more

This issue is no longer present. Back to the regular 3 categories: Stable, Stable RC, and beta. ... View more

Can you share the driver and version number that fixed your issue?   I'm having a similar issue. ... View more

we experienced a similar issue whilst we were performing a penetration security tests. The CPU on the primary appliance was becoming overloaded (as a result of the pen test), flipping to the secondary. Once the primary recovered it flipped back and the process repeated. May be worth raising a case with Meraki and enquire whether the compute in the appliances were being overutilized at the time. ... View more

We utilize Meraki Group policies and when we moved from MAC client addressing to IP we found that users we have applied the Meraki group policies dropped once they received a new IP address.   It was a pain adding Meraki Group Policies back to users all the time.   We ended up moving back to MAC client addressing from IP.  ... View more

I have the same problem. Someone at Meraki didn't think it through on having two stable firmware versions at the same time... ... View more

We also made the change last night and it rectified our issue. Worth mentioning if you are using "combined" networks, Tracking via IP is not supported. The network will need splitting first. ... View more

I already mentioned the issue. Workaround: rollback to MX 16 while waiting for their developer to fix it. ... View more

Interestingly Meraki have since requested we disable 802.11w on the associated SSID. Clearly there is some issue there! We will do this and perform further testing in an attempt to see if its a contributing factor to the issue. Thanks for the input ... View more

We have this issue as well.  MX450's acting as vpn concentrators in 1-armed mode running latest firmware.  The issue is actually the 'frames per second' table maximum of 500k is reached when scanning through to the branch locations.  When the FPS table is maxed it causes major performance degradation.  There's no solution support has provided other than to add more MXs and split up our remote auto-vpns to multiple concentrators to try and limit the impact.  We have about 150 branch locations. ... View more

Thanks you🙂 ... View more

We have reached out to them numerous time and they didn't had any answer except they wanted us to repeat entire scenario to examine which we are not sure how to replicate as wasn't something we triggered. To add salt over the injury they took 2 weeks to respond and now after 2 weeks all the IDS Alert and information is gone because that's what default policy is.. They just left us hanging in middle LOL ... View more

In a word no, not at the minute. The latest notes received on the case advise "During the call, I managed to establish that your MX has been running into a known issue that is currently being worked on by our engineering team." The roll back to MX16.16.6 addressed our issue. I was advised we should receive some more detailed routes around the cause. I will share these if received. ... View more

I supose it is or will be part of this https://community.meraki.com/t5/Feature-Announcements/ThousandEyes-Internet-Insights-Integration/ba-p/141403 ... View more