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

    Default NAT rules clarification.

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 1.1k 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.
    • K
      kathampy
      last edited by

      Why does 127.0.0.0/8 to WAN use the outbound port range 1024:65535 when LAN to WAN does not?

      Why is a NAT rule for 127.0.0.0/8 even required? Won't the OS automatically use the WAN interface for all outbound traffic originating from itself?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        @KurianOfBorg:

        Why does 127.0.0.0/8 to WAN use the outbound port range 1024:65535 when LAN to WAN does not?

        IIRC that is the default for others it's just explicitly stated in the 127.0.0.1 rule.

        @KurianOfBorg:

        Why is a NAT rule for 127.0.0.0/8 even required? Won't the OS automatically use the WAN interface for all outbound traffic originating from itself?

        Not always, that's for services that explicitly bind to 127.0.0.1 rather than 'any'. It was one of a few things we added that helped squid+multi-WAN function in limited circumstances.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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