Project

General

Profile

Correction #9685

Feedback on Firewall — Floating Rules

Added by David Gyimesi 29 days ago. Updated 29 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
08/19/2019
Due date:
% Done:

0%

Estimated time:
Affected Documentation:
pfSense Documentation site (Wiki)

Description

Page: https://docs.netgate.com/pfsense/en/latest/book/firewall/floating-rules.html

Feedback:

Nice page however MATCH rule processing order is not described.

Without Quick checked, the rule will only take effect if no other rules match the traffic.

This implies that without QUICK flag a rule is evaulated after Floating, Interface group, Interface rules, basically at the end of the whole ruleset.
1. Floating rules (Quick)
2. Interface group rules
3. Interface rules
4. Floating rules (NON Quick)

It is clear so far however

Match rules do not work with Quick enabled.

Which means a MATCH rule is never quick, and according the statement above says "Without Quick checked, the rule will only take effect if no other rules match the traffic", therefore processed at the end of the whole ruleset.
I don't think this is the reality otherwise there would be cases when MATCH rule would never be evaluated. Could you please explain in the document the processing order of a (non quick) MATCH rule?
Thank you!

History

#1 Updated by David Gyimesi 29 days ago

I have to correct myself.
Processing order remains the same regardless Quick or non Quick
1. Floating rules (Quick + NON Quick)
2. Interface group rules
3. Interface rules

But quick reverses the behavior of “first match wins” to be “last match wins”.
Therefore I can simplify my request:
Could you please describe in the book if “last match wins” is Applicable OR Not Applicable to MATCH rules (which are not quick)?
Thank you!

#2 Updated by David Gyimesi 29 days ago

To furhter simlpify (and if my understaning is correct) can be said that: MATCH rule applies immediately, it doesn't stop the rule processing, therefore the evaluation continues till the end of the ruleset.

Also available in: Atom PDF