All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hasenack <ahasenack@terra.com.br>
To: lartc@vger.kernel.org
Subject: [LARTC] mysterious rebounce in htb
Date: Wed, 22 Feb 2006 16:35:47 +0000	[thread overview]
Message-ID: <20060222163546.GG3443@mandriva.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]

Attached is a graph obtained with ethereal where after time +/-45s there is
a rebounce which I can't explain.

Setup is this:
- my machine starts to generate traffic at maximum speed against a
  target machine (using nc < /dev/zero here and nc -l > /dev/null there)
- traffic pattern is:
   0s: dst port 2500 (red)
  20s: dst port 8000 (blue)
  40s: kill port 2500 traffic
  60s: kill port 8000 traffic
- htb is limiting that traffic to 100mbps at all times (see below for
  htb configuration)

Could that bounce be a result of some wrong configuration I have? Or
some other traffic interfering with my measurements? I used a "host
10.0.16.10" filter in ethereal, and since the bounce is "compensated" in
the other traffic I don't think it was some external interference, but
who knows.6

htb config is created by this script. Note I created two root classes so
that my regular work on this desktop doesn't interfere with the
measurements and tests I'm performing (or so I hope):

#!/bin/bash
DEV=eth0
WWWPORT=8000
SMTPPORT=2500
MAPI=10.0.16.10
tc qdisc del dev $DEV root > /dev/null 2>&1

# root qdisc
tc qdisc add dev $DEV handle 1: root htb default 2

# root classes
tc class add dev $DEV classid 1:1 parent 1: htb rate 100kbps
tc class add dev $DEV classid 1:2 parent 1: htb rate 90mbit
tc qdisc add dev $DEV handle 2: parent 1:2 sfq perturb 10

# a/www
tc class add dev $DEV classid 1:10 parent 1:1 htb rate 30kbps ceil 100kbps prio 0
tc qdisc add dev $DEV handle 10: parent 1:10 sfq perturb 10

# a/smtp
tc class add dev $DEV classid 1:11 parent 1:1 htb rate 10kbps ceil 100kbps prio 0
tc qdisc add dev $DEV handle 20: parent 1:11 sfq perturb 10

# b
tc class add dev $DEV classid 1:12 parent 1:1 htb rate 60kbps ceil 100kbps
tc qdisc add dev $DEV handle 30: parent 1:12 sfq perturb 10

# qualquer coisa indo para a mapi8 cai na classe 1:1
tc filter add dev $DEV parent 1:0 prio 10 protocol ip u32 \
	match ip dst $MAPI/32 \
	flowid 1:1

# on 1:1: a/www -> 1:10
tc filter add dev $DEV parent 1:1 prio 5 protocol ip u32 \
	match ip dst $MAPI/32 \
	match ip protocol 0x06 0xff \
	match ip dport $WWWPORT 0xffff \
	flowid 1:10

# on 1:1: a/smtp -> 1:11
tc filter add dev $DEV parent 1:1 prio 5 protocol ip u32 \
	match ip dst $MAPI/32 \
	match ip protocol 0x06 0xff \
	match ip dport $SMTPPORT 0xffff \
	flowid 1:11

# on 1:1: b (telnet, for example) -> 1:12
tc filter add dev $DEV parent 1:1 prio 5 protocol ip u32 \
	match ip dst $MAPI/32 \
	match ip protocol 0x06 0xff \
	match ip dport 23 0xffff \
	flowid 1:12



[-- Attachment #2: rebounce-ann.png --]
[-- Type: image/png, Size: 6311 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2006-02-22 16:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060222163546.GG3443@mandriva.com \
    --to=ahasenack@terra.com.br \
    --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.