Confusion with PFblockerNG rules and my own and system rules

[johnpoz]

Rules are evaluated top down, first rule to trigger wins - no other rules are evaluated... So if you have some device on your lan that where dest is in the whitelist, then it use your default routing... That might be your vpn, if you setup your vpn client to pull routes, and your default route is out your vpn... Look at routing table.

But once that rule triggers none of those other rules are even going to be evaluated.

[zenn biji]

@johnpoz Ah i see. what about floating rules?
also, i just want PFblockerNG to create the aliases but leave the firewall rules alone. i believe i can achieve this with alias native but i cant find it anywhere. And, personally, for this specific situation, what do you recommend? should i just make it not create rules on its own? or change how PFblockerNG creates its rules

[johnpoz]

Floating rules are looked at before interface rules.. Are they marked quick - this is gone over in the docs

https://docs.netgate.com/pfsense/en/latest/firewall/firewall-rule-processing-order.html

i just want PFblockerNG to create the aliases but leave the firewall rules alone

Then do that, that is what I do as well.

[zenn biji]

@johnpoz How did you do that? according to google, it should be under GeoIP (for some reason) and its called Alias native. for me, there is nothing there
this is the closest thing i could find.

[johnpoz]

Just don't pick any interfaces to be applied on.

Set your lists to just be native..

[zenn biji]

@johnpoz Thanks. i dont use the GeoIP section (all disabled. i have no servers that i want to expose) i assume its okay to leave it at disabled? and one last thing. lets say i add an IP to one of my blocklists. assuming that the firewall rule for it is in place, it automatically starts to work correct? thanks for your time

[johnpoz]

Validate that your table gets populated, diag tables.. And then put it in a rule.. You would have to clear any existing states that might be open but sure it would start working as soon as the rules are are applied... Taking into account any preexisting states.

[zenn biji]

@johnpoz alright. thanks man. the rules no longer interfere with my own rules.

[zenn biji]

@johnpoz forgive me for bothering you but even after all of those changes, (except the last one) PFblockerNG still changes the firewall rules. example :
Before running PFblockerNG update
after running pfblocker update
as you can see it deleted its own rules and my rules that were based on the default pfblockerng rules.
i just want it to STOP. i dont want it to even look at the rules anymore

[johnpoz]

Showed you how to do that... I have zero pfblocker rules..

[zenn biji]

@lordofpc734 Oh nvm. i just had to rename the rules (changed pfB_ to pfb_) this was in some infoblock in the IPv4 page