Captive portal and idle timeout
Idle timeout set to 8 hours, dhcp to 24 hours.
What causes CP users not to timeout at all?
Even if DHCP leases go up and down, CP users only go up.
Idle timeout is the duration of zero traffic on the CP entry at all. Even so much as a DHCP release/renew or an ARP is enough to reset that timer.
It is essentially used to see if a device has completely left the property. At that it excels.
If DHCP release or renew is enough, why is there about 25% more CP users than dhcp leases? Seems like the CP user graph is just going up, but DHCP is fluctuating.
Gertjan last edited by
If DHCP release or renew is enough, why is there about 25% more CP users than dhcp leases?
I have a idle time : 60 minutes and a hard time auto : 6 hours - DHCP default ease time 86400 seconds or 24 hours.
I know the idle-timer works : people leave the place, so "ghost-traffic" can't be possible.
The hard timer is just a safety net.
Seems like the CP user graph is just going up, but DHCP is fluctuating.
Every wifi device that joins your network takes a DHCP lease whether they go through your portal or not.
The pool size needs to be sized to accommodate your device churn and your lease times and your portal timeouts, hard or idle.