From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Help needed with HTB
Date: Tue, 03 Apr 2007 19:44:37 +0000 [thread overview]
Message-ID: <4612AEA5.2090701@andyfurniss.entadsl.com> (raw)
Edgar Merino wrote:
> Hello, a few days ago I sent an email asking for help with my tc htb
> rules I've got (a script), but I'm not sure if that email got to you...
> anyway, I'm sending it again along with my htb script and I'll tell you
> the problem once again:
>
> I have a computer with ip 192.168.0.100 which is acting as a p2p server,
> so I want to shape traffic coming out from that ip, I have a linux box
> acting as a router with two NICs, server ip is 192.168.0.1. So I hope
> you can take a look at it and tell me why is it that everytime I have
> mldonkey or any other p2p software running on that computer I experience
> a lot of latency in my whole network with http traffic, maybe someone
> can help me out specify the burst and cburst parameters... and maybe
> even the quantum parameter, and some little explanation on it since I
> haven't been able to understand what the benefits of this parameters are.
The rates on htb child classes should not add up to any more that about
80% of the link speed. The parent rate and ceils should be equal to
about 80% of link speed. I guess you already know for tc bps =
bytes/sec. Read some of my recent posts about htb default on eth.
Check with iptables -L -v -n that the rules are matching as you expect -
without testing I can't recall if the output one will see addresses.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2007-04-03 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 19:44 Andy Furniss [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-06 23:03 [LARTC] Help needed with HTB Edgar Merino
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=4612AEA5.2090701@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.com \
--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.