Project

General

Profile

Actions
Copy link

Bug #14537

closed

Nat Reflection changed behavior on pfsense 2.7

Added by Michele Zamboni 10 months ago. Updated 3 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
NAT Reflection
Target version:
-
Start date:
Due date:
% Done:

0%

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

Description

Hello,

we are having problems with NAT Reflection after updating to pfsense 2.7 from 2.6
It seems that now NAT reflection works only on the CARP master firewall.

In our dns we setup entries like this (we have a high availability firewall cluster with 2 nodes master/slave):

firewall1.example.com -> WAN public ip 1
firewall2.example.com -> WAN public ip 2

firewall1.intra.example.com -> LAN private ip 1
firewall2.intra.example.com -> LAN private ip 2

If we try to connect to https://firewall1.example.com from lan when firewall1 is carp master, it allows us to reach the gui
If we try to connect to https://firewall2.example.com from lan when firewall1 is carp master, the connection times out.

If we move the carp master from firewall1 to firewall2 the behavior is swapped: we can connect on the gui of firewall2 but not firewall1.

The behavior is the same whether we use "nat+proxy" or "pure nat" settings in System>Advanced>Firewall & NAT
With pfsense 2.6 we can reach both WAN ip addresses regardless where the carp master ip is.

The connection to firewall1.intra.example.com and firewall2.intra.example.com is obviously not affected.

Is it an expected behaviour for 2.7?

Thanks,
Michele

Files

Screenshot 2023-07-03 at 18-29-01 metatron.comedia.it - System Advanced Firewall & NAT.png (329 KB) Screenshot 2023-07-03 at 18-29-01 metatron.comedia.it - System Advanced Firewall & NAT.png System>Advanced>Firewall & NAT>Network Address Translation Michele Zamboni, 07/03/2023 04:30 PM
Actions
Copy link
 #2

Updated by Jim Pingle 10 months ago

  • Status changed from New to Rejected

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum .

See Reporting Issues with pfSense Software for more information.

Actions
Copy link
 #3

Updated by Michele Zamboni 10 months ago

Hello Jim,
thanks for your reply. It was not a request for support.
I just notified a changed behavior between pfsense 2.6 and 2.7 with the same configuration.

Thanks,
Michele

Actions
Copy link
 #4

Updated by Tobias D. 5 months ago

I have the same problem since I upgraded to 2.7.0 (also upgraded to 2.7.1 now, but the behavior is still the same).
I have a cluster with two firewalls in active/passive.
I upgraded the passive node from 2.5.2 to 2.6.0 and everything worked fine. I was able to access the passive node from an internal system via the external address.
After upgrading to 2.7.0, the same access no longer works. The same behavior on 2.7.1.
When switching the passive node to the active node, it works, but then the same applies to the former active node. No access from an internal system via the public IP.
The public IP is not a CARP address, but is configured directly on the WAN interface.
Switching global nat reflection to nat+proxy or pure nat does not help.

This happens for both https and ssh access.

I can see my request in the state table but it instantly goes to syn_sent:closed state on the passive node.

all tcp 192.168.42.43:46820 -> xxx.xxx.xxx.xxx:22 CLOSED:SYN_SENT 0 / 0 0 B / 0 B
all tcp xxx.xxx.xxx.xxx:14583 (192.168.42.43:46820) -> xxx.xxx.xxx.xxx:22 SYN_SENT:CLOSED 0 / 0 0 B / 0 B

Actions
Copy link
 #5

Updated by Marcos M 3 months ago

FWIW I've tested this setup in 24.03 and it works fine there.

Actions
Copy link

Also available in: Atom PDF