All of lore.kernel.org
 help / color / mirror / Atom feed
From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter problem
Date: Fri, 17 Feb 2006 02:35:42 +0000	[thread overview]
Message-ID: <43F5367E.AEF6EB96@iswest.com> (raw)
In-Reply-To: <1140115731.43f4c913386c7@webmail.paonia.com>

jeremy@ossnetworks.org wrote:
> 
> Hi,
> 
> I'm using a linux 2.4.29 kernel and having trouble getting my filters added. The
> script I'm editing I actually use on a different system currently. Is this a
> tc/iproute/kernel type incompatibility? Any ideas how to debug it?
> 
> Thanks, Jeremy
> 
> # create a qdisc on T1 interface
> tc qdisc add dev w1g1 root handle 1: htb default 77
> OK
> 
> # create a master class
> tc class add dev w1g1 parent 1: classid 1:1 htb rate 1400kbit
> OK
> 
> # create a leaf class
> tc class add dev w1g1 parent 1:1 classid 1:10 htb rate 175kbit \
>      ceil 1400kbit prio 0
> OK
> 
> # create a SFQ qdisc within our subclass
> tc qdisc add dev w1g1 parent 1:10 handle 10: sfq perturb 10
> OK
> 
> # filter traffic on iptables mark 10
> tc filter add dev w1g1 parent 1:0 prio 0 protocol ip handle 10 fw flowid 1:10
> Error: RTNETLINK answers: Invalid argument

I just ran that script on a 2.4.32 kernel and it does not error.  Be
sure to destruct before running:
tc qdisc del dev w1g1 root

I doubt that the above is everything in your script.  Because there is a
problem with prio 49152 (tc -s filter show dev w1g1), my hunch is that
you will find that "prio 0" is the problem.  Try E.G. "prio 9" for all
your filter lines.

(Rhetorical: What device is w1g1?)
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2006-02-17  2:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 18:48 [LARTC] tc filter problem jeremy
2006-02-17  2:35 ` gypsy [this message]
2006-02-17  4:34 ` jeremy

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=43F5367E.AEF6EB96@iswest.com \
    --to=gypsy@iswest.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.