cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1868
Views
0
Helpful
6
Replies

Web authentication WISM 2

maddalena.selis
Level 1
Level 1

Hi, I have an issue in web authentication with WISM 2 with code 7.0.220.

An user can obtain an IP address, type for example www.google.com and so he can see the the web authentication window. The user can login (I can see thet authentication status is YES in WLC) but after login process there are not redirection to www.google.com. In order to navigate users have to re-type www.google.com. Same issue with Safari (iPhone e iPad), Mozilla and Internet Explorer. 

I don't have that problem in WISM 1 with code 7.0.220.

Thanks in advance!

Maddalena

6 Replies 6

Viten Patel
Cisco Employee
Cisco Employee

Hello,

I would try using a different DNS server. You can quickly test if its a dns issue or not by doing the following --

1. clear the browser cache

2. either change the dns server info on the dhcp server or setup a new scope on the wlc (just for testing) and use a public dns server like (4.2.2.2 or 8.8.8.8).

3. once you do this your initial web redirect (to the login page) may break (just type in https://1.1.1.1/login.html). If after successfull login, the user does not get redirected, I would open up a TAC case. Yes do make sure you try multiple websites (it may happen that the redirect to a specific website may be failing.)

Stephen Rodriguez
Cisco Employee
Cisco Employee

try rebooting WiSM2 and see if that restores the redirection.

Steve

Sent from Cisco Technical Support iPhone App

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

Tony Davis
Level 1
Level 1

We put our redirect in a custom web-auth bundle... works great!  I help if you decide to go this route.

Thanks,

Tony

maddalena.selis
Level 1
Level 1

Hi to all,

we found our configuration problem: after users get authenticated, WISM2 dropped the traffic towards 1.1.1.1.

To  correct this, we modified the CPU ACL with explicit permit to and  from 1.1.1.1:443 because WISM2, due to different CPU architecture, treated traffic to 1.1.1.1 as  "management" traffic as soon as the user got authenticated. This does  not happen with WISM1 and WLCs where we don't need to explicit permit traffic toward 1.1.1.1

Thanks for all your helpful suggestions,

Maddalena

On what device did you apply this ACL?

On WISM2, where we use cpu acls to protect mgt traffic.

Thanks,

Maddalena

Review Cisco Networking for a $25 gift card