Bug #3660
closed
Captive Portal Idle timeout Pfsense 2.1.3
0%
Description
Using the value in Captive Portal idle timeout greater 60 minutes, connection does not expire.
Tested with 70 to 120 minutes, but does not expire. Notebook Client shut down to prevent connection attempt.
Disable MAC filtering parameter checked.
Using Captive Portal Integrated Freeradius (Base Openldap)
Files
Updated by Gilmar Cabral almost 10 years ago
Problem is related to time Last Activity as print attached.
Login as 07:46:12 and presented logout but time was 12:06:19 Activity
Updated by Gilmar Cabral almost 10 years ago
With my current time zone(gmt -3), session last activity is almost 5 hours ahead.
so I've tried to set my timezone to london (gmt 0) and for my surprise, last activity is earlier then start time.
Updated by Chris Buechler over 9 years ago
- Status changed from New to Rejected
issue as described isn't true
Updated by Gilmar Cabral over 9 years ago
It's true. Solution to the problem on the link below
https://forum.pfsense.org/index.php?topic=69606.0
Updated by Chris Buechler over 9 years ago
that's a problem inherent in what you're doing with squid and has nothing to do with CP itself.