All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nataniel Klug <nata@cnett.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Another question (now about u32)
Date: Tue, 04 Apr 2006 19:06:58 +0000	[thread overview]
Message-ID: <4432C3D2.1090201@cnett.com.br> (raw)
In-Reply-To: <4432B431.7070104@cnett.com.br>

Guys,

I tryed to make the u32 module up, but didnt work as well:

[root@ns1 sched]# ls
cls_fw.ko     cls_rsvp.ko  sch_cbq.ko     sch_gred.ko  sch_htb.ko      
sch_netem.ko  sch_red.ko  sch_tbf.ko
cls_route.ko  cls_u32.ko   sch_dsmark.ko  sch_hfsc.ko  sch_ingress.ko  
sch_prio.ko   sch_sfq.ko  sch_teql.ko
[root@ns1 sched]# modprobe cls_u32
[root@ns1 sched]# lsmod
Module                  Size  Used by
cls_u32                 8324  0
sch_htb                19072  2
ipt_MARK                2688  43
cls_fw                  5248  4
sch_sfq                 6016  5
sch_cbq                17536  1
iptable_mangle          3072  1
ipt_LOG                 7552  2
iptable_filter          3200  1
ipt_ipp2p               7552  0
agpgart                33632  0
i2c_viapro              8592  0
i2c_core               21504  1 i2c_viapro
8139too                30464  0
mii                     5760  1 8139too
ext3                  132232  4
mbcache                17028  1 ext3
jbd                    83736  1 ext3
[root@ns1 sched]# tc filter add dev eth1 parent 1:0 protocol ip prio 1 
u32 match ip sport 80 0xffff flowid 1:10
RTNETLINK answers: Invalid argument
We have an error talking to the kernel

Att,

Nataniel Klug

Nataniel Klug escreveu:
>    Hello all,
>
>    I am trying to match some conections using u32 but I tryed this:
>
> [root@ns1 ~]# tc filter add dev eth1 parent 1:0 protocol ip prio 1 u32 
> match ip src 0/0 match ip dst 0/0 match ip sport 80 0xffff flowid 1:10
> RTNETLINK answers: Invalid argument
> We have an error talking to the kernel
> [root@ns1 ~]#
>
>
>    I have this class at device eth1:
>
> [root@ns1 ~]# tc class show dev eth1
> class htb 1:1 root rate 100Mbit ceil 100Mbit burst 18412b cburst 51587b
> class htb 1:10 parent 1:1 leaf 10: prio 1 rate 3Mbit ceil 3Mbit burst 
> 18Kb cburst 3099b
> class htb 1:20 parent 1:1 leaf 20: prio 5 rate 500Kbit ceil 500Kbit 
> burst 18Kb cburst 1849b
>
>    And this qdisc:
>
> [root@ns1 ~]# tc qdisc show dev eth1
> qdisc htb 1: r2q 10 default 20 direct_packets_stat 10
> qdisc sfq 10: parent 1:10 limit 128p quantum 1514b perturb 10sec
> qdisc sfq 20: parent 1:20 limit 128p quantum 1514b perturb 10sec
>
>    I have looked into kernel and into this paramenter:
>
> Networking > Networking Options > U32 Classifier (module)
>
>    It is enable as a module.
>
>    Can someone help me? My box is a Fedora Core 3 using kernel 2.6.13.4.
>
> PS.: Thanks all guys who have answered me about my other question 
> (QoS). It was very useful hints. Now I think my QoS is working almost 
> 100% ok.
>
> Att,
>
> Nataniel Klug
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      parent reply	other threads:[~2006-04-04 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04 18:00 [LARTC] Another question (now about u32) Nataniel Klug
2006-04-04 18:52 ` Jody Shumaker
2006-04-04 18:59 ` Nataniel Klug
2006-04-04 19:06 ` Nataniel Klug [this message]

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=4432C3D2.1090201@cnett.com.br \
    --to=nata@cnett.com.br \
    --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.