All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai RUSU <dizzy@roedu.net>
To: lartc@vger.kernel.org
Subject: [LARTC] HTB & police filters
Date: Wed, 10 Apr 2002 14:22:21 +0000	[thread overview]
Message-ID: <marc-lartc-101844815211471@msgid-missing> (raw)

Hi

Im playing with HTB and police filters. It seems that the drop action
doesnt work with htb (I think it sends the traffic to the "default"
configured class).

#!/bin/bash

tc=/sbin/tc

$tc qdisc del dev eth0 root
$tc qdisc add dev eth0 root handle 1: htb default 20

$tc class add dev eth0 parent 1: classid 1:1 htb rate 100Mbit burst 15k

$tc class add dev eth0 parent 1:1 classid 1:10 htb rate 128Kbit burst 15k
$tc class add dev eth0 parent 1:1 classid 1:20 htb rate 256Kbit ceil 100Mbit burst 15k

$tc class add dev eth0 parent 1:10 classid 1:100 htb rate 64Kbit burst 15k
$tc class add dev eth0 parent 1:10 classid 1:200 htb rate 128Kbit burst 15k

$tc filter add dev eth0 protocol ip parent 1: pref 5 u32 match ip dst \
1.2.3.4 flowid 1:200 police drop rate 64Kbit burst 15k

It seems that the filter matches the defined rate and calls enqueue() for
class 1:200, but after that the overlimit traffic it sends to the
"default" 1:20 defined htb class. If I want this I could use "continue"
but NOT drop. Is this a bug? :)

----------------------------
Mihai RUSU

Disclaimer: Any views or opinions presented within this e-mail are solely
those of the author and do not necessarily represent those of any company,
unless otherwise specifically stated.


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-04-10 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-10 14:22 Mihai RUSU [this message]
2002-04-10 17:45 ` [LARTC] HTB & police filters Martin Devera

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-101844815211471@msgid-missing \
    --to=dizzy@roedu.net \
    --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.