Bug #12916
open
pfBlockerNG-devel cron job does not trigger xmlrpc sync
Added by Marcos M over 2 years ago.
Updated over 1 year ago.
Description
Tested on pfSense 2.6.0 and pfBlockerNG-devel 3.1.0_1
pfBlockerNG-devel option "Enable Sync" with "Sync to host(s) defined below" selected.
Verified by checking secondary settings after each step.
When the cron job runs (either scheduled or from selecting it under the Update page), it does not trigger an XMLRPC Sync for the package configuration. Manually reloading all does work; see attached cron/reload logs.
Files
Marcos Mendoza wrote:
Tested on pfSense 2.6.0 and pfBlockerNG-devel 3.1.0_1
pfBlockerNG-devel option "Enable Sync" with "Sync to host(s) defined below" selected.
Verified by checking secondary settings after each step.
When the cron job runs (either scheduled or from selecting it under the Update page), it does not trigger an XMLRPC Sync for the package configuration. Manually reloading all does work; see attached cron/reload logs.
the same issue exists with pfBlockerNG-devel 3.1.0_2
I can confirm this issue also on a HA pair running 22.01. We have had this issue since switching to pfBlockerNG-devel a few month ago.
We unchecked "keep settings" and removed 3.1.0_1 today on the backup firewall to troubleshoot this and reinstalled 3.1.0_4 but it didn't sync until we did a reload on the primary firewall.
- Assignee set to Viktor Gurov
Viktor Gurov wrote in #note-3:
fix:
https://github.com/pfsense/FreeBSD-ports/pull/1158
I've manually added this fix to a pair of Netgate 7100 running pfSense+ 22.05-RELEASE, and it didn't seem to fix the issue for me; I still had to run a "Reload" task on the primary firewall before the secondary received the updates.
- Has duplicate Bug #13989: XML-RPC Sync not triggered added
Hello Marcos,
sadly this is not the same bug, because for me on pfSense+ 23.01 no update option worked, not even "Reload".
This means for me currently, there is no workaround. In consequence the firewall on the secondary pfSense+ installation does not have the necessary pfBlockerNG tables loaded, meaning the firewall throws errors - continuously. Also the added protection given by these pfBlockernG tables is not present whenever the backup firewall is active, which is a serious problem.
Please look into it again.
Also available in: Atom
PDF