Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Manual Outgoing NAT problem

    Scheduled Pinned Locked Moved NAT
    1 Posts 1 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tata_tulen
      last edited by

      Hi all,

      I've problem with manual outgoing NAT. I've defined two outgoing NAT rules (see attachmed screenshot). We have two pfSense boxes - one for clients VLANs with manual outgoing NAT (let's say "PF1") and the second for servers VLANs with 1:1 NAT rules (let's say "PF2").

      When I try to connect to the service (e.g. website) published on "PF2" using 1:1 NAT via "PF1" (as internal client), it doesn't work and in packet cature on PF2 I can see the internal IP (from PF1 internal subnet) as Source:

      
      13:02:35.420557 IP 192.168.3.160.49870 > 93.99.xx.xx.80: tcp 0
      13:02:36.022538 IP 192.168.3.160.49872 > 93.99.xx.xx.80: tcp 0
      
      

      However, any other outgoing communication seem to be ok - e.g. on http://www.ripe.net I can see correct external IP that match the corresponding  outgoing NAT rule…

      I really have no idea where to start debugging this issue...
      outbound_nat.png
      outbound_nat.png_thumb

      -tt-

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.