lartc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Claudio Neves" <nevalabs@yahoo.com.br>
To: lartc@vger.kernel.org
Subject: [LARTC] Ingress qdisc problems
Date: Fri, 21 Dec 2001 19:49:47 +0000	[thread overview]
Message-ID: <marc-lartc-100896423614946@msgid-missing> (raw)

Hello,

I tried ingress qdisc with kernel 2.4.16, and it works very
well.
But when I tried it with kernel 2.2.20, with diffserv-8
patches applied (and latest HTB too), it doesn't work. It
seems that the filter don't classify the packets to the
ingress queue.

Here follows the simplest setup I tried:

#!/bin/bash

tc qdisc del dev eth0 root 2> /dev/null > /dev/null
tc qdisc del dev eth0 ingress 2> /dev/null > /dev/null

tc qdisc add dev eth0 handle ffff: ingress

tc filter add dev eth0 parent ffff: protocol ip prio 0 u32
match ip src \
   0.0.0.0/0 police rate 1000kbit burst 90k mtu 1500 drop
flowid :1


This doesn't seems to limit any traffic, nor the traffic
goes to the ingress qdisc.

root@gw ~# tc -s qdisc
qdisc ingress ffff: dev eth0 ----------------
 Sent 0 bytes 0 pkts (dropped 0, overlimits 0)


Do you have any clues on what I am doing wrong ?!
I'm using iproute2 001007.

Thanks for your attention,

Claudio Neves


_______________________________________________________________________________________________
Yahoo! GeoCities
Tenha seu lugar na Web. Construa hoje mesmo sua home page no Yahoo! GeoCities. É fácil e grátis!
http://br.geocities.yahoo.com/

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

             reply	other threads:[~2001-12-21 19:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-21 19:49 Claudio Neves [this message]
2001-12-21 23:18 ` [LARTC] Ingress qdisc problems bert hubert
2001-12-22  2:38 ` Claudio Neves

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-100896423614946@msgid-missing \
    --to=nevalabs@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).