NAT / PAT issues. Please Help

RGuita

Hi all,

My infraestructure:

pfSense Interfaces: LAN -> IP: 10.10.10.99
LAN2-> IP: 192.168.10.254
WAN -> Disabled

Goal: create a NAT/PAT for traffic comming from LAN to 53.53.53.53 on port:443 should be redirected to 192.168.10.100 on port 443

Somehow it doesn't seem to work, what is wrong with the settings.

Some help would be appreciated.

Thanks & regards,

RGUITA

NAT.JPG_thumb

doktornotor

What's that 53.53.53.53? Did you create some virtual IP somewhere or what?

RGuita

What's that 53.53.53.53? Did you create some virtual IP somewhere or what?

Hi,

No, I didn't create any virtual IP, I just want to forward all traffic to a specific IP (which doesn't really exists on my network) to a different machine. Thats wy I thought to use NAT/PAT.

Do you know if there's a way????

Regards,

RGuita

Derelict

Create a VIP on LAN for 53.53.53.53.

https://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses

Not quite sure how any other hosts on your network will know to send traffic for 53.53.53.53 to pfSense but I guess that's your problem.

(Hint: You're doing it wrong.)

RGuita

Hi,

If I'm doing it wrong, what would be the best/right way????

Regards,

RGuita

Derelict

https://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense

cmb

@Derelict:

Create a VIP on LAN for 53.53.53.53.

https://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses

Not quite sure how any other hosts on your network will know to send traffic for 53.53.53.53 to pfSense but I guess that's your problem.

Assuming that's their default gateway, they'll send all off-subnet traffic there. If it's not their default gateway, adding a VIP won't help since the LAN hosts won't ever ARP that IP. Don't add a VIP. The rule as specified will work, with one caveat - source NAT on LAN is required if the source of the traffic is also on LAN2, as the target server will reply directly back to the source client with the wrong source IP, breaking the TCP connection. The source NAT ensures the reply goes back through the firewall, where it's translated back to the 53.53.53.53 IP so the connection isn't broken.