11-06-2012 07:05 AM
On a controller running 184.108.40.206 with an 802.1x ssid configured, I have clients showing up as auth type captive portal. No captive portal is enabled. This in turn creates troubleshooting issues with the help desk while using airwave because the auth type does not show correct information.
11-06-2012 07:10 AM
Airwave is even more inconsistent than the controller. Airwave shows 802.1x clients as EAP, Web Auth, and WPA all on the same 802.1x network.
I think the issue stems from the controller, as it shows the same clients that are on the 802.1x network as being auth'd by Captive Portal, which is incorrect.
11-06-2012 07:16 AM - edited 11-06-2012 07:17 AM
Wait... The auth is showing up incorrect on the controller? Please open a support case. I am not sure under what circumstances that would happen.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base