Re: mldonkey & traffic shaping -> WWW still slow
From: prg (rdgentry1_at_cablelynx.com)
Date: 10 Feb 2005 09:31:04 -0800
Benjamin Fraenkel wrote:
> Im having an ADSL connection (512/128kbps). When I start mldonkey
> webbrowsing is practically impossible, though no dl/ul occurs in
> mldonkey just usual seeking for sources, connecting to servers. But
> start a download (ftp/http) I still get maximumum download bw. So I
> thought it must be an upload problem and configured a router with
> traffic shaping.
> TCng script: http://www.fraenkel.at/bandwidth.tcng
> Of course I changed the gateways/dflt routes of all clients in the
> network to use the traffic shaping router and mldonkey traffic is now
> routed through the class 'download' with a max. of 8kbps - verified
> through analyzing network traffic and tc stats and the other classes
> working either.
> But webbrowsing is still that slow, until I shutdown mldonkey again.
> Here's the topology of my network:
> Because the Traffic shaping router and the router to the uplink are
> the same subnet traffic flows like that:
> Outgoing: Client --> Traffic Shaping Router ---> Router ---> Internet
> Incoming: Internet ---> Router ---> Client
> /*effectively not using the Traffic shaping router, but that's fine
> because I just want to limit upload bw*/
> I think it's not Linux specific but I have no idea what to do next,
> proposals desired!
Well, SFQ is not very insistent -- assumes everyone is playing "fair"
in order to get the F queueing.
Unfortunately, some clever software (e.g. Kazaa and eMule among others)
obliterate the benefit of this attempt at fair queuing by opening as
many TCP sessions (flows) as can be sustained.
These hummers are difficult to control. For what you're trying to
accomplish, you might want to look at this:
The key to its working is the use of the UID of mldonkey so that the
dynamically allocated flows can be marked/identified for control
purposes. This also means that it only works on the machine running
mldonkey as the fwmarks are strictly "machine local".
Don't use any of the p2p apps so haven't any direct experience. The
above approach looks promising from my read-through. Just squashing
them whem found at work.
Someone around here likely has more experience and perhaps a ready-made
solution or specific guidance dealing with mldonkey in a setup like
yours. The problem is identifying/distinquishing all the p2p ports
With your network setup, it is _imperative_ that all machines/nics be
operating at top speed/full duplex (100 Mbps probably). The full
duplex is most important.
email above disabled