Does Rumpus support multi-homing?
The issue of “multi-homing” is very different when discussing FTP vs. HTTP (Web). The point of multi-homing is to ensure that each client be given access to the correct content (usually a folder) based on the host (Web site) they are accessing. For Web servers, this means figuring out which of multiple Web sites is being requested and serving the page from the correct folder. But when connecting via FTP, users typically log in using a user account name and password. This means that the FTP server can use the user account information (in Rumpus, the user’s home folder) to determine what folder the user should be given access to, rather than relying on the IP address or host the user originally requested. In other words, Rumpus supports listening for incoming connections on multiple IP addresses assigned to the same server, and will correctly serve user content from home folders defined for each user account. So, for practical purposes, Rumpus does support multi-homing, with a couple of
