Project

General

Profile

Actions
Copy link

Bug #15346

closed

Cannot add Port Forward with an unassociated filter rule

Added by Timo M over 2 years ago. Updated 10 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Marcos M
Category:
Rules / NAT
Target version:
2.9.0
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
26.07
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

Related issues

Has duplicate Bug #16871: PHP Fatal error: add_filter_rules() — Argument #2 ($index) must be of type int, null given — when saving NAT Port Forward with filter rule association EnvironmentDuplicate

Actions
Actions
Copy link
 #1

Updated by Christopher Cope over 2 years 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 2 years 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 2 years 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 over 1 year ago

Tested on 24.11
The issue still persists.

Actions
Copy link
 #5

Updated by Marcos M 15 days ago

  • Has duplicate Bug #16871: PHP Fatal error: add_filter_rules() — Argument #2 ($index) must be of type int, null given — when saving NAT Port Forward with filter rule association Environment added
Actions
Copy link
 #6

Updated by Marcos M 15 days ago

  • Subject changed from Port Forward Add Unassociated Filter Rule Not Working to Cannot add Port Forward with an unassociated filter rule
  • Assignee set to Marcos M
  • Target version set to 2.9.0
  • Plus Target Version set to 26.07
Actions
Copy link
 #7

Updated by Marcos M 15 days ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100

Applied with f8b607d6966e45fec1d654a1708af12fdbb4cae7.

Actions
Copy link
 #8

Updated by Christopher Cope 10 days ago

  • Status changed from Feedback to Resolved

Tested on

26.11-DEVELOPMENT (amd64)
built on Sat Jun 13 6:00:00 UTC 2026
FreeBSD 16.0-CURRENT

It's working as expected now.

Actions
Copy link

Also available in: Atom PDF