pfBlockerNG-devel v3.1.0_19/10

[fireodo]

@bbcan177
Thanks!

On the alerts configuration page is this issue still present:

"Enter 'none' to disable." If in the color field (in GUI) you put "none" it is not getting validated/accepted!

The value is going back to #83791D and disregard the "none" and there is the following error in /var/log/pfblockerng/error.log:

PFB_FILTER - 20 | alerts hex [ 01/19/23 18:18:45 ] Failed validation [ none ]

[BBcan177]

@fireodo said in pfBlockerNG-devel v3.1.0_19/10:

PFB_FILTER - 20 | alerts hex [ 01/19/23 18:18:45 ] Failed validation [ none ]

Edit: /usr/local/pkg/pfblockerng/pfblockerng.inc
Line: 612
Reference:
https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L612

From:

if (preg_match("/^#([a-fA-F0-9]{6}|[a-fA-F0-9]{3})$/", $input)) {

To:

if ($input == 'none' || preg_match("/^#([a-fA-F0-9]{6}|[a-fA-F0-9]{3})$/", $input)) {

[fireodo]

@bbcan177 said in pfBlockerNG-devel v3.1.0_19/10:

@fireodo said in pfBlockerNG-devel v3.1.0_19/10:

PFB_FILTER - 20 | alerts hex [ 01/19/23 18:18:45 ] Failed validation [ none ]

Edit: /usr/local/pkg/pfblockerng/pfblockerng.inc
Line: 612
Reference:
https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L612

From:

if (preg_match("/^#([a-fA-F0-9]{6}|[a-fA-F0-9]{3})$/", $input)) {

To:

if ($input == 'none' || preg_match("/^#([a-fA-F0-9]{6}|[a-fA-F0-9]{3})$/", $input)) {

Thank you - now it works as expected!
That was super fast!

[jdeloach]

@bbcan177
Just updated to latest version v3.1.0_10 on pfSense 2.6.0 with no issues. I am now evaluating things. So far I have not seen any issues with what I use.

Thanks for hard work you put into maintaining/supporting this great package.

[fireodo]

@bbcan177
Hi again,

( @BBcan177 - please dont shoot )

when I set in the Dashboard Widget pfblocker to reset the IP&DNSBL Counter weekly I get this entry in cron:

after this cronjob is executed:

the DNSBL/IP-Counter Reset is again at Daily:

[motivio]

@fireodo I‘ve seen this too. I was wondering what is causing it.

[fireodo]

@motivio said in pfBlockerNG-devel v3.1.0_19/10:

I‘ve seen this too. I was wondering what is causing it.

I think (guess) there are 2 different places where the cron entrys are generated and those 2 places dont talk to each other ... simply said ...

[pfT]

BBcan177,

At last a chance to thank you for all your work.

Not sure if this is a regression in the latest release or not, since I usually set my ASN aliases to hold.

I noticed that on update of any ASN aliases I am getting the error:

[ AS13076_v4 ]			 Downloading update .
 Failed
 Invalid URL. Terminating Download! [ AS13076 ]

The error log shows basically the same thing:

[PFB_FILTER - 2] Invalid URL (not allowed2) [ AS13076 ] [ 01/19/23 16:31:01 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ AS13076 ] [ 01/19/23 16:34:07 ]
 Failed [ 01/19/23 16:34:07 ]
[PFB_FILTER - 2] Invalid URL (not allowed2) [ AS13076 ] [ 01/19/23 16:34:07 ]

I tried several different ASN, so not a specific problem with the example given.

I don't know the format of the URL created so I couldn't test it separately in the browser.

Not a big issue for the current ASN aliases I am using (since they are on HOLD), but does stop me creating new ones and may be more of a problem for others if they need to use them.

Otherwise everything appears to be working well - unbound even started after the update!

Thanks.

[fireodo]

@pft

Here too. Error thrown is:

[PFB_FILTER - 2] Invalid URL (not allowed2) [ AS47890 ] [ 01/20/23 00:09:28 ]
 Failed [ 01/20/23 00:09:28 ]

[emikaadeo]

v3.1.0_10 still not available for pfSense+ 22.05 (amd64) ?

[manilx]

@emikaadeo Wondering about the same.....

[fireodo]

@manilx said in pfBlockerNG-devel v3.1.0_19/10:

Wondering about the same.....

<guess> Set on hold because of some issues? </guess>

[cmcdonald]

@fireodo

Try again. Another package was failing and thus blocking the build job for 22.05 packages.

[fireodo]

@cmcdonald said in pfBlockerNG-devel v3.1.0_19/10:

@fireodo

Try again. Another package was failing and thus blocking the build job for 22.05 packages.

Its available now!

[manilx]

@cmcdonald Installed!

[BBcan177]

I have pushed another version to fix a couple of issues. So expect to see _20 or _11 depending on what pfSense version you use. Thanks.

[manilx]

@bbcan177 Just updated to _11.
All OK.

[fireodo]

@bbcan177
Updated to 3.1.0_11 - all good! Thanks

[jdeloach]

@bbcan177
Updated from v3.1.0_10 to v3.1.0.11 with no issues.

Thanks for the quick update.

[pfT]

@bbcan177

I've also updated and can confirm this fixed the error I was seeing with ASN.

I'm now getting:

[ Virgin_Media_UK_AS13076_v4 ]	 Downloading update .
  Downloading ASN: 13076... completed
. completed ..
  Empty file, Adding '127.1.7.7' to avoid download failure.

but I've seen that occasionally before (and why I originally set my other ASN aliases to HOLD when i suddenly found I couldn't connect from my phone externally via Wireguard or OpenVPN).

I suspect this probably just indicates a problem with the download site, rather than any underlying problem within pfBlockerNG-devel v3.1.0_11 on pfSense 2.6.0.

I've leave my test entry in there and see if it properly updates in a few days.

Thanks for such a swift update and resolution.