Project

General

Profile

Actions
Copy link

Bug #15346

open

Port Forward Add Unassociated Filter Rule Not Working

Added by Timo M over 1 year ago. Updated 10 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

Upon creating a port forward entry on pfSense Plus 23.09.1 and choosing the "Add unassociated filter rule" option under Filter Rule Association, no firewall rule was actually created. Next time I checked the port forward Filter Rule Association setting on the rule that was created, it had been automatically set to "None". The documentation seems to indicate that a rule should still be created even when the unassociated option is chosen.

https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html#port-forward-settings

Actions
Copy link
 #1

Updated by Christopher Cope over 1 year ago

  • Category changed from Unknown to Rules / NAT
  • Status changed from New to Confirmed

I'm able to confirm this behavior on

23.09.1-RELEASE (amd64)
built on Wed Dec 20 13:27:00 EST 2023
FreeBSD 14.0-CURRENT
Actions
Copy link
 #2

Updated by Lev Prokofev over 1 year ago

Can confirm this behavior on 24.03 BETA

24.03-BETA (amd64)
built on Fri Mar 22 9:00:00 MSK 2024
FreeBSD 15.0-CURRENT
Actions
Copy link
 #3

Updated by Kris Phillips over 1 year ago

I can also confirm this behavior on the March 22nd builds of 24.03. Associated and None work fine.

Actions
Copy link
 #4

Updated by aleksei prokofiev 10 months ago

Tested on 24.11
The issue still persists.

Actions
Copy link

Also available in: Atom PDF