For me traffic management means to ensure that some really important sites always have enough bandwith and therefore first limiting bandwith for mail, ftp and so on.Second point is to make sure that even if there is a DoS-attack are something like this that uses all available bandwith that i can make sure to have a usabel SSH-Connection to the hosts (or in general: make sure that there is IN EVERY SITUATION enough bandwith for the netmanagement). ------------------------------------------------ BS Web Services Roedingsmarkt 14 20459 Hamburg Germany info@bsmail.de www.bsws.de fon: +49 40 3750357-0 fax: +49 40 3750357-5 PLEASE USE EMAIL WHERE POSSIBLE Mark Lastdrager To: henning.brauer@bsmail.de <mark@pine.nl cc: > Subject: Re: IP assignment for virtual webhosting 11.05.00 13:41 At Thu, 11 May 2000, henning.brauer@bsmail.de wrote:

Yes, that exactly the way we do it. If I imagine the power needed to implement this its nearly impossible to reimpleent for ONLY name-based Virtual Hosts. And if you think of Bandwith management - i don't see any way to do this on an per name-basis, only per ip (and service) is possible as far as I know. To use Bandwidth mangement on named vhosts-basis, you would have to read out the FULL ip-header and service-specific headers on the router...i think this is not possible without enormous CPU-power and would give high delays on the router.

There is something called 'mod_throttle' (if a remember well) for Apache, but I don't think customers are very interested in paying a flat fee for a virthost instead of being fast all the time and paying per MB. Mark Lastdrager Pine Internet -- email: mark@lastdrager.nl :: ML1400-RIPE :: tel. +31-70-3111010 http://www.pine.nl :: RIPE RegID nl.pine :: fax. +31-70-3111011 PGP key ID 92BB81D1 :: Dutch security news @ http://security.nl Today's excuse: quatnum decoherence