Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi all, I am Betzaida P. I've been with Meraki since 2022 as an NSE. I'm looking forward to chat with other community members and collaborate on solutions!I enjoy playing the violin and running in my free time. Cheers,
Hi, This has been the latest update: We have determined that rule 1:1412 is generating false positives and the immediate recommendation is to whitelist it. The rule has been reviewed by our internal teams and will be removed in a future IDS/IPS rule...
The Snort version was updated to 3.9.6.0 via backend and triggered this. Engineering is aware and is currently investigating this. For now, whitelisting the rule is the recommended workaround. Wait up to an hour for the whitelist to take effect.
Hi @gabriellimacaitano,I would recommend adding a Layer 3 firewall rule to block traffic destined to 239.255.102.18 on any port and a Layer 7 firewall rule denying hostname "anydesk.com."You would still need to apply anydesk.com to the blocked URL li...
Hi @bridahlq, Here is a list of unsupported IPv6 features on IOS XE 17.15.3: https://documentation.meraki.com/MS/Cloud-Native_IOS_XE/Cloud-Native_IOS_XE_Overview#Unsupported_features_on_IOS_XE_17.15.3_with_cloud_configurationCheers,
Hi @guitbbb, I agree with @JamesT91, please open a case with Support to request your network(s)/org is added a checkbox on the Firewall page to enable/disable cellular failover rules. You may reference this KB in the case description so we're aware o...