Norberto Bensa wrote:
Ah!! But Windows (XP) uses TC by default. It doesn't use 20% of the
network bandwidth unless you tweak some registry setting and/or
disable QoS in network properties.
That sounds like a fine plan for me... but, erm, how does it know? Both
Linux and Xp talk to my router at 100mbps - and my router talks to the
outside world at 0.5mbps... so, while I'd be entirely happy to cap both
machines at 80mbps, I don't see why this would have any effect on the
competition for the 0.5mbps to the outside world.
What's more to the point, it doesn't seem to be Linux competing with Xp,
per se - but rather Linux competing with Linux - since my LAN works
great - and I can communicate at will between Xp and Linux - it is only
when Linux's bind competes with Linux's wget that I see a problem. This
is with two processes on the same PC.
Why? Is pretty obvious what's happening: your Linux box is eating all
the bandwidth with the MB download because _by_default_ Linux doesn't
do any TC at all. If the iptables thingy was too aggressive, try a
--limit-rate (or --rate-limit; I can't never get it right) in wget.
I presume this is what you mean (taken from "man iptables"):
--limit rate
Maximum average matching rate: specified as a number,
with an
optional `/second', `/minute', `/hour', or `/day'
suffix; the
default is 3/hour.
This looks as if I can limit the rate at which my linux box talks on my
LAN - but this isn't what I need to do. Interestingly, long downloads
from two competing WinXp boxes don't cause a problem - but both will
max-out my available download capacity... suggesting to me that fixed
rate-limiting is not what is called for...
