From: Jarek Poplawski <jarkap@poczta.onet.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: What am I missing?
Date: Mon, 24 Jul 2006 13:01:55 +0000 [thread overview]
Message-ID: <loom.20060724T144823-710@post.gmane.org> (raw)
Ray Van Dolson <rayvd <at> digitalpath.net> writes:
>
> On a custom compiled Linux 2.6.13 kernel...
>
> # tc qdisc add dev ppp145 handle ffff: ingress
> # tc filter add dev ppp145 parent ffff: protocol ip prio 50 u32 match ip src
0.0.0.0/0 police rate 384kbit
> burst 10k drop flowid :1
> RTNETLINK answers: Invalid argument
>
> This works fine on a CentOS machine and my Fedora Core 2 box with default
> kernel. I'm trying to figure out what is missing in the custom built 2.6.13
> kernel. strace isn't real helpful, and there doesn't appear to be a way to
> make tc present more useful error messages...
>
> Non ingress filtering works. Here's an excerpt from kernel config:
...
> Any ideas? Can paste entire kernel config if necessary.
You didn't write anything about this box: distro or previous kernel.
Maybe you should try to recompile or get newer version of iproute?
Jarek P.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-07-24 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 13:01 Jarek Poplawski [this message]
2006-07-27 16:45 ` [LARTC] Re: What am I missing? Ray Van Dolson
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=loom.20060724T144823-710@post.gmane.org \
--to=jarkap@poczta.onet.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox