1 .\" Copyright (c) 1990, 1993, 1994
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)tftp.1 8.2 (Berkeley) 4/18/94
29 .\" $FreeBSD: src/usr.bin/tftp/tftp.1,v 1.4.2.7 2002/06/21 15:29:33 charnier Exp $
30 .\" $DragonFly: src/usr.bin/tftp/tftp.1,v 1.5 2007/11/23 23:16:37 swildner Exp $
37 .Nd trivial file transfer program
44 utility is the user interface to the Internet
46 (Trivial File Transfer Protocol),
47 which allows users to transfer files to and from a remote machine.
50 may be specified on the command line, in which case
54 as the default host for future transfers (see the
60 is running, it issues the prompt
62 and recognizes the following commands:
64 .Bl -tag -width verbose -compact
65 .It Cm \&? Ar command-name ...
66 Print help information.
69 Shorthand for "mode ascii"
72 Shorthand for "mode binary"
74 .It Cm connect Ar host-name Op Ar port
85 does not maintain connections between transfers; thus, the
87 command does not actually create a connection,
88 but merely remembers what host is to be used for transfers.
89 You do not have to use the
91 command; the remote host can be specified as part of the
97 .It Cm get Ar filename
98 .It Cm get Ar remotename localname
99 .It Cm get Ar file1 file2 ... fileN
100 Get a file or set of files from the specified
103 can be in one of two forms:
104 a filename on the remote host, if the host has already been specified,
105 or a string of the form
107 to specify both a host and filename at the same time.
108 If the latter form is used,
109 the last hostname specified becomes the default for future transfers.
111 .It Cm mode Ar transfer-mode
112 Set the mode for transfers;
122 .It Cm put Ar localfile remotefile
123 .It Cm put Ar file1 file2 ... fileN remote-directory
124 Put a file or set of files to the specified
125 remote file or directory.
127 can be in one of two forms:
128 a filename on the remote host, if the host has already been specified,
129 or a string of the form
131 to specify both a host and filename at the same time.
132 If the latter form is used,
133 the hostname specified becomes the default for future transfers.
134 If the remote-directory form is used, the remote host is
138 If you need to specify IPv6 numeric address to
140 wrap them using square bracket like
142 to disambiguate the colon.
147 An end of file also exits.
149 .It Cm rexmt Ar retransmission-timeout
150 Set the per-packet retransmission timeout, in seconds.
155 .It Cm timeout Ar total-transmission-timeout
156 Set the total transmission timeout, in seconds.
159 Toggle packet tracing.
170 Because there is no user-login or validation within
173 protocol, the remote site will probably have some
174 sort of file-access restrictions in place. The
175 exact methods are specific to each site and therefore
176 difficult to document here.
178 Files larger than 33488896 octets (65535 blocks) cannot be transferred
179 without client and server supporting blocksize negotiation (RFC 1783).