VOULCHERS RECHARGE ITSELF AFETR USE
-
I INSTALL PF 2.0 BETA1 when i generate voulcher for example 60mins when the mins elaps the client will enter the same code again and it will start from 60 mins again, i ve deleted many voulcher and generate another one yet it is still happeinig is there a way to stop this, or will the recent snapshop correct it? please help me
-
BETA 1 is extremely old. Please try something more recent.
-
thanks for your advice, but if i do an upgarde from gui, will it ratin my setting as well as upgrade the pf box, or will my settings be lost. i would want to to retain my settings. pls advice, what is the different with upgrade and clean installation. for a better result as regards to voucher recharging itself
-
An upgrade will keep your settings, but you can always make a backup to be safe. Go to Diagnostics > Backup/Restore and download a backup.
If you are on beta1, it is likely that auto update is broken on your snapshot. You will need to do a manual firmware update by downloading a snapshot full update file to your PC and then applying it under System > Firmware.
An upgrade should be fine for what you are trying to do.
-
i have upgraded to 2.0-BETA4 (i386) built on Sun Oct 3 23:44:55 EDT 2010 FreeBSD 8.1-RELEASE-p1. yet i still have the same problem, once the system pfsense reboot all active voucher will start from the bignning again, it is suppose to continue from where it stopped, eg if a user have 60mins and have used up to 55 mins and unfurtnatly the power goes off and the pfsense system reboot, when the user log back in it will start from 60 mins again, please how do i correct this it is really affecting my setup.
Thanks in advance
-
Put a UPS on the pfSense. pfSense needs to write out the voucher database on reboot.
-
I have seen this small issues with CP on pf 2.0 betas. Will be great to have a DB for CP and used to save all the voucher info, if we lost energy or need to reboot will not matter because he will know the last state of the system(if the db is in good shape first).
I know we cannot run MySQL or PostgreSQL in a FW but a small Db like berkeleydb is more light right?
Or what options could be done to help CP be more stronger this will be very useful for me && others I think, cheers :P
-
You can push it through some bounty if you want.
-
We are going to try this, hope some have something to test, thanks!!!
-
am highly interested in knowing the final solution to this.
-
It'll be added to the periodic backup of other files. http://redmine.pfsense.org/issues/1087
-
Please test recent snapshot. Jim committed this.
http://redmine.pfsense.org/issues/1087
-
Someone else reported a foreach error in the voucher code. I backed mine out because Ermal already had code to do that. He committed a few fixes to his code and it was supposed to be working, but may still have a couple bugs.
-
i think i was able to figure out the problem, the voucher save interval is by default 300 mins, which make it impossible for the pf sense to save the current minutes the clients have used if the pf is not up for 300mins so setting the time to something like 3 or 4 mins will save the voucher used time 4 mins after the client logged in, even if ur pf reboots after 10mins the time will still continue from were it stooped, for example a client bought 1hr and used 20mins and there is power outage the pf reboots, the time will continue from 40mins. but note that the time is continuous and non stop even if the clients logs out, is there anyway that can be corrected so that when the clinets logs out the time stops.
to make the change goto service: captive portal: voucher: (save interval) default 300 mins
-
No the time is not continuous it will keep the time until you re-logon.
Please provide examples for this claim.
-
i will send a screen shot of logged out voucher
-
@ermal:
No the time is not continuous it will keep the time until you re-logon.
Please provide examples for this claim.
Does this mean you can stop the clock on vouchers to save time remaining? Unlike the experience of this poster? http://forum.pfsense.org/index.php/topic,31744.0.html
-
Does this mean you can stop the clock on vouchers to save time remaining?
that's how it works, there are no other options (unless you're on embedded and power cycle the box before its save interval hits).
-
hi there.
i am on pfSense 2.0-BETA5-pfSense (i386) still the same the voucher time does not stop even the user has logout.
A user with 30 minutes voucher time and logout after 10 minutes, when the user comes back after 20 minutes the account is already expired. It is supposed to be the user still can login because it has a 20 minutes remaining.
Hope this feature would be included in the next or future release.
regards,
sarhento
