| FTP(1) | General Commands Manual | FTP(1) |
ftp —
ftp |
[-46AadefginpRtVv?] [-N
netrc] [-o
output] [-P
port] [-q
quittime] [-r
retry] [-s
srcaddr] [-T
dir,max[,inc]]
[-x xfersize]
[[user@]host
[port]]
[[user@]host:[path][/]]
[file:///path]
[ftp://[user[:password]@]host[:port]/path[/][;type=type]]
[http://[user[:password]@]host[:port]/path]
[https://[user[:password]@]host[:port]/path]
... |
ftp |
-u
url file ... |
ftp is the user interface to the Internet standard File
Transfer Protocol. The program allows a user to transfer files to and from a
remote network site.
The last five arguments will fetch a file using the FTP or HTTP protocols, or by direct copying, into the current directory. This is ideal for scripts. Refer to AUTO-FETCHING FILES below for more information.
Options may be specified at the command line, or to the command interpreter.
-4ftp to only use IPv4 addresses.-6ftp to only use IPv6 addresses.-Aftp will try to
use passive mode FTP and fall back to active mode if passive is not
supported by the server. This option causes ftp to
always use an active connection. It is only useful for connecting to very
old servers that do not implement passive mode properly.-aftp to bypass normal login procedure, and
use an anonymous login instead.-d-e-f-g-i-N
netrc-nftp from attempting
“auto-login” upon initial connection for non auto-fetch
transfers. If auto-login is enabled, ftp will
check the .netrc (see below) file in the user's
home directory for an entry describing an account on the remote machine.
If no entry exists, ftp will prompt for the remote
machine login name (default is the user identity on the local machine),
and, if necessary, prompt for a password and an account with which to
login. To override the auto-login for auto-fetch transfers, specify the
username (and optionally, password) as appropriate.-o
output-’ or doesn't start with
‘|’, then only the first file
specified will be retrieved into output; all other
files will be retrieved into the basename of their remote name.-P
port-pftp
now tries to use passive mode by default, falling back to active mode if
the server does not support passive connections.-q
quittime-R-r
wait-s
srcaddr-t-T
direction,maximum[,increment]rate for more information.-u
url file ...ftp://’ URL types as supported by
auto-fetch (with an optional target filename for single file uploads), and
file is one or more local files to be uploaded.-Vverbose and
progress, overriding the default of enabled when
output is to a terminal.-vverbose and
progress. This is the default if output is to a
terminal (and in the case of progress,
ftp is the foreground process). Forces
ftp to show all responses from the remote server,
as well as report on data transfer statistics.-x
xfersizexferbuf
for more information.-?The client host with which ftp is to
communicate may be specified on the command line. If this is done,
ftp will immediately attempt to establish a
connection to an FTP server on that host; otherwise,
ftp will enter its command interpreter and await
instructions from the user. When ftp is awaiting
commands from the user the prompt
‘ftp>’ is provided to the user. The
following commands are recognized by ftp:
!
[command [args]]$
macro-name [args]macdef command. Arguments are passed to the
macro unglobbed.account
[passwd]append
local-file [remote-file]ntrans or nmap setting.
File transfer uses the current settings for type,
format, mode, and
structure.asciitype to network ASCII. This
is the default type.bellbinarytype to support binary image
transfer.byeftp. An end of file will also terminate the
session and exit.caseget, mget and
mput commands. When case
is on (default is off), remote computer file names with all letters in
upper case are written in the local directory with the letters mapped to
lower case.cd
remote-directorycdupchmod
mode remote-fileclosecrcr is on (the default), carriage
returns are stripped from this sequence to conform with the
UNIX single linefeed record delimiter. Records on
non-UNIX remote systems may contain single
linefeeds; when an ascii type transfer is made, these linefeeds may be
distinguished from a record delimiter only when cr
is off.debug
[debug-value]ftp prints each command sent to the remote
machine, preceded by the string
‘-->’.delete
remote-filedir
[remote-path [local-file]]ls
-l’. If remote-path is left
unspecified, the current working directory is used. If interactive
prompting is on, ftp will prompt the user to
verify that the last argument is indeed the target local file for
receiving dir output. If no local file is
specified, or if local-file is
‘-’, the output is sent to the
terminal.disconnectclose.editepsv,
epsv4, epsv6EPSV and
EPRT commands on all IP, IPv4, and IPv6
connections respectively. First try
EPSV/EPRT, and then
PASV/PORT. This is enabled
by default. If an extended command fails then this option will be
temporarily disabled for the duration of the current connection, or until
epsv, epsv4, or
epsv6 is executed again.exitbye.featuresFEAT command).fget
localfileform
formatform to
format. The default (and only supported) format is
‘non-print’.ftp
host [port]open.gate
[host [port]]FTPSERVER environment variable). If
host is given, then gate-ftp mode will be enabled,
and the gate-ftp server will be set to host. If
port is also given, that will be used as the port to
connect to on the gate-ftp server.get
remote-file [local-file]case, ntrans, and
nmap settings. The current settings for
type, form,
mode, and structure are
used while transferring the file.globmdelete,
mget, mput, and
mreget. If globbing is turned off with
glob, the file name arguments are taken literally
and not expanded. Globbing for mput is done as in
csh(1). For
mdelete, mget, and
mreget, each remote file name is expanded
separately on the remote machine and the lists are not merged. Expansion
of a directory name is likely to be different from expansion of the name
of an ordinary file: the exact result depends on the foreign operating
system and FTP server, and can be previewed by doing
‘mls remote-files -’. Note:
mget, mput and
mreget are not meant to transfer entire directory
subtrees of files. That can be done by transferring a
tar(1) archive of the subtree
(in binary mode).hash
[size]#’) printing for
each data block transferred. The size of a data block defaults to 1024
bytes. This can be changed by specifying size in
bytes. Enabling hash disables
progress.help
[command]ftp prints a list of the known commands.idle
[seconds]imagebinary.lcd
[directory]less
filepage.lpage
local-fileset pager option.lpwdls
[remote-path [local-file]]dir.macdef
macro-nameopen command), and remain defined until a
close command is executed. To invoke a macro, use
the $ command (see above).
The macro processor interprets
‘$’ and
‘\’ as special characters. A
‘$’ followed by a number (or
numbers) is replaced by the corresponding argument on the macro
invocation command line. A ‘$’
followed by an ‘i’ signals the
macro processor that the executing macro is to be looped. On the first
pass ‘$i’ is replaced by the first
argument on the macro invocation command line, on the second pass it is
replaced by the second argument, and so on. A
‘\’ followed by any character is
replaced by that character. Use the
‘\’ to prevent special treatment
of the ‘$’.
mdelete
[remote-files]mdir
remote-files local-filedir, except multiple remote files may be
specified. If interactive prompting is on, ftp
will prompt the user to verify that the last argument is indeed the target
local file for receiving mdir output.mget
remote-filesget for each file name thus produced. See
glob for details on the filename expansion.
Resulting file names will then be processed according to
case, ntrans, and
nmap settings. Files are transferred into the
local working directory, which can be changed with
lcd directory; new local
directories can be created with ! mkdir
directory.mkdir
directory-namemls
remote-files local-filels, except multiple remote files may be
specified, and the local-file must be specified. If
interactive prompting is on, ftp will prompt the
user to verify that the last argument is indeed the target local file for
receiving mls output.mlsd
[remote-path]MLSD. The format of display can be changed
with ‘remopts mlst
...’.mlst
[remote-path]MLST. The format of display can be changed
with ‘remopts mlst
...’.mode
mode-namemode to
mode-name. The default (and only supported) mode is
‘stream’.modtime
remote-fileRFC 2822 format.more
filepage.mput
local-filesput for each file in the resulting list. See
glob for details of filename expansion. Resulting
file names will then be processed according to
ntrans and nmap
settings.mreget
remote-filesmget, but performs a
reget instead of get.msend
local-filesmput.newer
remote-file [local-file]newer. Otherwise, this command is identical to
get.nlist
[remote-path [local-file]]ls.nmap
[inpattern outpattern]mput
commands and put commands issued without a
specified remote target filename. If arguments are specified, local
filenames are mapped during mget commands and
get commands issued without a specified local
target filename. This command is useful when connecting to a
non-UNIX remote computer
with different file naming conventions or practices. The mapping follows
the pattern set by inpattern and
outpattern.
inpattern is a template for incoming
filenames (which may have already been processed according to the
ntrans and case
settings). Variable templating is accomplished by including the
sequences ‘$1’,
‘$2’, ...,
‘$9’ in
inpattern. Use
‘\’ to prevent this special
treatment of the ‘$’ character.
All other characters are treated literally, and are used to determine
the nmap [inpattern]
variable values. For example, given inpattern
‘$1.$2’ and the remote file name
‘mydata.data’,
‘$1’ would have the value
‘mydata’, and
‘$2’ would have the value
‘data’.
The outpattern determines the resulting
mapped filename. The sequences
‘$1’,
‘$2’, ...,
‘$9’ are replaced by any value
resulting from the inpattern template. The
sequence ‘$0’ is replaced by the
original filename. Additionally, the sequence
[seq1,seq2]
is replaced by seq1 if seq1
is not a null string; otherwise it is replaced by
seq2. For example, the command
nmap $1.$2.$3
[$1,$2].[$2,file]would yield the output filename
‘myfile.data’ for input filenames
‘myfile.data’ and
‘myfile.data.old’,
‘myfile.file’ for the input
filename ‘myfile’, and
‘myfile.myfile’ for the input
filename ‘.myfile’. Spaces may be
included in outpattern, as in the example:
nmap $1 sed s/ *$// >
$1Use the ‘\’ character to
prevent special treatment of the
‘$’,
‘[’,
‘]’, and
‘,’ characters.
ntrans
[inchars [outchars]]mput commands and
put commands issued without a specified remote
target filename. If arguments are specified, characters in local filenames
are translated during mget commands and
get commands issued without a specified local
target filename. This command is useful when connecting to a
non-UNIX remote computer
with different file naming conventions or practices. Characters in a
filename matching a character in inchars are
replaced with the corresponding character in
outchars. If the character's position in
inchars is longer than the length of
outchars, the character is deleted from the file
name.open
host [port]ftp will attempt to contact an FTP server at that
port. If the set auto-login option is on
(default), ftp will also attempt to automatically
log the user in to the FTP server (see below).page
filefile and display with the program
specified by the set pager option.passive
[auto]auto is given, act as if
FTPMODE is set to ‘auto’. If passive
mode is turned on (default), ftp will send a
PASV command for all data connections instead of a
PORT command. The PASV
command requests that the remote server open a port for the data
connection and return the address of that port. The remote server listens
on that port and the client connects to it. When using the more
traditional PORT command, the client listens on a
port and sends that address to the remote server, who connects back to it.
Passive mode is useful when using ftp through a
gateway router or host that controls the directionality of traffic. (Note
that though FTP servers are required to support the
PASV command by RFC 1123,
some do not.)pdir
[remote-path]dir [remote-path],
and display the result with the program specified by the
set pager option.pls
[remote-path]ls [remote-path],
and display the result with the program specified by the
set pager option.pmlsd
[remote-path]mlsd [remote-path],
and display the result with the program specified by the
set pager option.preserveprogress-’ or a command that starts with
‘|’. Refer to
FILE NAMING CONVENTIONS
for more information. Enabling progress disables
hash.promptmget or mput will transfer
all files, and any mdelete will delete all files.
When prompting is on, the following commands are available at a prompt:
anpprompt off had been given).qy?Any other response will answer ‘yes’ to the current file.
proxy
ftp-commandproxy
command should be an open, to establish the
secondary control connection. Enter the command
‘proxy ?’ to see other FTP commands
executable on the secondary connection. The following commands behave
differently when prefaced by proxy:
open will not define new macros during the
auto-login process, close will not erase existing
macro definitions, get and
mget transfer files from the host on the primary
control connection to the host on the secondary control connection, and
put, mput, and
append transfer files from the host on the
secondary control connection to the host on the primary control
connection. Third party file transfers depend upon support of the FTP
protocol PASV command by the server on the
secondary control connection.put
local-file [remote-file]ntrans
or nmap settings in naming the remote file. File
transfer uses the current settings for type,
format, mode, and
structure.pwdquitbye.quote
[arg ...]rate
direction [maximum
[increment]]direction may be one of:
maximum can be modified on the fly by increment bytes (default: 1024) each time a given signal is received:
If maximum is not supplied, the current throttle rates are displayed.
Note: rate is not yet implemented for
ascii mode transfers.
rcvbuf
sizerecv
remote-file [local-file]get.reget
remote-file [local-file]reget
acts like get, except that if
local-file exists and is smaller than
remote-file, local-file is
presumed to be a partially transferred copy of
remote-file and the transfer is continued from the
apparent point of failure. This command is useful when transferring very
large files over networks that are prone to dropping connections.remopts
command [command-options]MLST (used for
MLSD and MLST).rename
[from [to]]resetrestart
markerget or
put at the indicated marker.
On UNIX systems, marker is usually a byte offset
into the file.rhelp
[command-name]rmdir
directory-namerstatus
[remote-file]runiqueget or mget command, a
‘.1’ is appended to the name. If the
resulting name matches another existing file, a
‘.2’ is appended to the original
name. If this process continues up to
‘.99’, an error message is printed,
and the transfer does not take place. The generated unique filename will
be reported. Note that runique will not affect
local files generated from a shell command (see below). The default value
is off.send
local-file [remote-file]put.sendportPORT commands. By default,
ftp will attempt to use a
PORT command when establishing a connection for
each data transfer. The use of PORT commands can
prevent delays when performing multiple file transfers. If the
PORT command fails, ftp
will use the default data port. When the use of
PORT commands is disabled, no attempt will be made
to use PORT commands for each data transfer. This
is useful for certain FTP implementations which do ignore
PORT commands but, incorrectly, indicate they've
been accepted.set
[option value]anonpass$FTPANONPASSftp_proxy$ftp_proxy.http_proxy$http_proxy.https_proxy$https_proxy.no_proxy$no_proxy.pager$PAGER.prompt$FTPPROMPT.rprompt$FTPRPROMPT.sslnoverify$FTPSSLNOVERIFY.site
[arg ...]SITE command.size
remote-filesndbuf
sizestatusftp.struct
struct-namefile’.suniqueSTOU
command for successful completion. The remote server will report unique
name. Default value is off.systemtenexthrottlerate.tracetype
[type-name]type to
type-name. If no type is specified, the current type
is printed. The default type is network ASCII.umask
[newmask]unset
optionset
for more information.usage
commanduser
user-name [password
[account]]ftp will prompt the user for it (after
disabling local echo). If an account field is not
specified, and the FTP server requires it, the user will be prompted for
it. If an account field is specified, an account
command will be relayed to the remote server after the login sequence is
completed if the remote server did not require it for logging in. Unless
ftp is invoked with “auto-login”
disabled, this process is done automatically on initial connection to the
FTP server.verbosexferbuf
size?
[command]help.Command arguments which have embedded spaces may be quoted with
quote ‘"’ marks.
Commands which toggle settings can take an explicit
on or off argument to force
the setting appropriately.
Commands which take a byte count as an argument (e.g.,
hash, rate, and
xferbuf) support an optional suffix on the argument
which changes the interpretation of the argument. Supported suffixes
are:
If ftp receives a
SIGINFO (see the status
argument of stty(1)) or
SIGQUIT signal whilst a transfer is in progress, the
current transfer rate statistics will be written to the standard error
output, in the same format as the standard completion message.
ftp
supports an auto-fetch feature. To enable auto-fetch, simply pass the list of
hostnames/files on the command line.
The following formats are valid syntax for an auto-fetch element:
@]host:[path][/]If path contains a glob character and
globbing is enabled, (see glob), then the
equivalent of mget path is
performed.
If the directory component of path
contains no globbing characters, it is stored locally with the name
basename (see
basename(1)) of
path, in the current directory. Otherwise, the
full remote name is used as the local name, relative to the local root
directory.
ftp://[user[:password]@]host[:port]/path[/][;type=type]set
ftp_proxy isn't defined. Otherwise, transfer the URL using HTTP via
the proxy defined in set ftp_proxy. If
set ftp_proxy isn't defined and
user is given, login as user.
In this case, use password if supplied, otherwise
prompt the user for one.
If a suffix of ‘;type=A’
or ‘;type=I’ is supplied, then the
transfer type will take place as ascii or binary (respectively). The
default transfer type is binary.
In order to be compliant with RFC
3986, ftp interprets the
path part of an
‘ftp://’ auto-fetch URL as
follows:
/’ immediately after the
host[:port]
is interpreted as a separator before the path,
and not as part of the path itself./’-separated list of name
components. For all but the last such component,
ftp performs the equivalent of a
cd command. For the last path component,
ftp performs the equivalent of a
get command.//’ within the
path, or from an extra
‘/’ at the beginning of the
path, will cause the equivalent of a
cd command without a directory name. This is
unlikely to be useful.%XX’
codes (per RFC 3986) within the path
components are decoded, with XX representing a
character code in hexadecimal. This decoding takes place after the
path has been split into components, but before
each component is used in the equivalent of a
cd or get command.
Some often-used codes are ‘%2F’
(which represents ‘/’) and
‘%7E’ (which represents
‘~’).The above interpretation has the following consequences:
%2F’. If a user's home
directory is required (and the remote server supports the syntax), use
a leading path of
‘%7Euser/’.
For example, to retrieve /etc/motd from
‘localhost’ as the user
‘myname’ with the password
‘mypass’, use
‘ftp://myname:mypass@localhost/%2fetc/motd’cd and get
commands can be controlled by careful choice of where to use
‘/’ and where to use
‘%2F’ (or
‘%2f’). For example, the
following URLs correspond to the equivalents of the indicated
commands:
cd command.http://[user[:password]@]host[:port]/pathset
http_proxy is defined, it is used as a URL to an HTTP proxy server.
If HTTP authorization is required to retrieve path,
and user (and optionally
password) is in the URL, use them for the first
attempt to authenticate.https://[user[:password]@]host[:port]/pathset
https_proxy is defined, it is used as a URL to an HTTPS proxy
server. If HTTPS authorization is required to retrieve
path, and user (and optionally
password) is in the URL, use them for the first
attempt to authenticate. There is currently no certificate validation and
verification.file:///pathabout:topicabout:ftpftp.about:versionftp. Useful to provide when
reporting problems.Unless noted otherwise above, and -o
output is not given, the file is stored in the current
directory as the basename(1)
of path. Note that if a HTTP redirect is received, the
fetch is retried using the new target URL supplied by the server, with a
corresponding new path. Using an explicit
-o output is recommended, to
avoid writing to unexpected file names.
If a classic format or an FTP URL format has a trailing
‘/’ or an empty
path component, then ftp will
connect to the site and cd to the directory given as
the path, and leave the user in interactive mode ready for further input.
This will not work if set ftp_proxy is being
used.
Direct HTTP transfers use HTTP 1.1. Proxied FTP and HTTP transfers use HTTP 1.0.
If -R is given, all auto-fetches that
don't go via the FTP or HTTP proxies will be restarted. For FTP, this is
implemented by using reget instead of
get. For HTTP, this is implemented by using the
‘Range: bytes=’ HTTP/1.1 directive.
If WWW or proxy WWW authentication is required, you will be prompted to enter a username and password to authenticate with.
When specifying IPv6 numeric addresses in a URL, you need to
surround the address in square brackets. E.g.:
‘ftp://[::1]:21/’. This is because
colons are used in IPv6 numeric address as well as being the separator for
the port number.
ABOR command to the
remote server, and discarding any further data received. The speed at which
this is accomplished depends upon the remote server's support for
ABOR processing. If the remote server does not support
the ABOR command, the prompt will not appear until the
remote server has completed sending the requested file.
If the terminal interrupt key sequence is used whilst
ftp is awaiting a reply from the remote server for
the ABOR processing, then the connection will be
closed. This is different from the traditional behaviour (which ignores the
terminal interrupt during this phase), but is considered more useful.
ftp commands are
processed according to the following rules.
-’ is specified,
the stdin (for reading) or
stdout (for writing) is used.|’, the remainder of the argument
is interpreted as a shell command. ftp then forks
a shell, using popen(3) with
the argument supplied, and reads (writes) from the stdout (stdin). If the
shell command includes spaces, the argument must be quoted; e.g.
‘"| ls -lt"’.
A particularly useful example of this mechanism is:
‘dir "" |more’.glob command. If the ftp
command expects a single local file (e.g. put),
only the first filename generated by the globbing operation is used.mget commands and get
commands with unspecified local file names, the local filename is the
remote filename, which may be altered by a case,
ntrans, or nmap setting.
The resulting filename may then be altered if
runique is on.mput commands and put
commands with unspecified remote file names, the remote filename is the
local filename, which may be altered by a ntrans
or nmap setting. The resulting filename may then
be altered by the remote server if sunique is
on.type may be one of
“ascii”, “image” (binary), “ebcdic”,
and “local byte size” (for PDP-10's and PDP-20's mostly).
ftp supports the ascii and image types of file
transfer, plus local byte size 8 for tenex mode
transfers.
ftp supports only the default values for
the remaining file transfer parameters: mode,
form, and struct.
-N
netrc option, or specified in the
NETRC environment variable. The following tokens are
recognized; they may be separated by spaces, tabs, or new-lines:
machine
namemachine token that matches the remote machine
specified on the ftp command line or as an
open command argument. Once a match is made, the
subsequent .netrc tokens are processed, stopping
when the end of file is reached or another machine
or a default token is encountered.defaultmachine
name except that default
matches any name. There can be only one default
token, and it must be after all machine tokens.
This is normally used as:
default login anonymous password
user@sitethereby giving the user an automatic anonymous FTP login to
machines not specified in .netrc. This can be
overridden by using the -n flag to disable
auto-login.
login
namepassword
stringftp will abort
the auto-login process if the .netrc is readable
by anyone besides the user.account
stringACCT command if it does not.macdef
nameftp
macdef command functions. A macro is defined with
the specified name; its contents begin with the next
.netrc line and continue until a blank line
(consecutive new-line characters) is encountered. Like the other tokens in
the .netrc file, a macdef
is applicable only to the machine definition
preceding it. A macdef entry cannot be used by
multiple machine definitions; rather, it must be
defined following each machine it is intended to
be used with. If a macro named init is defined, it
is automatically executed as the last step in the auto-login process. For
example,
default
macdef init
epsv4 off
followed by a blank line.
ftp supports interactive command line editing, via the
editline(3) library. It is
enabled with the edit command, and is enabled by
default if input is from a tty. Previous lines can be recalled and edited with
the arrow keys, and other GNU Emacs-style editing keys may be used as well.
The editline(3) library is configured with a .editrc file — refer to editrc(5) for more information.
An extra key binding is available to ftp
to provide context sensitive command and filename completion (including
remote file completion). To use this, bind a key to the
editline(3) command
ftp-complete. By default, this is bound to the TAB
key.
ftp displays a command line prompt of
‘ftp> ’ to the user. This can
be changed with the set prompt command.
A prompt can be displayed on the right side of the screen (after
the command input) with the set rprompt command.
The following formatting sequences are replaced by the given information:
%/%c[[0]n],
%.[[0]n]0’, the number of skipped
components precede the trailing component(s) in the format
“/<number>trailing”
(for ‘%c’) or
“...trailing”
(for ‘%.’).%M%m.’.%n%%%’.ftp uses the following environment variables.
FTPANONPASS`whoami`@”.FTPMODEFTPPROMPTftp> ’. Refer to
COMMAND LINE PROMPT for more
information.FTPRPROMPTFTPSERVERgate is
enabled.FTPSERVERPORTgate is enabled. Default is port returned by a
getservbyname(3)
lookup of “ftpgate/tcp”.FTPUSERAGENTFTPSSLNOVERIFYHOMENETRCPAGERSHELLftp_proxySee http_proxy for further notes about
proxy use.
http_proxyIf “unsafe” URL characters are required in the
username or password (for example
‘@’ or
‘/’), encode them with
RFC 3986
‘%XX’
encoding.
Note that the use of a username and password in
ftp_proxy and http_proxy
may be incompatible with other programs that use it (such as
lynx(1)).
NOTE: this is not used for interactive sessions, only for command-line fetches.
https_proxySee http_proxy for further notes about
proxy use.
no_proxy:port’, which
restricts the matching to connections to that port.ftp to use
extended passive mode. If you find that even a simple
ls appears to hang after printing a message such as
this:
229 Entering Extended Passive Mode
(|||58551|)then you will need to disable extended passive mode with
epsv4 off. See the above section
The .netrc File for an example of
how to make this automatic.
ftp attempts to be compliant with:
RFC
959RFC
1123RFC
1635RFC
2389RFC
2428RFC
2616RFC
2822RFC
3659RFC
3986ftp command appeared in
4.2BSD.
Various features such as command line editing, context sensitive
command and file completion, dynamic progress bar, automatic fetching of
files and URLs, modification time preservation, transfer rate throttling,
configurable command line prompt, and other enhancements over the standard
BSD ftp were implemented in
NetBSD 1.3 and later releases by
Luke Mewburn ⟨lukem@NetBSD.org⟩.
IPv6 support was added by the WIDE/KAME project (but may not be present in all non-NetBSD versions of this program, depending if the operating system supports IPv6 in a similar manner to KAME).
An error in the treatment of carriage returns in the 4.2BSD ascii-mode transfer code has been corrected. This correction may result in incorrect transfers of binary files to and from 4.2BSD servers using the ascii type. Avoid this problem by using the binary image type.
ftp assumes that all IPv4 mapped addresses
(IPv6 addresses with a form like ::ffff:10.1.1.1)
indicate IPv4 destinations which can be handled by
AF_INET sockets. However, in certain IPv6 network
configurations, this assumption is not true. In such an environment, IPv4
mapped addresses must be passed to AF_INET6 sockets
directly. For example, if your site uses a SIIT translator for IPv6-to-IPv4
translation, ftp is unable to support your
configuration.
| February 25, 2023 | NetBSD 10.0 |