Ingress with WonderShaper
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 setCONFIG_NET_SCH_HTB=m
# CONFIG_NET_SCH_CSZ is not setCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=mCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=mCONFIG_NET_QOS=yCONFIG_NET_ESTIMATOR=yCONFIG_NET_CLS=yCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_ROUTE=yCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=m
# CONFIG_NET_CLS_RSVP is not set
# CONFIG_NET_CLS_RSVP6 is not setCONFIG_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 / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Hi Gavin,
You're missing the INGRESS option in the kernel,
you should have:
Quoted 5 lines
# QoS and/or fair queueing
#CONFIG_NET_SCHED=y
#CONFIG_NET_SCH_CBQis not setCONFIG_NET_SCH_HTB=m
Quoted 8 lines
#
CONFIG_NET_SCH_CSZis not setCONFIG_NET_SCH_PRIO=mCONFIG_NET_SCH_RED=mCONFIG_NET_SCH_SFQ=mCONFIG_NET_SCH_TEQL=mCONFIG_NET_SCH_TBF=mCONFIG_NET_SCH_GRED=mCONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_INGRESS=y
Quoted 11 lines
CONFIG_NET_QOS=yCONFIG_NET_ESTIMATOR=yCONFIG_NET_CLS=yCONFIG_NET_CLS_TCINDEX=mCONFIG_NET_CLS_ROUTE4=mCONFIG_NET_CLS_ROUTE=yCONFIG_NET_CLS_FW=mCONFIG_NET_CLS_U32=m
#CONFIG_NET_CLS_RSVPis not set
#CONFIG_NET_CLS_RSVP6is not setCONFIG_NET_CLS_POLICE=y
You'll need the NETFILTER kernel option turned on to be able to see/select the INGRESS option.
Quoted 5 lines
I even saw the
q_ingress.candq_htb.cfiles 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/ ...
yeah, it looks like the tc binary is right, so once you fix the kernel, everything should work.
Signature · 11 lines
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Damion de Soto - Software Engineer email: [email protected] SnapGear - A CyberGuard Company --- ph: +61 7 3435 2809 | Custom Embedded Solutions fax: +61 7 3891 3630 | and Security Appliances web: http://www.snapgear.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --- Free Embedded Linux Distro at http://www.snapgear.org --- _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 8 lines · Damion de Soto
Hi Gavin,
You're missing the INGRESS option in the kernel,
you should have:
CONFIG_NET_SCH_INGRESS=yYou'll need the NETFILTER kernel option turned on to be able to see/select the INGRESS option.
You wonderful man :) I didn't even realise this box didn't have netfilter enabled, so that kills two birds with one stone :)
Thanks so much!
Cheers,
Gavin.
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/