topic Depends on the idle and in Wireless

how to avoid the web reauthentication

sajad majeed — Mon, 05 Jul 2021 07:47:28 GMT

How to avoid the web re- authentication process for clients while going out of wireless network and enter into the network. Already changed the default session timeouts values

Is any way to keep the web session timeouts in client side or controller?

I cannot find any way to keep

Abhishek Abhishek — Wed, 28 May 2014 22:51:13 GMT

I cannot find any way to keep the web session timeouts in client side or controller.

You may want to change the

jmeachum — Thu, 29 May 2014 02:13:33 GMT

You may want to change the "User Idle Timeout" to 900 seconds (it is located in the Controller tab in the General section. I think that 900 seconds (15min) is the max for this setting and it has a default of 300 seconds. This will keep the clients in the WLC database longer when they leave.

If this is a very large network you may want to make sure you are not near the client limits of the WLC before you make this change.

John

HI Sajad,You must adjust Idle

Sandeep Choudhary — Thu, 29 May 2014 08:15:53 GMT

HI Sajad,

You must adjust Idle timeout as well as session timeout but max 24 hours and then he must reauthenticate, there is no other option in webauth.

Please check this link:

http://rscciew.wordpress.com/2014/05/07/timeout-setting-on-wireless-lan-controller/

Regards

Dont forget to rate helpful posts

How about sleeping client

Karel Navratil — Mon, 04 Aug 2014 22:02:45 GMT

How about sleeping client timeout?

http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-5/config_guide/b_cg75/b_cg75_chapter_010111.html#d88319e2058a1635

Clients with guest access

Venkatesh Attuluri — Fri, 22 Aug 2014 20:54:02 GMT

Clients with guest access that have had successful web authentication are allowed to sleep and wake up without having to go through another authentication process through the login page. You can configure the duration for which the sleeping clients are to be remembered for before reauthentication becomes necessary. The valid range is 1 hour to 720 hours (30 days), with the default being 12 hours. You can configure the duration on a WLAN and on a user group policy that is mapped to the WLAN. The sleeping timer becomes effective after the idle timeout. If the client timeout is lesser than the time configured on the sleeping timer of the WLAN, then the lifetime of the client is used as the sleeping time.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-5/config_guide/b_cg75/b_cg75_chapter_010111.html#concept_F70A46E44FFB41CA9C2A4FC60A81B0A2

The user has to re

sajad majeed — Wed, 08 Oct 2014 09:07:00 GMT

The user has to re authenticate again once going out and coming back to the wireless network .We cannot keep the session timeouts in the controller.

This will not solve the issue

sajad majeed — Wed, 08 Oct 2014 09:08:03 GMT

This will not solve the issue permanently

Depends on the idle and

Sandeep Choudhary — Wed, 08 Oct 2014 09:11:58 GMT

Depends on the idle and session timeout setting.

Check this:

http://rscciew.wordpress.com/2014/05/07/timeout-setting-on-wireless-lan-controller/

Regards

Dont forget to rate helpful posts

We try the session timeout

sajad majeed — Wed, 08 Oct 2014 09:18:27 GMT

We try the session timeout limits but this will not solve this issue permanently.

One thing we cannot keep the sessions when user is roaming(going out/coming in of wireless network)

No,Did you also set the ARP

Sandeep Choudhary — Wed, 08 Oct 2014 09:27:18 GMT

No,

Did you also set the ARP timeout setting.

I tried this and it is working in my case.

Lets say when i go for lunch at 13:00 in the canteen(Canteen dont have WLAN access ) and come back at around 14:00 and u wont belive it that i have connection.

Regards