On Tue, May 04, 2004 at 08:36:04PM -0600, Rodolfo J. Paiz wrote: > 1. Required: Limit the total bandwidth a client can use to either > 128 Kbps or 256 Kbps. http://www.knowplace.org/shaper I haven't used it but a quick Google search found it for me. > > 2. Optional: Allow each client to exceed their limit if no one > else is using the space. I think that's covered in the shaper stuff above. I only read 2 minutes of the web site page though. > 4. Optional: Provide each tenant with an FTP-served directory on > the server which can *only* be accessed from their network. So if they pull > down the confidential something or their wife's nude pictures, other > tenants cannot get at that information. This can be done with ProFTP and wu-ftpd I think. Other servers might be able to do it now with xinetd - you can have different configuration files for different interfaces. man xinetd.conf. I haven't tried this yet either. Even easier would be to just chroot each user though. Since they're on dedicated networks, they won't be able to physically sniff the packets anyway, so chroot'ing the users will give you the separation that you need. Let Linux security help you here. wu-ftpd has lots of restriction options but ProFTPd is probably a better choice these days. vsftpd is a fairly weak server. I manage a server with 1100 authenticated users on it with wu-ftpd - over 400 are chroot'ed. Even files that are world readable can not be transferred unless they're in the authorized directory tree. -- Ed Wilts, Mounds View, MN, USA mailto:ewilts@xxxxxxxxxx Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
