Project

General

Profile

Actions
Copy link

Feature #4259

closed

Port forward NAT rules with "any" protocol

Added by Anonymous almost 10 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jim Pingle
Category:
Rules / NAT
Target version:
2.7.0
Start date:
01/21/2015
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:

Description

Hello,
i'm starting to use pfsense inside my company network but i see that pfsense is missing a NAT ability compared to other product used on our production environment.
It would be nice to be able to create NAT rules with "any" as ip protocol. I don't mean bi-nat rules but simple destination or source nat rules without specify the ip protocol to use.
For example we should need to create destination nat rules dst_IP -> dst_IP for all ip protocols.
I checked on pf manual and i see that the protocol is optional. Is it correct?
Thank you

Related issues

Related to Regression #13203: Floating rules without an interface are not loadedResolvedMarcos M

Actions
Actions
Copy link
 #1

Updated by Chris Buechler almost 10 years ago

  • Subject changed from NAT rules without ip protocol to Port forward NAT rules with "any" protocol
Actions
Copy link
 #2

Updated by Ermal Luçi over 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #3

Updated by Ermal Luçi over 9 years ago

Actions
Copy link
 #4

Updated by Phillip Davis over 9 years ago

The fix "Use proper variable to do calculations" is actually the fix for #4529 - bit confusing there with the numbers just switched around.

Actions
Copy link
 #5

Updated by Chris Buechler over 9 years ago

  • Status changed from Feedback to New
  • % Done changed from 100 to 0
Actions
Copy link
 #6

Updated by Giuanin Piemunteis about 8 years ago

Could be it implemented with the new 2.4 release ?

Actions
Copy link
 #7

Updated by Viktor Gurov over 2 years ago

  • Assignee set to Viktor Gurov
  • Target version changed from Future to 2.7.0
  • Plus Target Version set to 22.05
Actions
Copy link
 #8

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Pull Request Review
Actions
Copy link
 #9

Updated by Viktor Gurov over 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #10

Updated by Alhusein Zawi over 2 years ago

  • Status changed from Feedback to Resolved

added

rdr on em0 inet from any to 10.100.100.127 -> 10.10.10.30

2.7.0.a.20220422.0600

Actions
Copy link
 #11

Updated by Jim Pingle over 2 years ago

  • Status changed from Resolved to New

This is causing a PHP error:

strstr() expects at least 2 parameters, 1 given in /usr/local/pfSense/include/www/firewall_nat.inc on line 520
strstr() expects at least 2 parameters, 1 given in /usr/local/pfSense/include/www/firewall_nat.inc on line 521
Actions
Copy link
 #12

Updated by Viktor Gurov over 2 years ago

Jim Pingle wrote in #note-11:

This is causing a PHP error:

[...]

fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/752

Actions
Copy link
 #13

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Pull Request Review
Actions
Copy link
 #14

Updated by Viktor Gurov over 2 years ago

  • Status changed from Pull Request Review to Feedback
Actions
Copy link
 #15

Updated by Alhusein Zawi over 2 years ago

Error:

There were error(s) loading the rules: /tmp/rules.debug:166: syntax error - The line in question reads [166]: pass in quick on $WAN reply-to ( em0 10.100.100.1 ) inet proto any from any to 10.10.10.30 ridentifier 1651948803 keep state label "id:1651948803" label "USER_RULE: NAT test_any_rule"

2.7.0.a.20220426.0600

Actions
Copy link
 #16

Updated by Viktor Gurov over 2 years ago

Alhusein Zawi wrote in #note-15:

Error:

There were error(s) loading the rules: /tmp/rules.debug:166: syntax error - The line in question reads [166]: pass in quick on $WAN reply-to ( em0 10.100.100.1 ) inet proto any from any to 10.10.10.30 ridentifier 1651948803 keep state label "id:1651948803" label "USER_RULE: NAT test_any_rule"

2.7.0.a.20220426.0600

You should test it on the latest snapshot (>20220428).

Actions
Copy link
 #17

Updated by Alhusein Zawi over 2 years ago

I am still seeing the same error
2.7.0.a.20220513.0600

There were error(s) loading the rules: /tmp/rules.debug:167: syntax error - The line in question reads [167]: pass in quick on $WAN reply-to ( em0 10.100.100.1 ) inet proto any from any to 10.10.10.30 ridentifier 1652551188 keep state label "id:1652551188" label "USER_RULE: NAT "
@ 2022-05-14 11:00:15

Actions
Copy link
 #18

Updated by Jim Pingle over 2 years ago

  • Status changed from Feedback to New
Actions
Copy link
 #19

Updated by Jim Pingle over 2 years ago

  • Status changed from New to In Progress
  • Assignee changed from Viktor Gurov to Jim Pingle

I can replicate the error here as well. It's failing to load the firewall rule because it has "proto any" where it should be omitted in that case. I found the test where it's falling through to that.

Actions
Copy link
 #20

Updated by Jim Pingle over 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #21

Updated by Viktor Gurov over 2 years ago

  • Related to Regression #13203: Floating rules without an interface are not loaded added
Actions
Copy link
 #22

Updated by Danilo Zrenjanin over 2 years ago

Tested:

2.7.0-DEVELOPMENT (amd64)
built on Fri May 27 06:19:08 UTC 2022
FreeBSD 12.3-STABLE

No errors and the rdr rule works as expected. I am marking this ticket as resolved.

Actions
Copy link
 #23

Updated by Danilo Zrenjanin over 2 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom PDF