NAT hairpin not working
-
I am having some issues with NAT hairpin not working.
Up to about 2 months ago, everything was working. After a reboot of my appliance, NAT hairpin does not work.
All other NAT rules from the outside world are functioning, but I cannot get my FQDN to work from the LAN.
Does anyone have any suggestions?
I am currently running pfSense 2.81
-
Let's see the NAT rule (at least).
-
@tinfoilmatt the rule in particular with the issue are rustdesk
-
Is interface "
BELLFIBE" a WAN interface?What interface is attached to the subnet the RustDesk server is connected to (i.e.,
172.16.0.2[/24?]), is it "LAN"? -
@tinfoilmatt My pfsense WAN interface the physical connection. The BELLFIBE is an authenticated PPPoE vlan connection on the physical pfSense interface which is then the WAN interface.
My LAN is on 172.16.0.1
-
Not entirely sure if relevant at all but, seeing that you have a linked firewall rule and reading through the documentation on the "Filter Rule Association" option, I found the following note in the documentation:
Rules using Pass can only work on the interface containing the default gateway for the firewall, they do not work with Multi-WAN.
Network Address Resolution / Port Forwarding Risks
Would be helpful to see the NAT rule's actual configuration.
-
@tinfoilmatt I don't have a mutil WAN.
-
My ISP does not support bridging their modem to my pfSense
-
Searching the internet about 5 years ago I found this setup on how to bypass their modem https://prnt.sc/vwcy02
-
This works and so has the NAT hainpin until about 2 months ago
-
This is the NAT rule's configuration
-
The BELLFIBE interface is my default gateway
-
