Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace in.tftp server with dnsmasq, to add support for single-port TFTP #55

Merged
merged 1 commit into from
Aug 4, 2024

Conversation

dezeroku
Copy link
Contributor

@dezeroku dezeroku commented Jan 31, 2024

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!

@antonym
Copy link
Member

antonym commented Feb 2, 2024

I think the change makes sense, I'll need to spend some time to test and make sure there aren't any issues switching packages.

@antonym antonym merged commit 040c56f into netbootxyz:master Aug 4, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants