TFTP(1) | General Commands Manual | TFTP(1) |
tftp
— trivial
file transfer program
tftp |
[-e ] [host]
[port] |
tftp
is the user interface to the Internet
TFTP (Trivial File Transfer Protocol), which allows users to transfer files
to and from a remote machine. The remote host (and
optional port) may be specified on the command line,
in which case tftp
uses host
(and port) as the default for future transfers (see
the connect
command below).
The optional -e
argument sets a binary
transfer mode as well as setting the extended options as if
tout
, tsize
, and
blksize 65464
, had been given.
The Multicast TFTP option is supported in open-loop (i.e., "slave-only") mode based on IETF draft-dion-tftp-multicast-option-01.txt (May 2002), which in turn was based on RFC2026.
Once tftp
is running, it issues the prompt
‘tftp>
’ and recognizes the
following commands:
?
command-name ...ascii
binary
blksize
blk-sizeget
or put
is 65535, the
default block size of 512 bytes only allows a maximum of just under 32
megabytes to be transferred. The value given for
blk-size must be between 8 and 65464, inclusive.
Note that many servers will not respect this option.
connect
host-name [port]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.
get
filenameget
remotename localnameget
file1 file2 ... fileNmode
transfer-modeput
fileput
localfile remotefileput
file1 file2 ... fileN remote-directoryquit
tftp
. An end of file also exits.
rexmt
retransmission-timeoutstatus
timeout
total-transmission-timeouttout
trace
tsize
verbose
The tftp
command appeared in
4.3BSD. IPv6 support was implemented by WIDE/KAME
project in 1999. TFTP options were implemented by Wasabi Systems, Inc., in
2003, and first appeared in NetBSD 2.0. Multicast
TFTP was implemented by Jared D. McNeill in 2006,
and first appeared in NetBSD 4.0.
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.
July 23, 2006 | NetBSD 10.99 |