Hi Simon,

We're happy to use dnsmasq for organize network booting in Kubernetes, it
have everything need: DNS-, DHCP- and TFTP-servers.

The only problem is that TFTP protocol in its reference implementation is
not working behind the NAT, because always sends reply packets from random

Note that Kubernetes uses NAT for external services, so it's not possible
to run TFTP-server for external clients there. There is one proposed
solution for that, it suggests moving away from the RFC and implement
--single-port option for always reply from the same port which was
requested by the client.

In this way, the TFTP-packets can be simple NAT'ed back to the client side.

Take a look on unique features for go-tftp implementation:

And its command line client:

Best regards
- kvaps
Dnsmasq-discuss mailing list

Reply via email to