Port69— TFTP
TFTP (Trivial File Transfer Protocol) runs on UDP 69 with no authentication and no directory listing. It exists for automated distribution — router firmware, PXE network boot, VoIP phone provisioning — where the client already knows the exact filename.
Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Configuration and troubleshooting
For TFTP failures: check the server with `systemctl status tftpd-hpa` (or atftp) and the root directory permissions. Files must be world-readable and case-sensitive on the client side. Allow UDP 69 — data transfers use negotiated high ports, so a stateful firewall handles them, but strict setups may need a TFTP conntrack helper.
Important limitations
TFTP has zero authentication: any client that guesses a filename can read it. Never expose it to the internet — keep it on an isolated management VLAN (PXE/VoIP).
Read-only checks: run on the server host
Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.
Linux
sudo ss -lunp 'sport = :69'macOS
sudo lsof -nP -iUDP:69Windows PowerShell
Get-NetUDPEndpoint -LocalPort 69Sources and review
Sources checked on:
This review covers the explanations and sources on this page, not your device or every community software entry below.
Software Using This Port (4 software)
Community software entries: links are references, not individual verification.
TFTP File Transfer
Trivial File Transfer Protocol
Usage Suggestions
- Before using port 69, please confirm it is not occupied by other services
- If you encounter port conflicts, consider using other ports or stopping the occupying service
Frequently asked questions
What is port 69 used for?
Port 69 sits in the File Sharing category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 69 TCP or UDP?
The registered protocol on this page is UDP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 69 is in use?
On Linux: sudo ss -tlnp 'sport = :69' for an exact port match. On macOS: sudo lsof -nP -iTCP:69 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 69 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 69 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication. The caution section on this page lists port-specific risks.
Quick Info
- Port
- 69
- Protocol
- UDP
- Categories
- File Sharing
- Usage Status
- 4 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction