Does this show you :
[2.3.4-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: ps ax | grep 'prune'
15442 - Is 0:00.00 /usr/local/bin/minicron 60 /var/run/cp_prunedb_cpzone1.pid /etc/rc.prunecaptiveportal cpzone1
15733 - S 0:01.28 minicron: helper /etc/rc.prunecaptiveportal cpzone1 (minicron)
79162 0 S+ 0:00.00 grep prune
(show here what it show you, do not say : yes - don't paste images of what you see, copy-paste the lines)
[2.3.4-RELEASE][root@LAN-GW.lan]/etc: ps ax | grep prune
31149 - Is 0:00.00 /usr/local/bin/minicron 60 /var/run/cp_prunedb_client.pid /etc/rc.prunecaptiveportal client
31312 - I 0:00.18 minicron: helper /etc/rc.prunecaptiveportal asiakkaat (minicron)
31143 0 S+ 0:00.00 grep prune
So as you can see it is running. And i guess my problem really is that the DHCP lease time is less than captive portal idle timeout. Confusing that CP idle timeout is in minutes and DHCP lease in seconds.
But yeah, im ok with vi, ssh and cli. But not good with coding, so the php is too complex for me.
I used a portal idle timeout to great effect at a hotel. I only wanted them to be bothered by the portal once - even on a multi-day stay. I used an 18-hour idle timeout and a shorter DHCP lease time. I just made sure that the dhcp pool was large enough to accommodate the device churn through the property so the same lease was always available to give back to a device until they were long gone. As soon as the device left the property for 18 hours, the dhcp lease and the portal entry were both history.
I was thinking about the same thing. Only once bothered, perhaps every 24 hours.
I guess i just have to change the netmask to something larger first.
Thanks alot. I'll see how the tweaking of DHCP and idle timeout affects :)