| 1 | .\" Copyright (c) 1990 The Regents of the University of California. |
| 2 | .\" All rights reserved. |
| 3 | .\" |
| 4 | .\" Redistribution and use in source and binary forms, with or without |
| 5 | .\" modification, are permitted provided that the following conditions |
| 6 | .\" are met: |
| 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. All advertising materials mentioning features or use of this software |
| 13 | .\" must display the following acknowledgement: |
| 14 | .\" This product includes software developed by the University of |
| 15 | .\" California, Berkeley and its contributors. |
| 16 | .\" 4. Neither the name of the University nor the names of its contributors |
| 17 | .\" may be used to endorse or promote products derived from this software |
| 18 | .\" without specific prior written permission. |
| 19 | .\" |
| 20 | .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND |
| 21 | .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE |
| 22 | .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE |
| 23 | .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE |
| 24 | .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL |
| 25 | .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS |
| 26 | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) |
| 27 | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT |
| 28 | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY |
| 29 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF |
| 30 | .\" SUCH DAMAGE. |
| 31 | .\" |
| 32 | .\" @(#)tftp.1 5.4 (Berkeley) 4/22/91 |
| 33 | .\" |
| 34 | .Dd April 22, 1991 |
| 35 | .Dt TFTP 1 |
| 36 | .Os BSD 4.3 |
| 37 | .Sh NAME |
| 38 | .Nm tftp |
| 39 | .Nd trivial file transfer program |
| 40 | .Sh SYNOPSIS |
| 41 | .Nm tftp |
| 42 | .Op Ar host |
| 43 | .Sh DESCRIPTION |
| 44 | .Nm Tftp |
| 45 | is the user interface to the Internet |
| 46 | .Tn TFTP |
| 47 | (Trivial File Transfer Protocol), |
| 48 | which allows users to transfer files to and from a remote machine. |
| 49 | The remote |
| 50 | .Ar host |
| 51 | may be specified on the command line, in which case |
| 52 | .Nm tftp |
| 53 | uses |
| 54 | .Ar host |
| 55 | as the default host for future transfers (see the |
| 56 | .Cm connect |
| 57 | command below). |
| 58 | .Sh COMMANDS |
| 59 | Once |
| 60 | .Nm tftp |
| 61 | is running, it issues the prompt |
| 62 | .LI tftp> |
| 63 | and recognizes the following commands: |
| 64 | .Pp |
| 65 | .Bl -tag -width verbose -compact |
| 66 | .It Cm \&? Ar command-name ... |
| 67 | Print help information. |
| 68 | .Pp |
| 69 | .It Cm ascii |
| 70 | Shorthand for "mode ascii" |
| 71 | .Pp |
| 72 | .It Cm binary |
| 73 | Shorthand for "mode binary" |
| 74 | .Pp |
| 75 | .It Cm connect Ar host-name Op Ar port |
| 76 | Set the |
| 77 | .Ar host |
| 78 | (and optionally |
| 79 | .Ar port ) |
| 80 | for transfers. |
| 81 | Note that the |
| 82 | .Tn TFTP |
| 83 | protocol, unlike the |
| 84 | .Tn FTP |
| 85 | protocol, |
| 86 | does not maintain connections betweeen transfers; thus, the |
| 87 | .Cm connect |
| 88 | command does not actually create a connection, |
| 89 | but merely remembers what host is to be used for transfers. |
| 90 | You do not have to use the |
| 91 | .Cm connect |
| 92 | command; the remote host can be specified as part of the |
| 93 | .Cm get |
| 94 | or |
| 95 | .Cm put |
| 96 | commands. |
| 97 | .Pp |
| 98 | .It Cm get Ar filename |
| 99 | .It Cm get Ar remotename localname |
| 100 | .It Cm get Ar file1 file2 ... fileN |
| 101 | Get a file or set of files from the specified |
| 102 | .Ar sources . |
| 103 | .Ar Source |
| 104 | can be in one of two forms: |
| 105 | a filename on the remote host, if the host has already been specified, |
| 106 | or a string of the form |
| 107 | .Ar hosts:filename |
| 108 | to specify both a host and filename at the same time. |
| 109 | If the latter form is used, |
| 110 | the last hostname specified becomes the default for future transfers. |
| 111 | .Pp |
| 112 | .It Cm mode Ar transfer-mode |
| 113 | Set the mode for transfers; |
| 114 | .Ar transfer-mode |
| 115 | may be one of |
| 116 | .Em ascii |
| 117 | or |
| 118 | .Em binary . |
| 119 | The default is |
| 120 | .Em ascii . |
| 121 | .Pp |
| 122 | .It Cm put Ar file |
| 123 | .It Cm put Ar localfile remotefile |
| 124 | .It Cm put Ar file1 file2 ... fileN remote-directory |
| 125 | Put a file or set of files to the specified |
| 126 | remote file or directory. |
| 127 | The destination |
| 128 | can be in one of two forms: |
| 129 | a filename on the remote host, if the host has already been specified, |
| 130 | or a string of the form |
| 131 | .Ar hosts:filename |
| 132 | to specify both a host and filename at the same time. |
| 133 | If the latter form is used, |
| 134 | the hostname specified becomes the default for future transfers. |
| 135 | If the remote-directory form is used, the remote host is |
| 136 | assumed to be a |
| 137 | .Tn UNIX |
| 138 | machine. |
| 139 | .Pp |
| 140 | .It Cm quit |
| 141 | Exit |
| 142 | .Nm tftp . |
| 143 | An end of file also exits. |
| 144 | .Pp |
| 145 | .It Cm rexmt Ar retransmission-timeout |
| 146 | Set the per-packet retransmission timeout, in seconds. |
| 147 | .Pp |
| 148 | .It Cm status |
| 149 | Show current status. |
| 150 | .Pp |
| 151 | .It Cm timeout Ar total-transmission-timeout |
| 152 | Set the total transmission timeout, in seconds. |
| 153 | .Pp |
| 154 | .It Cm trace |
| 155 | Toggle packet tracing. |
| 156 | .Pp |
| 157 | .It Cm verbose |
| 158 | Toggle verbose mode. |
| 159 | .El |
| 160 | .Sh BUGS |
| 161 | .Pp |
| 162 | Because there is no user-login or validation within |
| 163 | the |
| 164 | .Tn TFTP |
| 165 | protocol, the remote site will probably have some |
| 166 | sort of file-access restrictions in place. The |
| 167 | exact methods are specific to each site and therefore |
| 168 | difficult to document here. |
| 169 | .Sh HISTORY |
| 170 | The |
| 171 | .Nm |
| 172 | command appeared in |
| 173 | .Bx 4.3 . |