Bug #8421
closed
AutoConfigBackup v1.51 Option to Ignore Captive Portal Vouchers not working
Added by Bruno Pinto about 7 years ago.
Updated about 7 years ago.
Category:
AutoConfigBackup
Affected Architecture:
amd64
Description
I've been using pfSense in a HA configuration for a while now, and just recently started using the captive portal feature, so I don't know if this option was even supposed to work like this.
But every time a user logs into the captive portal, it syncs the database with the secondary unit, which is how it's supposed to work, but it also creates a config backup, and uploads it with the AutoConfigBackup package. So the actual config changes are lost in the list.
In the package config the option "Ignore Captive Portal Vouchers" seems to have no effect. While reading the description, it seems that it would be the option to enable the behavior I want.
I'm running pfSense 2.4.3 with AutoConfigBackup 1.51 on a Netgate Branded XG-1540 HA
- Assignee set to Anonymous
What is the reason you see for the backup? under Diagnostics > AutoConfigBackup > Restore I want to make sure I am seeing the same thing. This is what I see when I have an HA with synced vouchers. If you see the same message I have a fix that I can push up. I just want to verify this is the same reason you are seeing on your system.
(system)@172.xx.xxx.x: Captive Portal Voucher database synchronized with 192.168.xxx.x:xx
Thank you.
The message looks like the same from here
(system)@172.xx.x.xx: Captive Portal Voucher database synchronized with 192.168.x.x:443
- Status changed from New to Feedback
Fix committed b95ecbc9a9f4d87e77079dbf023ddb346460bdb1. It should show up as a package update for AutoConfigBackup when the next build cycle completes. It will be version 1.52 for ACB.
After a few days waiting for the package to show up on the update list, I went to look at the FreeBSD-ports repository and the commit was only deployed at the devel branch, and I could not find a way to switch branches for package updates in the pfsense Package Manager.
Is it safe to apply the patch directly on the firewall?
If the patch is not safe, are there any resources you could point me to get the devel branch working?
It should show up for 2.4.3 users momentarily.
I can now confirm the package is available for 2.4.3 and the fix works as expected.
Thank you all for your time.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF
Updated by Anonymous 
Updated by 
Updated by