From: Andreas Henriksson <andreas@fatal.se>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] iproute2: add option to build m_xt as a tc module.
Date: Mon, 12 Apr 2010 20:13:59 +0200 [thread overview]
Message-ID: <20100412181359.GA4612@amd64.fatal.se> (raw)
In-Reply-To: <20100412083317.0d9e9f3f@nehalam>
On Mon, Apr 12, 2010 at 08:33:17AM -0700, Stephen Hemminger wrote:
> On Mon, 12 Apr 2010 13:55:38 +0200
> Andreas Henriksson <andreas@fatal.se> wrote:
>
> > Add TC_CONFIG_XT_MODULE option that can be added
> > either to Config (after ./configure) or as an argument to "make".
>
> I like the idea and will incorporate it, but do not like having more
> build options. Adding more configuration options like this is just
> lazy design "we can't figure this out, let's make the user do it".
>
> So put the patch in but there it will always be true.
Sure..... unfortunately I found problems for the patch to work.
(dlopen needs full path and module name needs to match action name)
Will send new patch as a followup to this mail.
Note: I'm not a user of any of this functionality. (including "make install"!)
I've tried testing "action ipt" with m_xt.so now, but m_xt_old.so is
completely untested!
I used the following command when testing m_xt.so:
tc qdisc add dev lo ingress
tc filter add dev lo parent ffff: protocol ip prio 1 u32 match ip src 127.1.1.1/32 action ipt -j FOOBAR
...which gave me the error "failed to find target FOOBAR",
and this is to me an indication of success since I don't have that target.
--
Andreas Henriksson
next prev parent reply other threads:[~2010-04-12 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 11:55 [PATCH] iproute2: add option to build m_xt as a tc module Andreas Henriksson
2010-04-12 15:33 ` Stephen Hemminger
2010-04-12 18:13 ` Andreas Henriksson [this message]
2010-04-12 18:19 ` [PATCH] iproute2: add option to build m_xt as a tc module (v2) Andreas Henriksson
2010-04-12 18:24 ` [PATCH] iproute2: add option to build m_xt as a tc module (v3) Andreas Henriksson
2010-04-12 18:41 ` Stephen Hemminger
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=20100412181359.GA4612@amd64.fatal.se \
--to=andreas@fatal.se \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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;
as well as URLs for NNTP newsgroup(s).