Captive Portal Timeout no new Session - Cisco VPN Client

[sebastian]

Hi there,

I'm facing the following challenge.

We have various guest users being authenticted via the captive portal after that, they are using their cisco vpn client.

So there is only one session.

And because all traffic is routed to the vpn connection no new sessions would be established.

Our idle timer was 1800 minutes and after that the connection was disabled.

Any smart ideas how to handle that or is the only way to increase the idle timer?

#show user ip-user-mapping all type CP

IP              Vsys   From    User                             IdleTimeout(s) MaxTimeout(s)

--------------- ------ ------- -------------------------------- -------------- -------------

ip-address    vsys1  CP      username                  275            41399      

#show session all filter source ip-address

--------------------------------------------------------------------------------

ID      Application    State   Type Flag  Src[Sport]/Zone/Proto (translated IP[Port])

Vsys                                      Dst[Dport]/Zone (translated IP[Port])

--------------------------------------------------------------------------------

824354  ciscovpn       ACTIVE  FLOW  NS 

vsys1                                   

[reaper]

Hi Sebastian

the captive portal timeout is not related to any sessions the user creates, it's the time allowed for the user to use sessions until re-authentication is required.

If you need a longer time for your users to be available you would need to extend the idle time.

The only alternative to "auto refresh" the idle time is to enable cookies and give the cookies a much longer timer than the captive portal idle time, but these cookies would only work with an active browsing session. (these cookies would be used to re-authenticate in the background rather than having a login screen appear once the captive portal timer has expired)

regards

Tom