OPNsense Forum

English Forums => General Discussion => Topic started by: assasen11 on March 27, 2019, 05:23:27 PM

Title: NAT issues
Post by: assasen11 on March 27, 2019, 05:23:27 PM
I am losing my mind over an issue that I have no idea why it is happening. I am creating accurate NAT rules and the ports are just not opening at all. Am I missing something? I saw a post not too long ago related to outbound routes but I did not entirely understand what it was suggesting I needed to fix or change. I am running the newest version of Opnsense. Does anyone know how to fix this?

-Thanks ahead of time
Title: Re: NAT issues
Post by: bartjsmit on March 27, 2019, 05:45:44 PM
A NAT rule is not enough to allow the traffic. It only rewrites the address field of the packets.

Ensure you have a corresponding firewall rule on the WAN interface with the internal host as the destination.

Bart...
Title: Re: NAT issues
Post by: assasen11 on March 27, 2019, 06:49:50 PM
Quote from: bartjsmit on March 27, 2019, 05:45:44 PM
A NAT rule is not enough to allow the traffic. It only rewrites the address field of the packets.

Ensure you have a corresponding firewall rule on the WAN interface with the internal host as the destination.

Bart...

I have been auto generating the rules. I went ahead and checked to confirm there was a corresponding rule for the WAN interface to allow the traffic.
Title: Re: NAT issues
Post by: walkerx on March 28, 2019, 10:38:48 AM
what are you wanting through the firewall for nat rules?

Title: Re: NAT issues
Post by: assasen11 on March 28, 2019, 08:12:22 PM
At this moment I am trying to do a straight port 443 pass through directly to a host. So if traffic hits the specific static WAN address then it forwards port 443 to the LAN host.
Title: Re: NAT issues
Post by: bartjsmit on March 28, 2019, 09:12:47 PM
Did you put in a 1:1 NAT for it? These settings work for me:

Interface: WAN
Type: BINAT
External Network: <static WAN IP>
Source: Single Host or Network, <internal IP>/32
Destination: any

Allow 443 TCP to the internal IP in the WAN firewall rules

Bart...