08-18-2011 10:16 AM - edited 07-03-2021 08:35 PM
I'm looking for a way to enforce some degree of .1x machine authentication against AD for wireless devices which do not have a robust supplicant and/or cannot join AD. We're using MAC Authentication Bypass (MAB) on the wired side, and a similar capability on wireless would be advantageous.
Can WLCs do MAB like a switch can? Alternatives? Ideas?
Thanks!
Solved! Go to Solution.
08-18-2011 01:14 PM
MAB on wired works, because if the device can't do 802.1x, it can fall to another auth mech, and keep doing so, until it his the Guest profile.
Wireless doesn't work quite the same way. For 802.1x you'd want the profile to be built prior to connection, specifiying the EAP type, cert if one is used, as well as credentials, whether cached from login, or a specified set. WLAN Supplicants can see a broadcasted SSID, and the user could click on it, to start to connect, but that could cause you more issues, than just using a GPO to push the wireless config, if they are domain devices.
As another option, I'd take a look at ISE. Granted it's a seperate piece, but it allows you to use device profiling,to determine what is connecting to the network, and then push policy as to what it has access to.
HTH,
Steve
08-18-2011 01:14 PM
MAB on wired works, because if the device can't do 802.1x, it can fall to another auth mech, and keep doing so, until it his the Guest profile.
Wireless doesn't work quite the same way. For 802.1x you'd want the profile to be built prior to connection, specifiying the EAP type, cert if one is used, as well as credentials, whether cached from login, or a specified set. WLAN Supplicants can see a broadcasted SSID, and the user could click on it, to start to connect, but that could cause you more issues, than just using a GPO to push the wireless config, if they are domain devices.
As another option, I'd take a look at ISE. Granted it's a seperate piece, but it allows you to use device profiling,to determine what is connecting to the network, and then push policy as to what it has access to.
HTH,
Steve
08-18-2011 01:52 PM
Thank you.
Funny you should mention ISE. Our local Cisco reps are pushing it too, especially since ACS5.x doesn't work as advertised.
08-23-2012 06:56 AM
ISE is the way to go, when licensing is no option. You can use a variety of functions to secure your WLAN properly.
We used Username/Password in combination with a Whitelist to enable a select few with private devices on the network. Worked like a charm.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide