This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 12 and 14 (spanning 2 versions)
Revision 12 as of 2013-05-01 12:59:32
Size: 2839
Editor: clementc
Revision 14 as of 2018-10-09 12:31:01
Size: 2629
Editor: AlexHammer
Comment: Listing the TFTP dissector as fully functional - verified in current release build
Deletions are marked like this. Additions are marked like this.
Line 20: Line 20:
 [[attachment:SampleCaptures/tftp_rrq.pcap]] Capture of a TFTP Read Request.

 [[attachment:SampleCaptures/tftp_wrq.pcap]] Capture of a TFTP Write Request.
 XXX - Add example traffic here (as plain text or Wireshark screenshot).
Line 26: Line 24:
The TFTP dissector is (fully functional, partially functional, not existing, ... whatever the current state is). The TFTP dissector is fully functional.
Line 34: Line 32:
XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.  [[attachment:SampleCaptures/tftp_rrq.pcap]] Capture of a TFTP Read Request.

 [[attachment:SampleCaptures/tftp_wrq.pcap]] Capture of a TFTP Write Request.

Trivial File Transfer Protocol (TFTP)

TFTP is used to transfer files in a very simple way.

Compared to other file transfer protcols (like: FTP or HTTP), TFTP is much simpler (and much smaller in code size) and therefore easier to implement. Because of this, it's often used in embedded devices (e.g. thin clients) to get files from a server at bootup time (typically in conjunction with BOOTP).

Sometimes TFTP is also used to upload firmware files from the user to an embedded device, but as these devices become more and more advanced, HTTP is more often used for this purpose today.


XXX - add a brief description of TFTP history

Protocol dependencies

  • UDP: Typically, TFTP uses UDP as its transport protocol. The well known UDP port for TFTP traffic is 69.

Example traffic

  • XXX - Add example traffic here (as plain text or Wireshark screenshot).


The TFTP dissector is fully functional.

Preference Settings

There are no TFTP specific preference settings.

Example capture file

Display Filter

A complete list of TFTP display filter fields can be found in the display filter reference

  • Show only the TFTP based traffic:


Capture Filter

You cannot directly filter TFTP protocols while capturing. However, if you know the UDP port used (see above), you could filter on that one; however, as a TFTP server will choose a unique port number from which to send the reponse, and will send it to the port number from which the request came, which is not likely to be a well known port number, a filter checking for UDP port 69 will capture only the initial TFTP request, not the response to that request or any subsequent packets in that TFTP conversation.


  • RFC 1350 THE TFTP PROTOCOL (REVISION 2) (obsoletes RFC 783)

  • RFC 2090 TFTP Multicast Option

  • RFC 2347 TFTP Option Extension

  • RFC 2348 TFTP Blocksize Option

  • RFC 2349 TFTP Timeout Interval and Transfer Size Options


TFTP (last edited 2018-10-09 12:31:01 by AlexHammer)