View Single Post
Old 20th July 2005, 13:16
till till is offline
Super Moderator
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 37,015
Thanks: 840
Thanked 5,652 Times in 4,461 Posts
Default Problem solved

The ProFTPD on SuSe needed the following additional directive
in the proftpd.conf cofiguration file:

SocketBindTight on

to start correctly with an virtual IP configuration.
We added this to the Tutorial on Howtoforge too.

Explanation from the proFTPD vHosting Howto:

There is one last configuration directive about which an administrator should know: SocketBindTight. By default, the proftpd daemon will listen on all addresses, port 21, for the connection requests of remote clients. Sometimes, the administrator may wish to have the proftpd daemon listen only on the IP addresses for which it has been configured, and not every address. To accomplish this, simply use the SocketBindTight configuration directive:

SocketBindTight on

This configures the daemon to "bind tightly" only to those IP addresses to which it has been configured to listen, rather than every address. By default, the proftpd daemon will listen to every address on the host machine.

Intersting thing: On e.g Debian or Mandrake this directive is not nescessary,
maybe its related to the newer ProFTPD version.


Last edited by till; 20th July 2005 at 13:18.
Reply With Quote