<![CDATA[Outbound IP from 127.0.0.1]]>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 ?

]]>https://forum.netgate.com/topic/103271/outbound-ip-from-127-0-0-1RSS for NodeSun, 17 May 2026 23:57:13 GMTTue, 26 Jul 2016 10:15:28 GMT60<![CDATA[Reply to Outbound IP from 127.0.0.1 on Tue, 26 Jul 2016 14:57:54 GMT]]>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.

]]>https://forum.netgate.com/post/639929https://forum.netgate.com/post/639929Tue, 26 Jul 2016 14:57:54 GMT<![CDATA[Reply to Outbound IP from 127.0.0.1 on Tue, 26 Jul 2016 14:48:59 GMT]]>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"

]]>https://forum.netgate.com/post/639925https://forum.netgate.com/post/639925Tue, 26 Jul 2016 14:48:59 GMT<![CDATA[Reply to Outbound IP from 127.0.0.1 on Tue, 26 Jul 2016 14:14:31 GMT]]>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.

]]>https://forum.netgate.com/post/639908https://forum.netgate.com/post/639908Tue, 26 Jul 2016 14:14:31 GMT