Navigation

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

    Yet Another Outbound " NAT " Newbie Topic... I thank you!

    NAT
    2
    2
    71
    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.
    • F
      fgs last edited by

      Thanks for reading this. Much appreciated.

      I've got a number of virtual IPs configured under my "WAN" public IP address / interface. All goes well with traffic coming in to my servers assigned with "LAN" IP addresses. The classic problem is, all traffic returning from the servers under "LAN" go out with the same unified "WAN" IP address. That's the default outbound "NAT" behavior.

      From what I read on the documentation, I favor a "hybrid" type of outbound "NAT" configuration. However, this PFSENSE is now live and I wouldn't mess around too much. If you could just leave a bit of your own experience to solve such issue, that is, for every server under "LAN", traffic must leave from the same public "IP alias" it came in, I'll be truly grateful.

      Could you provide me with some sample steps? Thank you!

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @fgs last edited by

        @fgs said in Yet Another Outbound " NAT " Newbie Topic... I thank you!:

        The classic problem is, all traffic returning from the servers under "LAN" go out with the same unified "WAN" IP address. That's the default outbound "NAT" behavior.

        No, that only applies to outbound traffic initiated by your local devices.
        Response packets on requests from WAN come back from the IP the requests were sent to if your WAN interface is set up correctly.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post