Solved: Web authentication redirect page error

m.arienti · ‎02-14-2013

Hi,

I have a problem with WLC 7.3.112.0 web authentication: A client with IExplorer 10 associate and authenticate from correct redirected page of WLC, the problem born at the end of the timeout session time when client is de-authenticated. After its deauthentication it was associated and maintains his IP address but when I try to refresh for the second time the authentication page it wasn't opened.

Problem happened only with some client.

The workaround for the problem is to cancel the flag from required DHCP address in the SSID advanced tab.

Someone have the same problem with some client? Is it normal?

Greetings

Marco

David Watkins · ‎02-15-2013

Web Auth is a L3 security method, so when the session time-out expires and the client re-connects to the WLAN (most likely immediately); they are probably going to just send a DHCP Request (depends on the client), rather than full DISCOVER/OFFER, etc. It wouldn't be unusual that the client is disconnected and re-connects immediately maintaining it's previous IP address. They are going to pull an IP "before" WebAuth, so this is normal.

Does this appear to be isolated to IE10? Have you tried multiple browsers? When you have re-authenticated after being kicked off the first time, what Policy state is your client placed in? DHCP_REQD, WEBAUTH_REQD, etc?

Can you perform a client debug and attach the output capturing initial connection, authentication, timeout, deauth, followed by new authentication attempt?

>debug client

View solution in original post

David Watkins · ‎02-15-2013

Web Auth is a L3 security method, so when the session time-out expires and the client re-connects to the WLAN (most likely immediately); they are probably going to just send a DHCP Request (depends on the client), rather than full DISCOVER/OFFER, etc. It wouldn't be unusual that the client is disconnected and re-connects immediately maintaining it's previous IP address. They are going to pull an IP "before" WebAuth, so this is normal.

Does this appear to be isolated to IE10? Have you tried multiple browsers? When you have re-authenticated after being kicked off the first time, what Policy state is your client placed in? DHCP_REQD, WEBAUTH_REQD, etc?

Can you perform a client debug and attach the output capturing initial connection, authentication, timeout, deauth, followed by new authentication attempt?

>debug client

Saravanan Lakshmanan · ‎03-18-2013

When session timeout is kicked deauth is sent to that client and WLC removes the client from its database, After deauth the client must have associated immediately and had hiccup with dhcp handshake due to dhcp required however after struggle it should have redirected to the intended page.

maldehne · ‎03-18-2013

Please have the following outputs when the issue happens:

debug client < mac address of the client >

show client detail < mac address of the client >