pfBlockerNG-devel spamming php error keep current gateway
-
pfSense 2.4.4 stable,
pfBlockerNG-devel 2.2.5_19.
pfBlockerNG launched via cron job, do it work, after this ~one minute in multi WAN environment I see many same errors (40 per one second) in general log:
/usr/local/www/pfblockerng/pfblockerng.php: Keep current gateway, its already part of the group members.
It is ok? Thanks in advance.Latest stable pfSense on 2x XG-7100 and 1x Intel Xeon Server, running mutiWAN, he.net IPv6, pfBlockerNG-devel, HAProxy-devel, Syslog-ng, Zabbix-agent, OpenVPN, IPsec site-to-site, DNS-over-TLS...
Unifi AP-AC-LR with EAP RADIUS, US-24 -
@dragoangel said in pfBlockerNG-devel spamming php error keep current gateway:
Keep current gateway, its already part of the group members
Maybe related to this Redmine issue?
https://redmine.pfsense.org/issues/8914 -
yes, seems like this but* it only appears on cronjob after [pfBlockerNG] Starting cron process., not on GW up/down.
Latest stable pfSense on 2x XG-7100 and 1x Intel Xeon Server, running mutiWAN, he.net IPv6, pfBlockerNG-devel, HAProxy-devel, Syslog-ng, Zabbix-agent, OpenVPN, IPsec site-to-site, DNS-over-TLS...
Unifi AP-AC-LR with EAP RADIUS, US-24 -
I still don't see this related to the package. It sounds like something is incorrectly configured for the gateways... Check the pfblockerng.log, resolver.log, system.log for more clues to see if you can narrow it down. Best to post this question to the applicable Forum for more traction.
