Project

General

Profile

Actions
Copy link

Bug #14537

closed

Nat Reflection changed behavior on pfsense 2.7

Added by Michele Zamboni 11 months ago. Updated 4 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

Also available in: Atom PDF