Contents

TFTP Server

Serve files from a chosen folder over TFTP, read-only by default, with optional uploads for config backups.

Sidebar group: Servers · Works offline: yes on the local network (it listens only while you run it) · Needs admin rights: only to bind a port below 1024, such as 69 (see Platform notes)

When to use it

Quick start

  1. Click Choose folder and pick the folder to serve. Put the files the device needs in it.
  2. Set Port. 69 is standard; use 6969 if you do not want to grant admin rights and the client can use another port.
  3. Tick Writable (accept uploads) only if the device needs to send files to you.
  4. Click Start. The status line shows Serving <folder> on UDP <port> (read-only) or (read + write).
  5. On the device, point the TFTP transfer at this computer's IP address, for example 192.0.2.50.
  6. Watch the transfer table for progress and the result.
  7. Click Stop when done.

Inputs and options

Field What it means Default / accepted values
Choose folder The root folder. Every request is confined to this folder and its subfolders. Required
Port UDP port for incoming requests. Each transfer then runs on its own random high port, as TFTP specifies. 69; 1 to 65535
Writable (accept uploads) Accept write requests (PUT). When off, write requests are refused with an access violation. Off

When Writable is on and the server is stopped, the panel warns: any client that can reach this port can create or overwrite files in the chosen folder.

Supported TFTP options (RFC 2347 to 2349): blksize (clamped to 8 to 65464 bytes), tsize (the real file size on reads, echoed on writes) and timeout (1 to 255, acknowledged). Without options, the block size is 512 bytes.

Reading the results

The status line shows the folder, port and mode while running, and Stopped. afterwards.

The transfer table, newest first:

Requests refused before the transfer starts (file not found, uploads while Writable is off, paths outside the folder) are answered with a TFTP error to the client but do not add a row to the table. Check the client's error message in that case.

Worked example. A switch at 192.0.2.20 runs copy tftp://192.0.2.50/fw.bin flash:. The table shows GET, fw.bin, 192.0.2.20:49152, the growing size, then done. A later copy running-config tftp://192.0.2.50/sw1.cfg with Writable on shows PUT, sw1.cfg, and done. With Writable off, the switch reports an access violation error and no row is added.

What the results do and do not tell you

Online activity and privacy

The server listens on the chosen UDP port on all IPv4 interfaces only between Start and Stop. Any host that can reach the port can read any file in the folder, and with Writable on, write files to it. TFTP has no authentication or encryption, so files cross the network in clear text. Serve a folder that holds only what the device needs.

The app keeps nothing beyond the files clients upload into your folder. The transfer table is cleared on the next Start.

Export and projects

There is no export or "Add to project" for this tool. Uploaded files are saved directly in the served folder.

Platform notes

Troubleshooting

Error "Choose a folder to serve first." or "choose a folder to serve". No folder is set, or it no longer exists.

Error "cannot bind UDP port 69: permission denied. Ports below 1024 need admin/root; try a port such as 6969." Click Use port 6969 (no admin needed).

Error "cannot bind UDP port N: already in use." Another TFTP server (often a built-in OS service) holds the port. Stop it or pick another port.

Client reports "file not found" and no row appears. The file is not in the folder, or the name's case does not match (Linux and some macOS volumes are case sensitive).

Client reports "access violation" on a PUT and no row appears. Writable is off, or the target subfolder does not exist. If a row appears with access violation, the file could not be created or written (folder permissions, disk full).

Client reports "path escapes the served directory". The client asked for a path outside the folder.

Status "illegal TFTP operation" partway through. The client stopped acknowledging (timeout after 5 retries), sent an error, or you clicked Stop. A firewall blocking the per-transfer high port often shows as a transfer that starts but never progresses.

Nothing appears in the table and the client times out. The request is not reaching this computer. Check the device can reach the IP, the port, and the OS firewall.