Replace in.tftp server with dnsmasq, to add support for single-port TFTP #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dnsmasq provides TFTP server functionality that supports the optional
--tftp-single-port
argument.Essentialy, when this flag is provided, all TFTP connections (not only the initial one) are performed over port
69
.This makes it much easier to set up in environment with heavy NAT and/or firewall.
It comes in handy e.g. with the Kubernetes deployments.
Reasoning is basically the same as in parallel PR.
I've tested the changes in K8s environment (exposing only port 69 of the container) and with the example
docker-compose.yml
, connecting from a VM and a "real" device.Also documenting the
TFTPD_OPTS
env variable.The
--port=0
argument disables the built-in DNS server.Oh, and thanks for providing nice software!