possible problem or misconfiguration
-
If you mouse-over that it shows you the linked firewall rules created by that port forward.
The two lower rules don't have that because you selected not to create a linked firewall rule when you created them.
See:
Filter Rule Association
here: https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html -
@stephenw10 beat me to it ;)
-
How come I chose not to create an associated firewall rule?
As I only created one rule and duplicated it several times then corrected it?
Is there anything that can be pressed to connect and if so where is it located?Also does it matter if they are related or not? Are there any advantages when they are connected or is it just a guideline?
Sorry for the dumb questions just trying to understand exactly how it works and thank you for your time.
-
@markdudov said in possible problem or misconfiguration:
and duplicated it several times then corrected it?
And there is your answer.. I don't even think it lets you copy a nat rule.. Maybe on the new 24.03? But to create linked rule, the nat rule would have to be created.
It lets you create a new one based on an old one.. That would should create the new association, if you left that selected.. And changed the interface to wan 2.
does here via test just did
-
Hmm, I would expect that to work.
However it's easy to fix. Edit the port forward and set the 'Filter Rule Association' to 'Create associated firewall rule' and resave.
-
Mmm, there's a bug here. Shows something odd.
-
that's it
-
And what is the meaning of Filter rule association? What actually happens when a new Filter rule association is created?
-
It adds a rule to pass traffic to the forward. It's explained in the doc I linked above.
-
Opened bug report: https://redmine.pfsense.org/issues/15547
Appears to be mostly cosmetic though.