From: Andy Furniss Date: Mon, 26 Apr 2004 07:47:34 +0000 Subject: Re: [LARTC] boring question Message-Id: <408CBE96.2080905@dsl.pipex.com> List-Id: References: <20040422214238.8E57A44CB@outpost.ds9a.nl> In-Reply-To: <20040422214238.8E57A44CB@outpost.ds9a.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Mr Ivan Hawkes wrote: > Andy Furniss wrote: > >> Mr Ivan Hawkes wrote: >> >>> It is important to note that this generally works well for outgoing >>> traffic but is not particularly effective against incoming traffic >>> since that is *pushed* onto your machine and it has no way to control >>> this. >> >> >> >> You can control incoming bandwidth much the same as outbound - but >> it's hard to keep latency low all of the time. >> >> Andy. >> >> > Are you able to selectively control incoming bandwidth? e.g. I have some > BT's running sucking up all that good bandwidth and my incoming pipe > gets saturated (it's 2MB, so this doesn't generally happen). How would I > tell the BT streams to slow down while giving more priority to the > important stuff? I know how to do it on egress, just not on ingress. > You can treat it a egress traffic coming from shaping box to LAN. So the marking/filtering should be no different. In the BT case, there is a project on sf.net called ipp2p which can mark it, it needs you to patch netfilter/kernel with connmark. I don't use it so can't tell you in detail. Andy. _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/