Server | Tftp

# Using tftp client (Linux/macOS)
tftp 192.168.1.100
get myfile.bin
quit
Every Linux distribution has a TFTP server via tftpd-hpa (HPA stands for H. Peter Anvin, the author).
To understand the TFTP server, you must distinguish it from its more famous cousin, FTP (File Transfer Protocol).
| Feature | FTP Server | TFTP Server |
| :--- | :--- | :--- |
| Authentication | Username & Password required | None (Anonymous only) |
| Transport Protocol | TCP (Reliable, connection-oriented) | UDP (Unreliable, connectionless) |
| Data Transfer | Complex commands (LIST, CD, GET, PUT) | Simple read/write requests (RRQ/WRQ) |
| Port Usage | Ports 20 & 21 (plus dynamic ports) | Single port: UDP 69 |
| Error Checking | Built-in (TCP guarantees delivery) | Application must handle timeouts/retries |
| File Browsing | Yes (List directories) | No (Must know exact file path) | TFTP Server
Because TFTP uses UDP (User Datagram Protocol) instead of TCP, it does not have the overhead of handshakes and acknowledgements. This makes TFTP servers incredibly lightweight—they can run on a router with 4MB of RAM or a Linux machine from 1995. However, UDP also means the protocol is prone to loss; it relies on a simple "timeout and retransmit" mechanism that is slow over high-latency links.
If you work in IT, specifically in networking or systems administration, a TFTP (Trivial File Transfer Protocol) server is one of those tools you rarely think about until you desperately need it. It isn't flashy, it doesn't have a GUI full of graphs, and it is intentionally simple. # Using tftp client (Linux/macOS)
tftp 192
The Verdict: A TFTP server is an essential utility for network engineers. It allows for the transfer of files (like router firmware or switch configurations) without the overhead of authentication or complex setup. While the protocol itself is insecure by modern standards, the software that runs it is vital for infrastructure management.

Cisco, Juniper, Arista, Ubiquiti, and HP all use TFTP to upgrade firmware on switches, routers, and firewalls. Cisco, Juniper, Arista, Ubiquiti, and HP all use
tftp localhost
tftp> get testfile.txt
tftp> put newfile.txt
tftp> quit

TFTP is inherently insecure. If you must run a TFTP server:

Modern best practice: Use TFTP only for the initial bootstrap (small file), then switch to HTTPS or SCP for the main data transfer.