From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [PATCH] mark in u32
Date: Thu, 06 Jan 2005 13:27:24 +0000 [thread overview]
Message-ID: <41DD3CBC.1010108@dsl.pipex.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501051151270.8614@webhosting.rdsbv.ro>
Thomas Graf wrote:
> * Andy Furniss <41DCFE27.4030704@dsl.pipex.com> 2005-01-06 09:00
>
>>I retried with a vanilla 2.6.10 + iptables 1.2.11 on a different box and
>>it is the same.
>
>
> 2 options:
> 1) get latest -bk snapshot and apply http://people.suug.ch/~tgr/patches/pending/
> The patchset fixes a lot of small issues, adds action capabilities to
> all classifiers, and extends tcindex and route classifier to be changeable
> during runtime. If problem remains, goto to 2.
Could take some time - I don't have bitkeeper and will have to find some
disk space. I'll try soon(ish).
> 2) Provided detailed information about how your police configuration
> looks like, wehther you are using CONFIG_NET_CLS_ACT, etc. so I can fix it.
I just tried some variations - but get an error - I am using new tc and get
RTNETLINK answers: Invalid argument
We have an error talking to the kernel
with the last 2 - see below.
>
>
>>The only difference between working and not working cases when using tc
>>-s qdisc ls dev eth0 is the drops count. The stats are OK apart from that.
>
>
> And it is definitely classifier specific to fw?
I don't know what should I test with :-)
tc filter add dev eth0 parent ffff: protocol ip prio 1 u32 match ip src
0.0.0.0/0 police rate 100kbit burst 10k drop flowid :1
Works OK.
tc filter add dev eth0 parent ffff: protocol 6 prio 1 u32 match ip src
0.0.0.0/0 police rate 100kbit burst 10k drop flowid :1
Doesn't work even on 2.4 that fw test works on.
[andy@amd ~]$ grep NET_CLS /boot/config-lfs-5.1-2.4.26
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=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_POLICE=y
Is the 2.4 that's OK.
[andy@amd ~]$ grep NET_CLS /boot/config-2.6.10
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_IND is not set
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_ACT=y
Is the fail on fw but work on ip src 0.0.0.0/0
Below are the ones that throw an error when I tc filter add (anything)
tc qdisc add dev eth0 handle ffff: ingress is OK
[andy@amd ~]$ grep NET_CLS /boot/config-2.6.10-2
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_IND is not set
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
# CONFIG_NET_CLS_ACT is not set
CONFIG_NET_CLS_POLICE=y
[andy@amd ~]$ grep NET_CLS /boot/config-2.6.10-3
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_IND is not set
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
CONFIG_NET_CLS_ACT=y
CONFIG_NET_CLS_POLICE=y
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-01-06 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 10:05 [LARTC] [PATCH] mark in u32 Catalin(ux aka Dino) BOIE
2005-01-05 14:59 ` Andy Furniss
2005-01-05 15:10 ` Thomas Graf
2005-01-05 15:25 ` Andy Furniss
2005-01-05 15:52 ` Thomas Graf
2005-01-05 16:40 ` Andy Furniss
2005-01-05 23:44 ` Stephen Hemminger
2005-01-06 8:53 ` Andy Furniss
2005-01-06 9:00 ` Andy Furniss
2005-01-06 9:50 ` Thomas Graf
2005-01-06 13:27 ` Andy Furniss [this message]
2005-01-06 16:45 ` Thomas Graf
2005-01-06 23:23 ` Andy Furniss
2005-01-06 23:25 ` Thomas Graf
2005-01-06 23:35 ` Andy Furniss
2005-01-07 2:45 ` Andy Furniss
2005-01-07 10:29 ` Andy Furniss
2005-01-08 2:34 ` Andy Furniss
2005-01-08 4:14 ` gypsy
2005-01-08 4:58 ` gypsy
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=41DD3CBC.1010108@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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.