cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3154
Views
3
Helpful
4
Replies

WLC Web Authentication Redirect

pepm
Level 1
Level 1

We've setup a WLC4402 to use Web Authentication. The WLC's own login-page is used. We're able to connect to the WLAN, so that works properly.

On the moment a URL is entered in a browser the titlebar states 'Web Authentication Redirect', which is good imho, BUT the browser tries to redirect to a routers IP-address (eg. https://x.x.x.x/login.html).

This IP-address isn't even mentioned in the WLC config, nor on the same subnet as the WLAN.

Any suggestions on how we can resolve this would be very helpful.

Rgrds, Martijn

1 Accepted Solution

Accepted Solutions

Stephen Rodriguez
Cisco Employee
Cisco Employee

Martjin, When you use webauth, the controller the client login is from https:///login.html. The virtual address of the controller, needs to be set, and it needs to be an unrouted address, usually we would recommend 1.1.1.1, and this needs to be the same on all of the controllers in a mobility group.

Also, when you do the webauth, the controller proxies the DNS request for the client. So what happens is, it uses the management interface to query DNS, and if the query comes back as valid, it will then let the traffic pass. If the query comes back invalid, it will deny the traffic and give the page can not be displayed error.

HTH,
Steve

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

View solution in original post

4 Replies 4

pepm
Level 1
Level 1

Added a trace file

sactoraymond
Level 1
Level 1

would that be the same IP as your WLC 's virtual interface IP? I think the default is 2.2.2.2.

Stephen Rodriguez
Cisco Employee
Cisco Employee

Martjin, When you use webauth, the controller the client login is from https:///login.html. The virtual address of the controller, needs to be set, and it needs to be an unrouted address, usually we would recommend 1.1.1.1, and this needs to be the same on all of the controllers in a mobility group.

Also, when you do the webauth, the controller proxies the DNS request for the client. So what happens is, it uses the management interface to query DNS, and if the query comes back as valid, it will then let the traffic pass. If the query comes back invalid, it will deny the traffic and give the page can not be displayed error.

HTH,
Steve

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

Thanks! Works like a charm!

Rgrds, Matijn

Review Cisco Networking for a $25 gift card