Meraki

PhilipDAth · ‎Mar 14 2022

You can restrict access of a VPN user by applying a group policy to the VPN user, and putting whatever layer 3 firewall rules you want in there. https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies

Ryan_Miles · ‎Feb 25 2022

You should also set the L3 firewall policy to deny Local LAN. Otherwise the guests could route to the other subnets. https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/MR_Firewall_Rules

Chris_Watkins · ‎Feb 25 2022

I still have multiple MR16's and 1 MR18 with this issue of nothing will connect until they are rebooted, then they work fine for a few days. We've been manually rebooting them a couple times per week for over a year, but it's a royal pain. Is it possible to revert the firmware only on the 16's & 18's and keep the newer firmware on the newer AP's? How do I get the older firmware?

cmr · ‎Dec 9 2021

DNS server forward lookup (host or cname) is pointing to a public IP, DNS reverse lookup (pointer) is pointing to a private IP. What DNS server is the device using and can you see the entries there to confirm?

Chris_Watkins · ‎Dec 8 2021

My subnets are not the same, so I don't think that is related. Thanks though

Meraki

Community

About Chris_Watkins

Chris_Watkins

Community Record

Badges

Re: I want to restrict 1 VPN user to 2 IP addresses How can I do this?

Re: How to make MR AP's invisible to MX reporting?

Re: No clients can connect periodicly (MR18)

Re: Client VPN connected but can't do anything on LAN

Re: Client VPN issue - cannot connect to my servers