Wireless Access

last person joined: 18 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Guest User Features

This thread has been viewed 0 times
  • 1.  Guest User Features

    Posted Sep 04, 2013 02:54 AM

    Hello Gurus!

     

    Yet another question :)

     

    Let's say that a user has connected to the guest SSID but goes idle for some time^

     

    1) How long does it take for the AP to figure that out? Is the value configurable?

     

    2) Once the AP has sensed that, can we configure it to logout the user and kick them back to the login session for yet another session (this is particularly important if we have bandwidth contracts configured. The user finishede the specified bandwidth and is sent to the login page)

     

    3) Can the AP kick out dead sessions and allocate to other users so as not to use up resources...more like dhcp lifetime

     

    Regards,

    fmo

     

     

     



  • 2.  RE: Guest User Features
    Best Answer

    Posted Sep 04, 2013 07:06 AM

    The setting you are looking for is User Idle Timeout and is a function of the controller.  This can be set globally under Configuration --> Authentication --> Advanced.    In later code versions, it has been added to individual AAA and Captive Portal profiles.  The idea behind the setting is for the controller to probe for the client when the timeout value is reached.  If the client responds (ie; is online, just not doing anything), the timer is reset.  If the client does not respond (offline/asleep/etc.), the session is terminated.



  • 3.  RE: Guest User Features
    Best Answer

    EMPLOYEE
    Posted Sep 04, 2013 07:06 AM

    @fmo wrote:

    Hello Gurus!

     

    Yet another question :)

     

    Let's say that a user has connected to the guest SSID but goes idle for some time^

     

    1) How long does it take for the AP to figure that out? Is the value configurable?

     

    2) Once the AP has sensed that, can we configure it to logout the user and kick them back to the login session for yet another session (this is particularly important if we have bandwidth contracts configured. The user finishede the specified bandwidth and is sent to the login page)

     

    3) Can the AP kick out dead sessions and allocate to other users so as not to use up resources...more like dhcp lifetime

     

    Regards,

    fmo

     

     

     


    1.  Please search here:  http://support.arubanetworks.com/KNOWLEDGEBASE/tabid/133/Default.aspx for the user idle timer

     

    2.  In general, that is what happens

     

    3.  If a client is using captive portal and it is still present, it will still consume an ip address, unfortunately.