Fresh install pfblockerNG on pfSense 25.11 RC a lot problems

tinfoilmatt

@Antibiotic Not so fresh if you (at least) made ill-advised Unbound configuration changes.

Antibiotic

@tinfoilmatt I think this soft should work at any way. Doesn't matter what we will change in unbound. But anyway this is RC not stable version, time to correct bugs still to go.

tinfoilmatt

@Antibiotic Or it's an issue with your system configuration. I would personally have to troubleshoot your system myself to develop a hunch one way or the other.

Wolf666

@Antibiotic you should enable python module on general settings.

Antibiotic

@Wolf666 The pictures were made in unbound mode not a python mode. That why this is option not ticked. When unbound python mode enabled in pfblockerNG this settings going ON by auto.

Gertjan

@Antibiotic said in Fresh install pfblockerNG on pfSense 25.11 RC a lot problems:

When unbound python mode enabled in pfblockerNG this settings going ON by auto.

I was somewhat surprised to read this, but is is the case.
Settings in a package (pfBlockerng) will modify pfSense 'core' (unbound) settings.

warning: so-sndbuf 4194304 was not granted. Got 57344

I translate :
I want 4 million, only got 50k ..... that's some ressource missing, and you need 80 (!!) times more.
This can't be a simple RAM, you should have enough of it.
Some "buffer size", see pfSense advanced settings ?

tinfoilmatt

@Gertjan said in Fresh install pfblockerNG on pfSense 25.11 RC a lot problems:

see pfSense advanced settings

Services / DNS Resolver / Advanced Settings / Advanced Resolver Options / Message Cache Size

Gertjan

@tinfoilmatt

This :

is some internal unbound cache.

The errors, imho, talks about something else.
I have this "kern.ipc.maxsockbuf(bsd) value" set to :

a bit more as 4 million ^^
Under System > Advanced >System Tunables

Btw : I'm just making noise here, as I didn't install the RC yet (as it is less candidate as release to me ^^).

tinfoilmatt

@Gertjan said in Fresh install pfblockerNG on pfSense 25.11 RC a lot problems:

The errors, imho, talks about something else.

The error was generated by PID 55760, user "unbound".

tinfoilmatt

@Gertjan FWIW, the (apparent) default kern.ipc.maxsockbuf is also ~ 4 MB on CE. Presumably OP could've increased this value dramatically—in excess of 10 MB—to match Unbound's configured 'message cache size.' But that's as bad of an idea as arbitrarily increasing the latter in the first place.