Bug #2752
closedCaptive Portal Last Activity isn't update anymore --> idle timeout just after login
0%
Description
Since version 2.0.2 some of our captive portal users are logged out suddenly after login. In radius accounting i saw an idle timeout. We have activated idle timeout of 1800 sec.
I analyzed the code of captiveportal.inc. Within the function "captiveportal_prune_old" idle timeout is checked by comparing last activity ($lastact) with current time ($pruning_time). I entred two log lines showing last activity, current time, login time and ip-address of user.
I found out that last activity (entrystats in table 1) isn't updated respective not deleted during logout. A restart of pfsense deletes the table but few minutes later next idle timeout is recurring.
The attached pdf shows the captive portal status page and two log entries of such idle timeouts (own analyze within timeout code).
Version 2.0.1 was OK. It must be something new. I updated via automatic update function. As quick measurement I had to disable ide-timeout.
Regards,
Erik
Files
Updated by Erik Ruedin almost 12 years ago
Next status update:
I reinstalled version 2.0.2 from scratch because I supposed that the update from 2.0.1 to 2.0.2 was broken and not properly done.
Bad news. Some users/clients (about 10 of 50) have no updated or cleared last activity. Therefore after login they serval thousands of seconds of idle time and the are logged out suddenly.
Unfortunately the captiveportal of 2.1 isn't running either. (after login the ip-address is written in table 0 instead of table 1 and 2)
Consequence: I have to switch-off captiveportal for the moment or I have to find a package of version 2.0.1 and reinstall old version again.
Updated by Jim Pingle almost 12 years ago
- Status changed from New to Feedback
Please try a 2.0.3 image, this appears to be one of the bugs addressed there:
http://forum.pfsense.org/index.php/topic,58203.0.html
Updated by Erik Ruedin over 11 years ago
Issue solved with 2.0.3 please close ticket.
Updated by Chris Buechler over 11 years ago
- Status changed from Feedback to Resolved
Updated by Fabio Faro over 11 years ago
i have two installation with 2.0.3 but the problem still exist.
i opened a new segnalation (3032)
thx