tftp [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 as the default host, and if specified, port as the default port, for future transfers. See the connect command below.
Once tftp is running, it issues the prompt tftp> and recognizes the following commands:
put localfile remotefile
put filename1 filename2 ... filenameN remote-directory
to specify both a host and filename at the same time. If the latter form is used, the specified host becomes the default for future transfers. If the remote-directory form is used, the remote host is assumed to be running the UNIX system.
The host can be a host name (see hosts(5)) or an IPv4 or IPv6 address string (see inet(4P) or inet6(4P)). Since IPv6 addresses already contain ":"s, the host should be enclosed in square brackets when an IPv6 address is used. Otherwise, the first occurrence of a colon will be interpreted as the separator between the host and the filename. For example,
Files may be written only if they already exist and are publicly writable. See in.tftpd(8).
get remotename localname
get filename1 filename2 filename3 ... filenameN
to specify both a host and filename at the same time. If the latter form is used, the last host specified becomes the default for future transfers. See the put command regarding specifying a host.
? [ command-name ... ]
inet(4P), inet6(4P), hosts(5), attributes(7), in.tftpd(8)
Malkin, G. and Harkin, A. RFC 2347, TFTP Option Extension. The Internet Society. May 1998
Malkin, G. and Harkin, A. RFC 2348, TFTP Blocksize Option. The Internet Society. May 1998
Malkin, G. and Harkin, A. RFC 2349, TFTP Timeout Interval and Transfer Size Options. The Internet Society. May 1998
Sollins, K.R. RFC 1350, The TFTP Protocol (Revision 2). Network Working Group. July 1992.
The default transfer-mode is ascii. This differs from pre-SunOS 4.0 and pre-4.3BSD systems, so explicit action must be taken when transferring non-ASCII binary files such as executable commands.
Because there is no user-login or validation within the TFTP protocol, many remote sites restrict file access in various ways. Approved methods for file access are specific to each site, and therefore cannot be documented here.
When using the get command to transfer multiple files from a remote host, three or more files must be specified. If two files are specified, the second file is used as a local file.
With the default block size of 512 octets and a 16-bit block counter, some TFTP implementations might have problems with files over 33,553,919 octets (513 octets short of 32MB) in size. The Solaris implementation can transfer files up to 4GB in size.
By default, the Solaris TFTP client does not enable the blocksize or transfer size options. Setting the blocksize option to a higher value is sometimes useful as a workaround when dealing with peers that have a 32MB limit.
|May 7, 2007||OmniOS|