ATFTP(1)ATFTP(1)NAMEatftp - TFTP client (RFC1350).
SYNOPSISatftp [options] [host [port]]
DESCRIPTIONatftp can be used interactively or in batch mode to retrieve files from
TFTP servers. When used interactively, a summary of the commands can be
printed by typing 'help'. This TFTP client support all basic feature
from RFC1350, RFC2347, RFC2348 and RFC2349. It also support multicast
implementation of RFC2090 and mtftp as defined in the PXE specifica‐
This program supports both the usual GNU command line syntax, with long
options starting with two dashes (`-') as well as short options. Some
options are usable in batch mode only, they have no meaning when atftp
is use interactively. A description of the options is included below.
Non interactive invocation only. Instruct atftp to get file.
--mget Non interactive invocation only. Used to get file from a mtftp
Non interactive invocation only. Instruct atftp to put file.
Non interactive invocation only. The client side file name to
read or write. Must be used in conjunction with --get or --put.
Non interactive invocation only. The server side file name to
get or put. Must be used in conjunction with --get or --put.
Number of seconds for timeout, client side. Default is 5 sec‐
--option <"name value">
Set option "name" to "value". This command support exactly the
same arguments as the interactive one. For example, use:
--option blksize 1428 to configure block size.
--mtftp <"name value">
Set mtftp possible options. Accept the same options as the
interactive mtftp command. For example, use: --mtftp client-port
76 to configure client side port to use.
See atftpd's man page.
Instruct atftp to be verbose. It will print more information
about what's going on.
This is useful for debugging purpose to display all packet going
to and from the network.
Print a summary of command line arguments.
This manual page was written by Remi Lefebvre <firstname.lastname@example.org> and
Jean-Pierre Lefebvre <email@example.com>.
December 27, 2000 ATFTP(1)