HP-UX Remote Access Services Administrator's Guide

connection. When a control connection matching the cidr (classless inter-domain
routing) requests a passive data connection (PASV), the externalip address is
reported.
The syntax for controlling the reported address is as follows:
passive address <externalip> <cidr>
passive ports <cidr> <min> <max>
Example 2-1 The passive Clause
The following are some examples for the passive clause:
passive address 10.0.1.15 10.0.0.0/8
In this example, clients connecting from the class A network - 10 are informed 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 a control connection from the class A network - 10 exits, the port
range within 90 and 100 is randomly selected for the daemon to listen to.
NOTE: You cannot control the reported address in an IPv6 environment.
PORT and PASV Data Connection
This feature enables the site administrator 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. You
can specify multiple passive addresses to handle complex or multi-gateway networks.
The syntax for selectively allowing PORT and PASV data connections is as follows:
pasv-allow <class> [ addrglob ...]
port-allow <class> [ addrglob ...]
NOTE: You cannot selectively allow PORT and PASV data connections in an IPv6
environment.
The keepalive Clause
The keepalive clause allows you to control network disconnect by setting the TCP
SO_ALIVE option for data sockets. You can specify yes to set the TCP option, or no
to use the system default settings, which is usually off. HP recommends that you set
the keepalive clause to yes to retain the network traffic connected.
Additional Clauses in ftpaccess 49