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.
I use Duo on Windows server 2019. I use it for Microsoft RD Gateway and Microsoft RD Web.I haven't seen these Microsoft Remote Desktop listed in the products affected. Do I need to do anything/update these?
A while ago, I learned that Meraki MXs create an internal, implicit rule for 1:1 or 1:M NATs that completely bypass Layer 3 and Layer 7 rules.See here - https://community.meraki.com/t5/Security-SD-WAN/MX67W-blocking-country-IP-blocks-when-a-1-1-NAT-i...
I learned that any 1:1 (or 1:M) NATting supersedes Layer 7 country blocking. See here - https://community.meraki.com/t5/Security-SD-WAN/MX67W-does-1-1-NAT-forwarding-superceed-layer-7-country-blocking/m-p/257509#M57284Is there any way to use a countr...
(see below) Not sure if I can post links. I am having an issue with my MX67W where I am regularly seeing 'Disabled Gateway' in the historical data. The internet goes down during these occurances (which happen for less than a minute) and just recently...
Can someone confirm that there will be a difference in the red (offline) label depending on what happened?Just a Meraki cloud connectivity issue will show 'no connectivity' while a power outage will show 'reboot/no power' or something like that?TIA!
I just want to keep this updated to give it more visibility and make sure Meraki MX admins are aware that 1:1 and 1:M NATs completely bypass layer 3 and layer 7 rules, by default.There is an early access feature to enable layer 3 processing with NATs...
Meraki support replied with unfortunate news. 1:1 and 1:M NATs will still bypass any Layer 7 country blocking, even with the early access NAT exceptions function active. So, for country blocks, all the hundreds of CIDR entries would need to be added ...
