It's not quite as clean as the socket binding under Apache but the principle works something like this.
- In Standalone mode, to listen on the primary IP of a host use the SocketBindTight directive.
In "/etc/proftpd.conf":
SocketBindTight on
- To listen on a interfaces which are not the primary host interface, use the SocketBindTight directive, place your server configuration in a
block and use "Port 0" for the main host configuration and and "Port 21" inside the VirtualHost block. Port &n
bsp; &n bsp; &n bsp; &n bsp; &n bsp; 0
SocketBindTight & nbsp; & nbsp; on
<VirtualHost xxx.xxx.xxx.xxx>
Port 21
DefaultRoot & nbsp; & nbsp; ~
AllowOverwrite &nbs p; &nbs p; on
Umask & nbsp; & nbsp; & nbsp; 002
</VirtualHost>
- sandip's blog
- Login or register to post comments
Comments
We have spent days of drinking and thinking what could be the reason of our FTP not working on the alias'ed IP address.
Setting default port to 0 fixed the issue!
Thanks to the author of this VERY nice tutorial!
Helped me a lot..
When changed from port 21 to 2100 (for security) the server decided to shout on the logs:
unable to listen on 0.0.0.0#21: Address already in use
The parameter fixed the issue :-)