bitlvl
EN

Port 69 TFTP · UDP

TFTP: trivial file transfer over UDP, with no authentication and no directory listing.

Port69
TransportUDP
ServiceTFTP — Trivial file transfer (PXE boot, network gear)
CategoryFile transfer and sharing
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedNo, plaintext
ExposurePrivate network or VPN only

What runs on port 69

TFTP: trivial file transfer over UDP, with no authentication and no directory listing. It is how PXE boot loads a kernel, how switches and phones fetch firmware and configs, and how a lot of network gear still backs up its configuration. The request goes to port 69; the transfer continues from a random port, which confuses stateful firewalls without a TFTP helper.

Software that uses it: tftpd-hpa · atftpd · dnsmasq (built-in TFTP) · PXE/iPXE

Should port 69 be open?

Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.

Check port 69

# on the host: is anything listening, and which process?
ss -lunp 'sport = :69'
sudo lsof -i :69

# from another machine: is it reachable?
nc -zuv host 69
sudo nmap -sU -p 69 host

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 69

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 69 proto udp
sudo ufw deny 69/udp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 udp dport 69 accept
nft add rule inet filter input udp dport 69 drop

# iptables (legacy)
iptables -A INPUT -p udp --dport 69 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p udp --dport 69 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=69 protocol=udp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 69" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 69 TCP or UDP?

UDP. TFTP is datagram-based; TCP 69 is not used by it.

Is port 69 encrypted?

No, plaintext. Anything sent over it can be read by whoever is on the path, so it belongs on a trusted network or inside a VPN or SSH tunnel.

How do I check whether port 69 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 69 and which process. From another machine, nc -zv host 69 -u or nmap -p 69 -sU host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can TFTP run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.