passive-ip NcFTPd file configuration
Don't forget to restart NcFTPd after modifying the file.

This rarely-used option may be needed for sites that want to support passive-mode FTP with a load-balancing router, such as:

These solutions serve as a front-end to multiple back-end server machines, redirecting traffic transparently to server nodes. This lets you expose a single external IP address, but have multiple machines service that address.

For the Cisco product, NcFTPd needs to be configured so that for passive FTP data connections, that the address the client is instructed to connect to is the IP address of the front-end server instead of the back-end server node (which NcFTPd would be running on).  (The Cisco Local Director also needs to be configured to use "sticky" mode, so that TCP/IP connections from the same client IP address go to the same back-end server.)

Note that NcFTPd has only been tested using the Cisco product.  If you plan on using NcFTPd in such a configuration, you should do extensive testing to be sure the device is configured properly.  You should especially test with FTP clients that use passive mode FTP, such as Netscape Communicator or Internet Explorer 4.


Previous: noop-delay NcFTPd Home Next: pid-file