Categories

Category cover

Automation
43 posts

Category cover

Security
20 posts

Category cover

Notes
19 posts

Category cover

Personal Security
15 posts

Category cover

CISO
14 posts

Category cover

Infrastructure
12 posts

Category cover

Learning paths
9 posts

Category cover

OT/ICS
6 posts

Category cover

UNetLab
4 posts

Category cover

Books
3 posts

Category cover

Write-up
3 posts

Category cover

OSInt
2 posts

Category cover

My life
1 posts

A Cisco device as a TFTP server

Andrea Dainese
September 12, 2013
Post cover

TFTP or Trivial File Transfer Protocol is a simple file transfer protocol. TFTP uses UDP port 69, no authentication or encryption is supported, and directory navigation is not possible. Three file transfer methods are available: netascii (or ASCII for text files), octet (or image for binary files), and mail (not used anymore).

A TFTP client sends to the server a read request (RRW or Read ReQuest) or a written request (WRQ or Write ReQuest) using UDP protocol; the destination port is 69 and the source port is random (X). The TFTP server answers to the client with an ACK using a random source port (Y). Next data transfer will use only UDP ports X and Y (port 69 is not used anymore); each sent data packet (DAT) will be acknowledged (ACK).

Client

From an IOS device, TFTP can be used as a “redirection” destination:

show tech-support | redirect tftp://192.168.10.1/Router_tech-support-20120819

TFTP can be used also to transfer files from and to the server:

copy tftp://192.168.10.1/ios/c180x-advipservicesk9-mz.124-9.T7.bin flash:

Server

A Cisco router can act as a TFTP server, allowing remote clients to get locally stored files:

tftp-server flash:c180x-advipservicesk9-mz.124-9.T7.bin

Each local file must be declared as a TFTP file.