From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] unexpected drop
Date: Sun, 08 Jan 2006 21:20:08 +0000 [thread overview]
Message-ID: <43C18208.3070209@dsl.pipex.com> (raw)
In-Reply-To: <000801c6141c$31ad2b30$0100000a@casa>
Roberto Belletti wrote:
> Hello everybody,
>
> I have a Linux router with an ethernet adapter and a ADSL device.
> My router has a GRE tunnel connected to a remote IP address.
>
> Using "tc" I have configured 3 different classes:
> 1. 290kbit rate (used for Voip Services)
> 2. 180kbit rate (used for GRE tunnel)
> 3. 80kbit rate (for generic data traffic)
>
> For each class, using "iperf", I send some data from a PC (connected attraverso eth0 device)
> to a remote destination. The remote destination is the GRE tunnel terminator.
>
> The data traffic test is different for each class:
> 1. 240kbit, 60byte packet size, UDP protocol
> 2. 200kbit, 250byte packet size, UDP protocol
> 3. 80kbit, 235byte packet size, UDP protocol
>
> In this way I got a lot of dropped packets on each class, while my expected results was
> a many drop packages only on the second class.
iperf may be using data rates htb uses ip level packet sizes (I guess on
atm0 - it's ip len +14 on eth).
I don't know cbq but notice the rates don't add up.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-08 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 6:24 [LARTC] unexpected drop Roberto Belletti
2006-01-08 21:20 ` Andy Furniss [this message]
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=43C18208.3070209@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.