The tftp(1) utility is the user interface to the Internet
Trivial File Transfer Protocol (TFTP), which allows users to
transfer files to and from a remote computer. The remote
host can be specified on the command line, in which case
tftp(1) uses host as the default host for future
transfers (see the connect command later in this topic).
Set the host (and optionally port) for transfers.
Note that the TFTP protocol, unlike the File Transfer Protocol
(FTP), does not maintain connections between transfers. Thus, the
connect command does not actually create a connection, but
merely remembers what host is to be used for transfers. You do not
have to use the connect command; the remote host can be
specified as part of the get or put commands.
getfile1 file2 ... fileN
Get a file or set of files from the specified sources.
The source can be in one of two forms: a file name on the
remote host, if the host has already been specified, or a string of
the form hosts:filename to specify both a host and file name
at the same time. If the latter form is used, the last host name
specified becomes the default for future transfers.
Set the mode for transfers; transfer-mode can be either
ascii or binary. The default is ascii.
putfile1 file2 ... fileN remote-directory
Put a file or set of files to the specified remote file or
directory. The destination can be in one of two forms: a file name
on the remote host, if the host has already been specified, or a
string of the form hosts:filename to specify both a host and
file name at the same time. If the latter form is used, the host
name specified becomes the default for future transfers. If the
remote-directory form is used, the remote host is assumed to be a
computer based on the open standards.
Exit tftp(1). An end of file also exits.
retransmission-timeout Set the per-packet retransmission
time-out, in seconds.
Because there is no user login or validation within the TFTP
protocol, the remote site will probably have some sort of
file-access restrictions in place. The exact methods are specific
to each site and therefore difficult to document here.
The commands trace, verbose, and status are
good aids for debugging connection problems