cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Restrict access to LAN

Here to help

Restrict access to LAN

We are trying to create a scenario where we can control access to our primary LAN depending on whether a computer or user is "trusted" or "untrusted". We have Active Directory, so by default any computer that is part of the AD should be trusted. In addition, we need to be able to add other computers to the trusted computers group (eg for consultants). If a computer is not joined to the AD, or is not explicitly trusted, then it should be untrusted. Untrusted computers should get Internet access, but no access to the LAN. We have an MX64 with advanced security license, and also Meraki switches and Wireless APs. We need to be able to do this for both wired and wireless clients. Is this scenario possible? Thanks all for your help!

5 REPLIES 5
Highlighted
Kind of a big deal

Re: Restrict access to LAN

Yes.  Ideally you would use 802.1x on wired and WiFi (can't do it on the MX directly).  You drop authenticated users into the main VLAN and other users into the "guest" vlan.  Ditto on WiFi (well rather, authenticated users can access the SSID and you use a separate SSID for guest users).

You will need to deploy the NPS server role.  There is quite a bit of work involved.

 

With regard to switches:

https://documentation.meraki.com/MS/Access_Control/MS_Switch_Access_Policies_(802.1X)

For WiFi you would use WPA2-Enterprise mode (this even has an NPS walkthrough for WiFi):

https://documentation.meraki.com/MR/Encryption_and_Authentication/Configuring_RADIUS_Authentication_...

 

Highlighted
Here to help

Re: Restrict access to LAN

Thanks Philip, much appreciated! This is RADIUS/NPS stuff is new to me, so trying to digest it all. Is my assumption correct that users would use their AD username and password to authenticate against the RADIUS/NPS server? If not, what username/passwords would they use?

Highlighted
Kind of a big deal

Re: Restrict access to LAN

Typically you configure PEAP for the outer layer and use MSCHAPv2 for the inner layer.  If you do that, and it is a Windows AD joined machine, it will authenticate automatically as the logged in user without the user having to do anything.

Highlighted
Here to help

Re: Restrict access to LAN

Awesome, thanks. Sounds like I got some reading to do!

Highlighted
Kind of a big deal

Re: Restrict access to LAN

+1 for what @PhilipDAth said.  RADIUS would be your easiest route.  You can add NPS to a windows server and configure 802.1x to send authorized devices to a trusted VLAN and non authorized devices to a guest VLAN on the Meraki side. 

Adam R MS | CISSP, CISM, VCP, MCITP, CCNP, ITILv3, CMNO
If this was helpful click the Kudo button below
If my reply solved your issue, please mark it as a solution.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.