Cisco ACS 5.3 multiple service selection needs for RADIUS Wireless PEAP & 802.1x Port Auth

[michael mearlon]

I use ACS 5.3.0.40.8 with TACACS+ servicing Device AAA and RADIUS servicing the Cisco Wireless environment for AD user access. How can I implement 802.1x with the current RADIUS implementation with hindering current wireless users or am I hindered due to the EAP-GTC in use with PEAP via RADIUS?

Sent from Cisco Technical Support iPad App

[maldehne · Accepted solution]

Generally speaking the EAP type is determined by the supplicant and the server

so if you have wireless client configured for EAP TLS and wired clients configured

for PEAP MSCHAP v2 , you shouldn't have any problem if you have an Access

Service handling RADIUS and having both types of EAP enabled and the identity

policy as well as the authorization is straight to the same target and level of access.

Cheers

-------------------------------------------------------------------------------------------------------------------------

Please Don't Forget to rate correct answers

[michael mearlon]

I have my answer now. I needed to go to the Access Policies > Access Services > Service Selection Rules and add a NDG condition to one of my RADIUS match rules.

Sent from Cisco Technical Support iPad App

[michael mearlon]

I have my answer now. I needed to go to the Access Policies > Access Services > Service Selection Rules and add a NDG condition to one of my RADIUS match rules.

Sent from Cisco Technical Support iPad App