WU-FTPD 2.6.1 Release Notes (5900-2465, September 2012)

However, if you specify tcp instead of tcp6, FTP operates in the IPv4 mode.
Following are the features that support IPv6:
• Implementation of RFC 2428 (FTP Extensions for IPv6 and NATs)
This RFC specifies a method by which FTP clients and server exchange data connection
information, such as port, host address, and type of protocol family, for both IPv4 and IPv6
addresses.
FTP uses EPRT and EPSV instead of PORT and PASV, respectively, for IPv6 connections.
◦ EPRT - Extended Port
This command specifies a host port for both IPv4 and IPv6 connections.
Example 10 ERPT Command Output for IPv6 and IPv6 Connections
The following displays the output for the EPRT command for both IPv6 and IPv6
connections.
For IPv4:
------> EPRT 1 132.235.1.2 50934
For IPv6:
------> EPRT 2 fe80::260:b0ff:fec1:7b2f 50934
◦ EPSV - Extended Passive
This command requests a server to listen on a data port and wait for a connection. The
response to this command includes only the TCP port number of the listening connection.
Example 11 EPASV Command Output
An example for the EPASV command is as follows:
ftp> passive
Passive mode on.
------> EPSV
229 Entering Extended Passive Mode ( 9495 ).
• Implementation of RFC 1639 (FTP Operation Over Big Address Records (FOOBAR))
This RFC describes a convention for specifying an address other than the default data port for
the connection over which data is transferred.
The commands to accommodate FTP operations over network and transport protocols are
specified as follows:
◦ LPRT
This command enables you to specify a long address for the transport connection.
Example 12 LPRT Command Output
The following displays the output for the LPRT command:
------> LPRT6,16,254,128,0,0,0,0,0,0,2,96,176,255,254,193,123,47, 2,198,244200 LPRT command successful
◦ LPSV
This command requests a server to listen on a data port other than its default port and to
wait for a connection rather than initiate one on the receipt of a transfer command.
WU-FTPD 2.6.1 features 29