Error adding source to ipv4 rule in "Advanced Outbound Firewall Rule Settings"

[jnuser]

I have the following error, I need to add a source to my blocking rule made in IP > IPV4, when I go to Error adding source to ipv4 rule in "Advanced Outbound Firewall Rule Settings" I enable the source option, add both alias and ip, it gives the same fatal error in php.

"Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /usr/local/www/pfblockerng/pfblockerng_category_edit.php:447 Stack trace: #0 {main} thrown in /usr/local/www/pfblockerng/pfblockerng_category_edit.php on line 447 PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_category_edit.php, Line: 447, Message: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, null given in /usr/local/www/pfblockerng/pfblockerng_category_edit.php:447 Stack trace: #0 {main} thrown"

[jnuser]

I did some tests, trying to put other things in place, or changing other settings and the error remains, with no possibility of a solution! I tried to install the two versions that exist and did the tests, the error continues!

Does anyone have any idea what it could be?

[johnpoz]

@jnuser I use pfblocker aliases in my rules.. Did you validate in the diagnostic section, tables that the table is populated correctly?

Not even sure why a pfblocker anything would come up in a firewall rule, are you not using native aliases in your pfblocker for the alias(es) your creating?

[jnuser]

@johnpoz said in Error adding source to ipv4 rule in "Advanced Outbound Firewall Rule Settings":

ivos no seu pfblocker para o(s) alias(s) que você está criando?

So, in this case you are creating your own rules, right?

I was trying to use the rules directly from pfblocker, without notice or create them manually after pointing to the pfblocker alias

[johnpoz]

@jnuser Yeah I don't let pfblocker create rules. I just create the aliases and then use those aliases in my own rules..

Not really of fan of anything creating/editing or moving rules on its own.. While I love pfblocker - I love that it allows you this choice to just create your own aliases to use in your firewall rules.

[jnuser]

@johnpoz

interesting, thank you very much, I'll do it like that then... Another thing, since you're messing with the glanulation patch and word blocking, can we manage it by the rules?

[Bob.Dig]

@jnuser said in Error adding source to ipv4 rule in "Advanced Outbound Firewall Rule Settings":

I have the following error, I need to add a source to my blocking rule made in IP > IPV4, when I go to Error adding source to ipv4 rule in "Advanced Outbound Firewall Rule Settings" I enable the source option, add both alias and ip

What do you mean by that: add both? have you read the warning beneath it? Make a screenshot.

[johnpoz]

@jnuser said in Error adding source to ipv4 rule in "Advanced Outbound Firewall Rule Settings":

"Advanced Outbound Firewall Rule Settings"

Sorry must of read over that - why would you be using pfblocker in outbound nat rules as source???

The only "source" in the outbound nat would be your local IPs.. How why would they be in pfblocker?

[sengork]

I'm facing the same issue when attempting to perform outbound block for a set of ASNs and a custom source. See:

https://redmine.pfsense.org/issues/14523