Does anyone know how the Keep Alive works for captive portal, specifically in situations where you do NOT preserve the portal after login? Is it some kind of ping against the client? Is it just a check against the packets flowing through XG to ensure the client is still sending? I'm trying to understand the following:
- what is a "session" in this context (web traffic? any traffic? continuous traffic?)
- what process checks (and what is it checking) to keep a session alive
- how do I kill one of these sessions
Thanks,
Gary
This thread was automatically locked due to age.