From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Multiple connections
Date: Wed, 03 Dec 2003 10:10:34 +0000 [thread overview]
Message-ID: <marc-lartc-107044799825533@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106445243827957@msgid-missing>
On Tuesday 02 December 2003 16:42, Mihai Vlad wrote:
> I hope I am not that pushy, but I cannot figure this out.
>
>
> If 2 of my clients are downloading from the internet one file each, the
> splitting works and one client gets 64kbps and the other 64kbps.
> If one of those 2 clients are downloading by means of a Download Manager
> (like Flash Get or Download Accelerator) every gets messed up.
> The one downloading with multiple connections gets 90-95% of the bandwidth
> and the other client gets almost nothing.
>
> In my opinion if I have 2 clients downloading at the same time, the sum of
> all the connections from each other would have to be 64kbbit.
> Please tell me what I have to change to make sure that the splitting works
> ok.
> I am sure for you this is a piece of cake but for me it's a nightmare :)
>
> This is the script that I use.
>
>
>
> $TC qdisc add dev $LAN_IFACE root handle 1: htb default 30
> $TC class add dev $LAN_IFACE parent 1: classid 1:1 htb rate 128kbit ceil
> 128kbit burst 80k
>
>
> #--------default---------
> $TC class add dev $LAN_IFACE parent 1:1 classid 1:30 htb rate 1kbit ceil
> 128kbit burst 80k
> $TC qdisc add dev $LAN_IFACE parent 1:30 handle 300: sfq perturb 10
>
>
>
>
> #-----clients...-------------
>
> $TC class add dev $LAN_IFACE parent 1:1 classid 1:11 htb rate 8kbit ceil
> 128kbit burst 80k
> $FILTER_IP 192.168.0.121 flowid 1:11
> $TC qdisc add dev $LAN_IFACE parent 1:11 handle 110: sfq perturb 10
>
> $TC class add dev $LAN_IFACE parent 1:1 classid 1:13 htb rate 8kbit ceil
> 96kbit burst 80k
> $FILTER_IP 192.168.0.123 flowid 1:13
> $TC qdisc add dev $LAN_IFACE parent 1:13 handle 130: sfq perturb 10
I don't know if it's the cause if your problems, but burst 80k is too high and
your rate is too low. Burst is made for small burst of a few k, not 80k.
And htb needs a minimal burst before htb can work properly.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-03 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 1:19 [LARTC] Multiple connections carlosh
2003-12-01 8:15 ` Mihai Vlad
2003-12-01 12:03 ` Chijioke Kalu
2003-12-01 13:51 ` Jon Zeeff
2003-12-02 8:54 ` rio
2003-12-02 9:29 ` raptor
2003-12-02 15:42 ` Mihai Vlad
2003-12-03 10:10 ` Stef Coene [this message]
2004-06-10 19:35 ` [LARTC] multiple connections David Magda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-107044799825533@msgid-missing \
--to=stef.coene@docum.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.