[PR #55] [MERGED] Replace in.tftp server with dnsmasq, to add support for single-port TFTP #74

New issue

Closed

opened 2026-02-27 14:47:41 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 14:47:41 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netbootxyz/docker-netbootxyz/pull/55
Author: @dezeroku
Created: 1/31/2024
Status: ✅ Merged
Merged: 8/4/2024
Merged by: @antonym

Base: master ← Head: to-upstream

📝 Commits (1)

fe00be3 Replace in.tftp with dnsmasq, to add support for single-port TFTP

📊 Changes

3 files changed (+4 additions, -3 deletions)

View changed files

📝 Dockerfile (+1 -1)
📝 README.md (+1 -0)
📝 root/etc/supervisor.conf (+2 -2)

📄 Description

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!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netbootxyz/docker-netbootxyz/pull/55 **Author:** [@dezeroku](https://github.com/dezeroku) **Created:** 1/31/2024 **Status:** ✅ Merged **Merged:** 8/4/2024 **Merged by:** [@antonym](https://github.com/antonym) **Base:** `master` ← **Head:** `to-upstream` --- ### 📝 Commits (1) - [`fe00be3`](https://github.com/netbootxyz/docker-netbootxyz/commit/fe00be36f4def6107c6ec05715014f08079214e7) Replace in.tftp with dnsmasq, to add support for single-port TFTP ### 📊 Changes **3 files changed** (+4 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `Dockerfile` (+1 -1) 📝 `README.md` (+1 -0) 📝 `root/etc/supervisor.conf` (+2 -2) </details> ### 📄 Description 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](https://github.com/linuxserver/docker-netbootxyz/pull/40). 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! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>