pfBlockerNG-devel v3.1.0_7 / v3.1.0_14

jdeloach

@bbcan177
I updated pfBlockerNG_devel v3.1.0_6 to v3.1.0_7 with no issues. Everything appears to be working okay.

Thanks for all the hard work you put into maintaining/upgrading this Great package.

fireodo

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

So, please, don't let us wait : what is this line 15 ?

its a local file:
/root/database/ioam.txt

fireodo

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

Language issue

No, in 3.1.0_6 there was no issue!
(I do not use anywhere on pfsense special characters/Umlaut)

Gertjan

@fireodo said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

its a local file:
/root/database/ioam.txt

Yeah, I know.
It's a file.
A files has lines.
Line 15 of that file has an issue.

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

So, please, don't let us wait : what is this line 15 ?

edit :
I'm using

for several weeks now.
pfSense 22.05.

fireodo

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

Line 15 of that file has an issue.

Not the line 15 in the file (btw. its a domain name) - the error refers to the feed position in the group!

Line 15 is the position in the group of the feed that points to the local file! (Changing the feed position in the group results in change of the line number in the error)

Gertjan

@fireodo

Ah, ok.

Then what is different ?
Can you create a file called /root/test.xt - as I showed above ?
Can you place the content, as I showed above (7 lines or so) ?
Add the file as a "DNSBL Groups" entry" as I've showed above ?

We both use the same pfBlocker-ng version.

fireodo

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

Then what is different ?

I guess the way the script validates the feed url.

Can you create a file called /root/test.xt - as I showed above ?

I did.

Can you place the content, as I showed above (7 lines or so) ?

Yes

Add the file as a "DNSBL Groups" entry" as I've showed above ?

Yes - same error (the content of the file doesnt matter at this point)

We both use the same pfBlocker-ng version.

You under 22.05 and me under 2.6.0 ...

Gertjan

Remember :

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

Here a trick : go here : /var/db/pfblockerng/dnsblorig and delete your-file.orig - and reload pfblockerng

Because (I think) : pfblockerng doesn't reload the file, whatever you change in the settings.
It will reload a file or URL after one hours, two hours or whatever you've set.
To really for it : delete the 'orig' files or even all of them : they will get reloaded. As this worked for me.

fireodo

@gertjan said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

As this worked for me.

Because (i guess) your v3.1.0_7 on 22.05 is more like v3.1.0_6 was on 2.6.0 ...

BBcan177

@fireodo said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

[PFB_FILTER - 2] Invalid URL (not allowed2) [ /root/database/youtubeads.txt ] [ 12/9/22 08:56:50 ]

You need to move these files to the "/usr/local/www" or "/var/db/pfblockerng/" folder, if you intend to keep hosting these files on pfSense. Click on the Blue infoblock icon for the Source Definitions for more details.

Running Cron Update I get this error on this list:

[ EasyList ] Downloading update .. 200 OK
[PFB_FILTER - 17] Failed or invalid Mime Type: [text/x-asm|0]

The new code now checks the file magic to determine to the file mime-type.

There is an issue in decoding the magic for some Easylist feeds. I suggest you use the Easylist Feeds that are in the Feeds tab as I have allowed some exceptions until the magic database is updated.

I worked with the Dev to address this issue here:
https://github.com/file/file/commit/31ee773f9cb78ff584872456ea1f139081a01761

Just need for that to be updated into FreeBSD and then into pfSense.

fireodo

@bbcan177 said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

@fireodo said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

[PFB_FILTER - 2] Invalid URL (not allowed2) [ /root/database/youtubeads.txt ] [ 12/9/22 08:56:50 ]

You need to move these files to the "/usr/local/www" or "/var/db/pfblockerng/" folder, if you intend to keep hosting these files on pfSense. Click on the Blue infoblock icon for the Source Definitions for more details.

Ah - i thought that it was just a example in the infoblock - I moved now the files in /var/db/pfblockerng and could save the settings - and works.

Running Cron Update I get this error on this list:

[ EasyList ] Downloading update .. 200 OK
[PFB_FILTER - 17] Failed or invalid Mime Type: [text/x-asm|0]

The new code now checks the file magic to determine to the file mime-type.

There is an issue in decoding the magic for some Easylist feeds. I suggest you use the Easylist Feeds that are in the Feeds tab as I have allowed some exceptions until the magic database is updated.

OK understood - I'll do so!

I worked with the Dev to address this issue here:
https://github.com/file/file/commit/31ee773f9cb78ff584872456ea1f139081a01761

Just need for that to be updated into FreeBSD and then into pfSense.

Thanks a lot and regards,
fireodo

provels

It seems I've had v3.1.0_7 on 22.05 for some time. Not sure how that happened. I probably got a txt saying there was an update available a while back and installed it from the shell. Is this a re-release that needs to be reinstalled? No biggie, everything works, though I did need to start unbound after.

emikaadeo

@provels said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

It seems I've had v3.1.0_7 on 22.05 for some time.

Same here but the packages are definitely not the same.
Comparing file /usr/local/pkg/pfblockerng/pfb_dnsbl.doh.conf on my pfSense+ 22.05 and the one from github commit are different.

EDIT: I think we should wait https://www.reddit.com/r/pfBlockerNG/comments/zg9ipo/comment/izjaun5

BBcan177

@emikaadeo
What hardware?
amd64, arm64, or armv7

emikaadeo

@bbcan177
amd64

SteveITS

@provels 3.1.0_7 came out in late October or thereabouts, to fix the CPU usage/logging bug.
https://redmine.pfsense.org/issues/13154#note-17

jdeloach

This post is deleted!

emikaadeo

@jdeloach said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

@steveits
@provels
It came out for 22.x but not for CE 2.6.x. I think that is what is confusing everyone. including @BBcan177.

3.1.0_7 "from Netgate" and 3.1.0_7 from @BBcan177 are not the same packages.
Code is different.

jdeloach

@emikaadeo said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

@jdeloach said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

@steveits
@provels
It came out for 22.x but not for CE 2.6.x. I think that is what is confusing everyone. including @BBcan177.

3.1.0_7 "from Netgate" and 3.1.0_7 from @BBcan177 are not the same packages.
Code is different.

This is not the only package that has differences between the maintainers and Netgate versions.

Snort and Suricata both suffer the same issues, @bmeeks.

Edit: Long term, it is one hell of mess that's going to be hard to fix.

emikaadeo

@jdeloach said in pfBlockerNG-devel v3.1.0_7 / v3.1.0_14:

Edit: Long term, it is one hell of mess that's going to be hard to fix.

Exactly ;)