<![CDATA[TFTP Across Subnets]]>Hi @Derelict did you apply and voodoo to enable cross subnet TFTP to function? I have rules enabling outbound and response traffic but I still see errors as though the ACK is being seen.

tftplogs.png

and my tftp session from 192.168.20.99 shows...

tftp> get test.txt
getting from 192.168.10.43:test.txt to test.txt [netascii]
sent RRQ <file=test.txt, mode=netascii>
sent RRQ <file=test.txt, mode=netascii>
sent RRQ <file=test.txt, mode=netascii>
sent RRQ <file=test.txt, mode=netascii>
sent RRQ <file=test.txt, mode=netascii>
Transfer timed out.

any tips greatly appreciated,

]]>https://forum.netgate.com/topic/158553/tftp-across-subnetsRSS for NodeTue, 06 Oct 2026 06:03:56 GMTMon, 23 Nov 2020 06:16:32 GMT60<![CDATA[Reply to TFTP Across Subnets on Mon, 23 Nov 2020 20:17:10 GMT]]>@Derelict thank you, its likely something in the docker / macvlan configuration I've not wrapped my head round yet then.

]]>https://forum.netgate.com/post/947171https://forum.netgate.com/post/947171Mon, 23 Nov 2020 20:17:10 GMT<![CDATA[Reply to TFTP Across Subnets on Mon, 23 Nov 2020 13:26:55 GMT]]>No. Things like that are usually a firewall on the target host prohibiting connections from "foreign" subnets.

That or the default gateway on the target host is not set properly.

]]>https://forum.netgate.com/post/947084https://forum.netgate.com/post/947084Mon, 23 Nov 2020 13:26:55 GMT