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

    Outbound IP from 127.0.0.1

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 1.6k 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.
    • S
      sjag
      last edited by

      I have public IP /24
      IPv4 interface is XXX.XXX.10.2

      I set outbound NAT for 127.0.0.0/8 to NAT address XXX.XXX.10.111 (address is add as IP Alias)

      I use tftp helper to boot pxe, but outgoing IP is XXX.XXX.10.2 (not XXX.XXX.10.111 set in outbound nat)

      172.16.0.250:2070 -> 127.0.0.1:6969/XXX.XXX.10.2:59301 -> YY.YYY.YYY.9:69 "RRQ pxelinux.0"

      How can I set outbound IP XXX.XXX.10.111 to TFTP helper ?

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

        You'd have to match it by port number in the outbound NAT.

        The source of 127.0.0.1 for NAT is for daemons which only bind to 127.0.0.1 and nothing else.

        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
        • S
          sjag
          last edited by

          I set:
          Interface: WAN
          Source: any
          Source Port: *
          Destination: *
          Destination Port: *
          NAT Address: XXX.XXX.10.111

          as firts rule in outbound NAT

          but in log is 172.16.0.251:2070 -> 127.0.0.1:6969/XXX.XXX.10.2:60155 ->YY.YYY194.9:69 "RRQ pxelinux.0"

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

            It will show that in the log, but the state table should show it getting NAT applied.

            Still, a NAT rule like that with a source of any is an awful idea. Match the traffic more precisely (source = your WAN IP address, destination = any, port 69)

            Though TFTP is a mess of a protocol, it'll still probably need some other nonsense to make it work.

            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.