TFTP is a simple, lockstep protocol used to transfer files. It was first defined in 1981 (RFC 783) and later updated in RFC 1350. Unlike its more famous sibling, FTP (File Transfer Protocol), TFTP is designed to be so small it can fit inside the read-only memory (ROM) of hardware devices.
It operates on UDP port 69, unlike FTP which uses TCP ports 20 and 21. This choice of User Datagram Protocol (UDP) is a double-edged sword: it makes the protocol extremely lightweight with low overhead, but it also means the protocol itself must handle packet loss and order, as UDP does not guarantee delivery. TFTP Server
VoIP phones from Cisco, Avaya, or Polycom are dumb devices when powered on. They request an IP via DHCP, and the DHCP server tells them the IP of a TFTP Server. The phone then downloads SEP<MACADDRESS>.cnf.xml to register with the call manager. TFTP is a simple, lockstep protocol used to transfer files
| Server | Platform | Features |
| :--- | :--- | :--- |
| tftpd-hpa | Linux (Open Source) | Supports -s (secure chroot), -c (allow new files), -l (logging), block size negotiation. |
| atftpd | Linux, FreeBSD | Multi-threaded, IPv6, PXE support, runs as daemon or from inetd. |
| Solarwinds TFTP | Windows (Free) | GUI, syslog integration, transfer logging, used primarily for network device backups. |
| PRTG TFTP Server | Windows | Part of PRTG monitoring suite; limited to 30 sensors (free version). |
| Cisco IOS | Embedded in routers/switches | tftp-server flash:config.cfg command; used for IOS upgrades and config distribution. | It operates on UDP port 69 , unlike
SolarWinds is the industry standard for network monitoring, and their free TFTP server tool is arguably the most popular standalone option.
To truly master the TFTP Server, you must understand its basic packet structure. RFC 1350 defines five packet types:
After the initial UDP/69 request, the server spawns a dynamic high port for the remainder of the transfer, avoiding port 69 collisions.