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/
Hi Gavin, You''re missing the INGRESS option in the kernel, you should have:> # 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=mCONFIG_NET_SCH_INGRESS=y> 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=yYou''ll need the NETFILTER kernel option turned on to be able to see/select the INGRESS option.> 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/ ...yeah, it looks like the tc binary is right, so once you fix the kernel, everything should work. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Damion de Soto - Software Engineer email: damion@snapgear.com 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 / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
On Mon, 2004-01-05 at 00:42, Damion de Soto wrote:> Hi Gavin, > You''re missing the INGRESS option in the kernel, > you should have:> CONFIG_NET_SCH_INGRESS=y> You''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 / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/