All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abraham van der Merwe <abz@frogfoot.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc { class | filter } does not work
Date: Sat, 16 Nov 2002 17:57:53 +0000	[thread overview]
Message-ID: <marc-lartc-103746993912730@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103746119806662@msgid-missing>

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

Hi Stef!

> > I'm trying to use tc on linux 2.4.20-rc1aa with iproute 20010824-8 (latest
> > debian package), but I'm having no joy.
> The latest version is iproute2-2.4.7-now-ss020116.  I recommend using it.
> 
> > I've attached my kernel config in case you want to check whether I
> > configured the correct stuff (but I pretty much enabled everything - the
> > only odd thing is that I couldn't configure CONFIG_RTNETLINK and
> > CONFIG_NETLINK into the kernel since those options are not available
> > anymore (selected by default nowadays?))
> From your attached config :
> # CONFIG_NETLINK_DEV is not set
> I suggest enabling it and try again.

Ok, I tried a kernel with CONFIG_NETLINK_DEV compiled in and the tc from
iproute2-2.4.7-now-ss020116-try.tar.gz but I still can't see any entries in
the class or filter list. After adding these rules:

------------< snip <------< snip <------< snip <------------
tc qdisc add dev eth0 root handle 1: cbq bandwidth 10Mbit cell 8 avpkt 1000 \
mpu 64

tc class add dev eth0 parent 1:0 classid 1:1 cbq bandwidth 10Mbit rate 10Mbit \
allot 1514 cell 8 weight 1Mbit prio 8 maxburst 20 avpkt 1000

tc class add dev eth0 parent 1:1 classid 1:2 cbq bandwidth 10Mbit rate 3Mbit \
allot 1514 cell 8 weight 100Kbit prio 3 maxburst 20 avpkt 1000 split 1:0

tc class add dev eth0 parent 1:1 classid 1:3 cbq bandwidth 10Mbit rate 8Mbit \
allot 1514 cell 8 weight 800Kbit prio 7 maxburst 20 avpkt 1000 split 1:0

tc filter add dev eth0 parent 1:0 protocol ip prio 100 route
------------< snip <------< snip <------< snip <------------

I get:

------------< snip <------< snip <------< snip <------------
root@rana:~# tc filter show
root@rana:~# tc class show
root@rana:~# tc qdisc show
qdisc cbq 1: dev eth0 rate 10Mbit (bounded,isolated) prio no-transmit
root@rana:~#
------------< snip <------< snip <------< snip <------------

As you can see the qdisc is added, but the class and filter entries don't
seem to work.

If I type the same filter rule multiple times, it allows it so I don't think
it is added at all. The class entries seem to be added because I get EEXIST
if I add the same rule multiple times, but it does not show up in ``tc class
show'' - any ideas?

-- 

Regards
 Abraham

Beware of the Turing Tar-pit in which everything is possible but nothing of 
interest is easy.

___________________________________________________
 Abraham vd Merwe [ZR1BBQ] - Frogfoot Networks
 P.O. Box 3472, Matieland, Stellenbosch, 7602
 Cell: +27 82 565 4451 Http: http://www.frogfoot.net
 Email: abz@frogfoot.net


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-11-16 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-16 15:38 [LARTC] tc { class | filter } does not work Abraham van der Merwe
2002-11-16 15:58 ` Stef Coene
2002-11-16 17:57 ` Abraham van der Merwe [this message]
2002-11-16 19:52 ` Stef Coene

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-103746993912730@msgid-missing \
    --to=abz@frogfoot.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.