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

    DONT NAT on Destination network

    Scheduled Pinned Locked Moved NAT
    5 Posts 3 Posters 529 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.
    • M
      mrjoli021
      last edited by

      I have my firewall behind a router that has a couple of VPN connections to it. From LAN of my firewall I need to connect to these VPN connections. I am looking for a way to NOT NAT when I am going to these networks. I dont see an option on the NAT rules that disables it.
      Where / how can I create a NAT rule that says if destination network is X then dont NAT?

      M johnpozJ 2 Replies Last reply Reply Quote 0
      • M
        mcury Rebel Alliance @mrjoli021
        last edited by mcury

        I would try something like this: (Not sure if this is going to work).

        1 - create an alias with the destination networks that are behind the VPN.
        2 - Go to:
        Firewall / NAT / Outbound
        3 - Click in ADD
        4 - Tick the option 'Do not NAT'
        8e6ce19c-022a-4630-9f1b-c44eb7020c41-image.png
        5 - Fill the remaining options (destination would be the alias created in the 1st step)

        And make sure this NAT is above the NAT used for internet access.

        Edit: You will probably need to create a static route in the router pointing to pfsense as the next hop for the networks that are behind pfsense.

        Edit2: Actually, you don't need a NAT from pfsense to the router at all, you would only need the static routes, and disable the WAN NAT for LAN network.

        dead on arrival, nowhere to be found.

        1 Reply Last reply Reply Quote 0
        • johnpozJ
          johnpoz LAYER 8 Global Moderator @mrjoli021
          last edited by

          huh? What is the transit network between your router and your firewall?

          How would your upstream router know about these downstream networks if you do not nat to your firewall(pfsense) connection to the transit network?

          I assume this is what your doing because you say your natting, and want to turn it off for something specific.

          Could you draw up your network, and what is trying to go to what without natting, etc.

          An intelligent man is sometimes forced to be drunk to spend time with his fools
          If you get confused: Listen to the Music Play
          Please don't Chat/PM me for help, unless mod related
          SG-4860 24.11 | Lab VMs 2.8, 24.11

          1 Reply Last reply Reply Quote 0
          • M
            mrjoli021
            last edited by

            ![my ISP is connected to a router with a /27. I have split this up into two /28. One of these goes to my Firewall. My router has two VPN connections which I will need to migrate eventually to PFSense, but for right now they are anchored at the router. From the router I have private /30 connected to the WAN of the PFSense. All the /28's which are on the firewall are on the DMZ network. My NAT rule currently says that all outbound traffic gets the DMZ address. I am looking for a way to have pfsense NOT NAT any internal networks connected to the router. Right now when I ping anything that is connected to the router's network it shows up as my public IP.
            e55aaba4-2a81-46b1-af64-75a0136adaeb-image.jpeg

            johnpozJ 1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @mrjoli021
              last edited by

              How would 10.41.1.1 ever see your public IP as source? Other than the IP to create the vpn tunnel. Traffic inside the tunnel would look likes its coming from whatever pfsense gets for its tunnel IP after creating the vpn.

              For you to use your downstream network like that - would have to be setup. the network on the other side of the vpn would have to know to route traffic down the tunnel to get to your 10.36.45 network..

              So your natting on pfsense to this 172.21.36.2 address now? If you don't you have the ubnt setup to route this traffic via your transit?

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

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