From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Transfer rate above the desired (tc+htb)
Date: Wed, 20 Jul 2005 21:11:36 +0000 [thread overview]
Message-ID: <42DEBE08.8090004@dsl.pipex.com> (raw)
In-Reply-To: <3941d81c0507201042563b5e45@mail.gmail.com>
Alvaro Motta wrote:
> Hi Andy, thanks for your reply.
>
> I don't see why the src should be the culprit, since the AB segment is
> 10.4 network and the BC is 192.168. And IMHO 0.0.0.0/0
>
> Also, after modifying the src, the traffic rate was the same as if no
> qdisc were attached to the interface. I even played with the
> interfaces and the only way to throttle the traffic, is assigning the
> qdisc to the eth0 and having the src and dst as in the script I've
Hmm I am confused now :-)
If you run wget on machine A with address 10.4.x.y and request a file
from machine C address 192.168.0.23 then the source address of the
packets passing egress eth0 on machine B should be 192.168.0.23 - unless
there is some sort of NAT going on in machine B.
FWIW you use default 50 on your htb rule but don't have a class 1:50 and
your filter rule dst 0.0.0.0/0 matches any dst ipaddress and so is
redundant.
Maybe you should as a test limit all IP traffic on eth0 and see if that
works -
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 1: htb
tc class add dev eth0 parent 1: classid 1:1 htb rate 32kbit ceil 32kbit
tc filter add dev eth0 protocol ip parent 1:0 prio 100 u32 match u32 0 0
classid 1:1
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-07-20 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 17:42 [LARTC] Transfer rate above the desired (tc+htb) Alvaro Motta
2005-07-20 18:56 ` Andy Furniss
2005-07-20 20:11 ` Alvaro Motta
2005-07-20 21:11 ` Andy Furniss [this message]
2005-07-20 23:14 ` Francisco Pereira
2005-07-24 18:06 ` gypsy
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=42DEBE08.8090004@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.