Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Gavin Hamill <gdh@acentral.co.uk>
To: lartc@vger.kernel.org
Subject: [LARTC] Ingress with WonderShaper
Date: Sun, 04 Jan 2004 18:49:47 +0000	[thread overview]
Message-ID: <200401041849.47701.gdh@acentral.co.uk> (raw)

Hullo :)

I appear to be having a common problem, but the standard fix hasn't worked for 
me :/

I'm using a 2.4.23 kernel, with QoS options thusly: 

# QoS and/or fair queueing
#
CONFIG_NET_SCHED=y
# CONFIG_NET_SCH_CBQ is not set
CONFIG_NET_SCH_HTB=m
# CONFIG_NET_SCH_CSZ is not set
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS=y
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_NET_CLS_FW=m
CONFIG_NET_CLS_U32=m
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not set
CONFIG_NET_CLS_POLICE=y

The whole wshaper.htb script executes fine until the final two commands, and 
running the first one manually gives me:

$ tc qdisc add dev eth0 handle ffff: ingress
RTNETLINK answers: Invalid argument

Now, the standard solution I've seen is "get a newer tc", and one report [1] 
said that Debian's unstable one worked fine... so I backported it to woody, 
but had exactly the same problem :/

I even saw the q_ingress.c and q_htb.c files being compiled OK during the 
'debian/rules binary-arch' procedure so the code must be in the tc binary.

If I mis-type 'ingress', then the error changes to "RTNETLINK answers: No such 
file or directory" so it must be seeing /something/ ...

Any ideas? :D

Cheers,
Gavin.

[1] http://www.cs.helsinki.fi/linux/linux-kernel/2002-06/0035.html

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

             reply	other threads:[~2004-01-04 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-04 18:49 Gavin Hamill [this message]
2004-01-05  0:42 ` [LARTC] Ingress with WonderShaper Damion de Soto
2004-01-05  9:20 ` Gavin Hamill

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=200401041849.47701.gdh@acentral.co.uk \
    --to=gdh@acentral.co.uk \
    --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