All of lore.kernel.org
 help / color / mirror / Atom feed
From: Flemming Frandsen <ff@nrvissing.net>
To: lartc@vger.kernel.org
Subject: [LARTC] tc filter add ... fw returns RTNETLINK answers: Invalid
Date: Tue, 10 Jan 2006 21:40:53 +0000	[thread overview]
Message-ID: <43C429E5.3070007@nrvissing.net> (raw)

When I run this:
tc filter add dev eth0 parent 1: protocol ip prio 1 handle 1 fw

I get:
RTNETLINK answers: Invalid argument

The traditional interpretation of that gnarly error message is that 
cls_fw is missing, but lsmod | grep cls_fw gets me:
cls_fw                  2336   4  (autoclean)

I can't remove it because it's in use, but all 4 statements that use it 
failed, so I'm really stumped.


This is what happens in begining of the traffic shaper script:

+ tc qdisc del dev eth0 root
+ tc qdisc add dev eth0 root handle 1: htb default 0x42
+ tc class add dev eth0 parent 1: classid 1:1 htb rate 700kbit burst 6k
+ tc class add dev eth0 parent 1:1 classid 1:42 htb rate 600kbit burst 
15k prio 0
+ tc qdisc add dev eth0 parent 1:42 handle 42: sfq perturb 20
+ tc filter add dev eth0 parent 1: protocol ip prio 1 handle 1 fw
RTNETLINK answers: Invalid argument
+ iptables -t mangle -N to-dsl

Any clues?

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

             reply	other threads:[~2006-01-10 21:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 21:40 Flemming Frandsen [this message]
2006-01-10 22:21 ` [LARTC] tc filter add ... fw returns RTNETLINK answers: Invalid Muthukumar S
2006-01-10 23:19 ` Flemming Frandsen
2006-01-11  0:51 ` Andy Furniss
2006-01-11  0:52 ` Andy Furniss
2006-01-11 11:55 ` [LARTC] tc filter add ... fw returns RTNETLINK answers: Flemming Frandsen
2006-01-12  0:23 ` Andy Furniss
2006-01-13 21:45 ` Flemming Frandsen
2006-01-13 23:04 ` Jody Shumaker

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=43C429E5.3070007@nrvissing.net \
    --to=ff@nrvissing.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.