[LARTC] Invalid Argument

[LARTC] Invalid Argument

[Emmanuel Khamissian]

Hi,

I use tc to shape my internet traffic with linux Debian on a i386 box.
(I want to give lowest priority at napster, edonkey, and all parasit
flow).
I think that i have a good kernel configuration because i put all QoS
and networking option in module state.

All ip command run correctly, and tc qdisc and class too.

But ! 
1 - When i make a depmod i have :
 
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/net/sched/cls_fw.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/net/sched/cls_route.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/net/sched/cls_rsvp.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/net/sched/cls_rsvp6.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/net/sched/cls_tcindex.o
depmod: *** Unresolved symbols in
/lib/modules/2.4.19/kernel/net/sched/cls_u32.o

2 - When i make a 
tc filter add dev eth1 parent 1:0 protocol ip handle 1 fw classid 1:1 
it says me : 
RTNETLINK answers: Invalid argument

I try a lot of combination and syntax but nothing to do ... i always
have Invalid Argument as response.

Of course, i have already configured a qdisc and the classes.

Does somebody have any ideas ?

Thanks for all.

Emmanuel Khamissian.

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

Re: [LARTC] Invalid Argument

[Stef Coene]

On Wednesday 06 November 2002 16:37, Emmanuel Khamissian wrote:
> Hi,
>
> I use tc to shape my internet traffic with linux Debian on a i386 box.
> (I want to give lowest priority at napster, edonkey, and all parasit
> flow).
> I think that i have a good kernel configuration because i put all QoS
> and networking option in module state.
>
> All ip command run correctly, and tc qdisc and class too.
>
> But !
> 1 - When i make a depmod i have :
>
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/net/sched/cls_fw.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/net/sched/cls_route.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/net/sched/cls_rsvp.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/net/sched/cls_rsvp6.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/net/sched/cls_tcindex.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.19/kernel/net/sched/cls_u32.o
>
> 2 - When i make a
> tc filter add dev eth1 parent 1:0 protocol ip handle 1 fw classid 1:1
> it says me :
> RTNETLINK answers: Invalid argument
>
> I try a lot of combination and syntax but nothing to do ... i always
> have Invalid Argument as response.
>
> Of course, i have already configured a qdisc and the classes.
>
> Does somebody have any ideas ?
Yes.  You have problems with the modules as you can see in 1 so the commands 
in 2 are failing because the needed module can not be loaded.  Solution : 
recompile the kernel + modules so they match.  Before you compile, do "make 
clean" so all old compiled files are gone.

Stef

-- 

stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.oftc.net

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

Re: [LARTC] Invalid Argument

[David Boreham]

> RTNETLINK answers: Invalid argument

Possibly you have a mismatch between the tc binary
and the kernel module version. Look in the messages file,
or wherever you have kernel log messages go. It will
report the versions and the reason for the error.

Then build tc against the headers from the kernel code
you are running. While there is a tc binary out there,
it may not (probably isn't) built against the headers
your kernel code was built with, and so the structures
passed between the two don't match.




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

[LARTC] invalid argument

[Grace Baldonasa]

[-- Attachment #1.1: Type: text/plain, Size: 286 bytes --]

Hi All,

I cross compiled and run tc in arm platform. 
When I tried executing it I got this error. 

tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 100Mbit avpkt 1000 mpu 
64
RTNETLINK answers: Invalid argument

Is there something I'm missing here...

Thanks.

Grace

[-- Attachment #1.2: Type: text/html, Size: 500 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

Re: [LARTC] invalid argument

[gypsy]

Grace Baldonasa wrote:
> 
> Hi All,
> 
> I cross compiled and run tc in arm platform.
> When I tried executing it I got this error.
> 
> tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 100Mbit avpkt 1000
> mpu 64
> RTNETLINK answers: Invalid argument
> 
> Is there something I'm missing here...
> 
> Thanks.
> 
> Grace

I don't know what "arm" is.

Are you certain that the CBQ module loaded?  Yes, it should be a module,
not built into the kernel.

First make sure that there is only one TC executable on your system. 
Then try a few different TC commands:

tc -s qdisc ls dev eth0
tc -s class ls dev eth0
tc qdisc add dev eth0 root handle 1: htb default 30

If the htb works then the problem is, of course, cbq.  If both cbq and
htb fail but the "show" commands above work, then I can't help.  But if
all fail, your cross compile was bad.

Also try 
modprobe sch_cbq
modprobe -r sch_cbq
modprobe sch_htb
modprobe -r sch_htb
and watch your logs.

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

Re: [LARTC] invalid argument

[Grace Baldonasa]

[-- Attachment #1.1: Type: text/plain, Size: 1865 bytes --]

Hi,
Thanks for the info.
I cross compiled tc targeted to XSCALE platform. When i was trying to 
execute the tc commands that's when I encountered this invalid argument 
problem.
So now I understand, CBQ, HTB are kernel modules that needs to be loaded as 
well to use tc. 

I have a few question:
1. Is there any packages for CBQ or HTB that I can just compiled for ARM 
again.
I dont want to compile the kernel again, so if I could get the CBQ & HTB 
packages, it'll make my life easier.
2. Aside from having these modules, what else should i add? (e.g.: config 
files, init scripts.. etc)
3. If at any case I uses both HTB & CBQ would it be okay if both of these 
modules are loaded?

Thanks for the time.

Grace




On 4/27/05, gypsy <gypsy@iswest.com> wrote:
> 
> Grace Baldonasa wrote:
> >
> > Hi All,
> >
> > I cross compiled and run tc in arm platform.
> > When I tried executing it I got this error.
> >
> > tc qdisc add dev eth0 root handle 1:0 cbq bandwidth 100Mbit avpkt 1000
> > mpu 64
> > RTNETLINK answers: Invalid argument
> >
> > Is there something I'm missing here...
> >
> > Thanks.
> >
> > Grace
> 
> I don't know what "arm" is.
> 
> Are you certain that the CBQ module loaded? Yes, it should be a module,
> not built into the kernel.
> 
> First make sure that there is only one TC executable on your system.
> Then try a few different TC commands:
> 
> tc -s qdisc ls dev eth0
> tc -s class ls dev eth0
> tc qdisc add dev eth0 root handle 1: htb default 30
> 
> If the htb works then the problem is, of course, cbq. If both cbq and
> htb fail but the "show" commands above work, then I can't help. But if
> all fail, your cross compile was bad.
> 
> Also try
> modprobe sch_cbq
> modprobe -r sch_cbq
> modprobe sch_htb
> modprobe -r sch_htb
> and watch your logs.
> 
> gypsy
>

[-- Attachment #1.2: Type: text/html, Size: 2438 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

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

Re: [LARTC] invalid argument

[gypsy]

Grace Baldonasa wrote:
> 
>    I have a few question:
>   1.  Is there any packages for CBQ or HTB that I can just compiled
> for ARM again.

No.  Kernel modules must be built using the .config file in
/usr/src/linux and are specific to the things that are specified
therein.  It is not possible to compile a standalone module for any
scheduler (or much of anything else, for that matter).  (It is possible
to change the source to a previously compiled module and RE compile
that.)

>        I dont want to compile the kernel again, so if I could get the
> CBQ & HTB packages, it'll make my life easier.

Sorry, your life cannot be made easier.

>   2.  Aside from having these modules, what else should i add? (e.g.:
> config files, init scripts.. etc)

Jim DiGriz' (a nom de plume for Alexander Clouter - whose name I've just
misspelled) stuff is "the place" to start:

http://digriz.org.uk/

>   3. If at any case I uses both HTB & CBQ would it be okay if both of
> these modules are loaded?

Yes, certainly.  You'll also have modules for u32 and (e)sfq and perhaps
others like ingress policing loaded all at the same time.
 
>   Thanks for the time.
> 
> Grace
> 
> 
> On 4/27/05, gypsy <gypsy@iswest.com> wrote:
> 
>      Grace Baldonasa wrote:
>      >
>      > Hi All,
>      >
>      > I cross compiled and run tc in arm platform.
>      > When I tried executing it I got this error.
>      >
>      > tc qdisc add dev eth0 root handle 1:0 cbq bandwidth
>      100Mbit avpkt 1000
>      > mpu 64
>      > RTNETLINK answers: Invalid argument
>      >
>      > Is there something I'm missing here...
>      >
>      > Thanks.
>      >
>      > Grace
> 
>      I don't know what "arm" is.
> 
>      Are you certain that the CBQ module loaded?  Yes, it should
>      be a module,
>      not built into the kernel.
> 
>      First make sure that there is only one TC executable on your
>      system.
>      Then try a few different TC commands:
> 
>      tc -s qdisc ls dev eth0
>      tc -s class ls dev eth0
>      tc qdisc add dev eth0 root handle 1: htb default 30
> 
>      If the htb works then the problem is, of course, cbq.  If
>      both cbq and
>      htb fail but the "show" commands above work, then I can't
>      help.  But if
>      all fail, your cross compile was bad.
> 
>      Also try
>      modprobe sch_cbq
>      modprobe -r sch_cbq
>      modprobe sch_htb
>      modprobe -r sch_htb
>      and watch your logs.
> 
>      gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc