Voucher Sync not working properly
-
The problem is still on built on Sun Feb 16.
I can also use one voucher of a client that connect to the master pfSense and the same voucher i can use on a client at the second or third pfSense.
Master pfSense:
Secend pfSense:
-
+1, expired vouchers just do not sync.
Also, I'd like to set up a dedicated user for the sync purpose (not admin) however all my attempts failed miserably due to nonexistent documentation on required privs.
-
I pushed some fixes which should help with this.
Can you try latest code from github or next snapshot?
-
Thanks, will test the next snapshot, the boxes are one week behind latest anyway. :-)
-
I have tested the build Sun Feb 23.
On the master pfsense i created new voucher rolls but the comment don't show:
After I put a voucher has expired on the master pfsense, they are still valid on the second pfsense
-
Can you try once more with tomorrows snapshots.
-
Test: 2.1.1-PRERELEASE (amd64) built on Tue Feb 25 08:50:01 EST 2014
I use a new voucher. On both pfsense is the voucher valid. (Status –-> Captive Portal --> Test Voucher)
But when I try to login on the captive portal page at the second pfsense the voucher is immediately invalid.
On the master pfsense is still valid.
-
But when I try to login on the captive portal page at the second pfsense the voucher is immediately invalid.
On the master pfsense is still valid.Hmmm, yeah, this is actually a whole lot worse than before, perhaps just revert it. :)
-
Did you try with new snapshots or not?
-
Yes
Snapshot: pfSense-Full-Update-2.1.1-PRERELEASE-amd64-20140225-0849.tgz -
Yeah, I tried with the Feb 25 snapshot. This actually is getting worse instead of better, claiming valid vouchers to be invalid is just completely wrong.
-
@ermal, can you look again? :)
-
Should be fixed for good.
At least now it works on my test environment.
Please test latest snapshots.
-
Thanks ermal, now it works fine!
But one bug left. :)
The comment field still empty. -
No problem with comment field. (Has also nothing to do with the original problem here which indeed has been fixed. Thanks.)