Internet Services Delta Manual for HP-UX 11i Version 1.6

• Control of the address reported:
This feature allows control of the address reported in response to a PASV command and the
TCP port numbers, which may be used for a passive data connection.
The general syntax for this is:
passive address <externalip> <cidr>
passive ports <cidr> <min> <max>
Example 2
passive address 10.0.1.15
10.0.0.0/8
In this example, clients connecting from the class-A network 10 will be notified that the passive
connection is listening on the IP-address 10.0.1.15
passive ports 10.0.0.0/8
90 100
In this example, if there is a control connection from the class-A network 10, the port range
within 90 and 100 will be randomly selected for the daemon to listen on.
• Selectively allow PORT and PASV data connections:
This feature enables the site admin to selectively allow PORT and PASV data connections.
Usually a connection is not established if the remote IP address of the data connection does
not match the remote IP address of the control connection data. Multiple passive addresses
may be specified to handle complex, or multi-gatewayed, networks.
The general syntax for this is:
pasv-allow <class> [ addrglob ...]
port-allow <class> [ addrglob ...]
• SO_KEEPALIVE:
This feature sets the TCP option SO_KEEPALIVE for data sockets. This can be used to control
network disconnect. You could specify "Yes" to set this option or "No" to use the system
default, which is usually off.
The general syntax for this is:
keepalive yes|no
• ftpaccess log:
The feature ftpaccess log clause has been changed to allow logging transfers to both the
syslog and xferlog. This option enables you to redirect the logging messages for incoming
and outgoing transfers to syslog. If this option has not been specified, the messages are written
to xferlog.
The general syntax for this is:
log syslog
log syslog+xferlog
• Clauses to control access to areas on the FTP site:
The following clauses control whether a real or guest user is allowed access to areas on the
FTP site outside their home directories. These clauses are not meant to replace the use of
guestgroup and guestuser. Instead, you can use these clauses to supplement the operation of
guests. The unrestricted-uid and unrestricted-gid clauses may be used to allow users to use
their home directories who would otherwise be restricted.
The general syntax for this is:
Chapter Overview 21