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

    1:1 Nat only works in one direction

    Scheduled Pinned Locked Moved NAT
    3 Posts 3 Posters 301 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
      milonic
      last edited by

      Hi All,

      I have a very strange issue with a Virtual IP and 1:1 Nat being able to send packets but never a response.

      Basically I have created a virtual "IP Alias" of 10.1.1.1/8 on the LAN interface.

      I then create a 1:1 NAT Mapping for 10.1.1.1 pointing to 10.0.0.4 (web server and other services)

      Everything seems to be OK. 10.0.0.4 receives traffic but doesn't seem to be able to send a reply. It's like it can't send the synack or doesn't get a reply?

      This used to work fine so either something in an update or maybe a config change has broken it. I've spent most of today on this and I'm finally bamboozled and to what the problem is.

      Anybody got any pointers?

      V S 2 Replies Last reply Reply Quote 0
      • V
        viragomann @milonic
        last edited by

        @milonic said in 1:1 Nat only works in one direction:

        Basically I have created a virtual "IP Alias" of 10.1.1.1/8 on the LAN interface.

        I then create a 1:1 NAT Mapping for 10.1.1.1 pointing to 10.0.0.4 (web server and other services)

        Both in the same subnet? How should pfSense route then?

        Basically I think, there cannot be any need for a /8 network at any location.

        1 Reply Last reply Reply Quote 0
        • S
          SteveITS Galactic Empire @milonic
          last edited by

          @milonic Did you mean to use 10.1.1.1/24 for the VIP?

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote 👍 helpful posts!

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