CaptivePortal users with voucher didn´t disconnectet after time is ended.

valshare

Hi,

i have the problem that the user didn´t kicked out when the voucher time is ended. Only if i run /etc/rc.prunecaptiveportal from the console the ended vouchers will kick.

Same as this topic http://forum.pfsense.org/index.php/topic,37636.0.html

In Status > Captive Portal -> Active Vouchers the Voucher is not shown but in Active Users the voucher will show.

catpiveportal.db shows me:


[2.0.1-RELEASE][root@pfsense.xxxxx.local]/var/log(20): cat /var/db/captiveportal.db | grep 5879934662
1360147977,24,10.255.255.49,88:53:2e:af:xx:xx,5879934662,f5ad8bce6a93a309,,91440,,0

minicron shows me:


[2.0.1-RELEASE][root@pfsense.xxx.local]/var/log(23): ps aux | grep minicron
root   18574  0.0  0.0  3316   164  ??  Is    8Jan13   0:00.03 /usr/local/bin/minicron 240 /var/run/ping_hosts.pid /usr/local
root   19064  0.0  0.0  3316   164  ??  Is    8Jan13   0:00.00 /usr/local/bin/minicron 3600 /var/run/expire_accounts.pid /etc
root   19451  0.0  0.0  3316     0  ??  IWs  -         0:00.00 /usr/local/bin/minicron 86400 /var/run/update_alias_url_data.p
root   51291  0.0  0.0  3524   984   0  S+    1:22PM   0:00.00 grep minicron

jonallport

First thing to check - make sure your DHCP lease time is LONGER than your CP timeout (idle or hard)?

I used to see an ever increasing number of logged-in users because mine was less - CP users never expired!

jimp

If you're using 2.0.2, that's a known issue there, try a 2.0.3 image:
http://forum.pfsense.org/index.php/topic,58203.0.html

valshare

Hi,

i use 2.01 because of know bugs in 2.02 and will wait what 2.03 will bring. Leasetime in dhcp is 7 Days. Idel and hardtimeout in CP didnt set. Now i use /etc/rc.prunecaptiveportal in cron as workaround.

jonallport

Just catching up with some replies….

You've said that you dont have Idle or Hard timeout set. That's the problem then:

From the setup:

Idle timeout minutes
Clients will be disconnected after this amount of inactivity. They may log in again immediately, though. Leave this field blank for no idle timeout.
Hard timeout minutes
Clients will be disconnected after this amount of time, regardless of activity. They may log in again immediately, though. Leave this field blank for no hard timeout (not recommended unless an idle timeout is set).

There's nothing to tell the CP that the users should be booted-out. At least set an idle timeout of (say) 30 minutes.

valshare

Hi jonallport,

thanx for answer but you are wrong. Minicron calls the /etc/rc.prunecaptiveportal script and that check if a voucher has a timeout. I start /etc/rc.prunecaptiveportal now all 10 minutes per Cronjob.

Valshare

eviltrooper

where did you add this script?

minicron says nothing to me.. i only know cron.