From: Patrick McHardy <kaber@trash.net>
To: Andreas Henriksson <andreas@fatal.se>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Problem using iptables MARK from tc.
Date: Mon, 12 Jan 2009 05:10:25 +0100 [thread overview]
Message-ID: <496AC2B1.4010603@trash.net> (raw)
In-Reply-To: <1231248276.11025.148.camel@amd64.fatal.se>
Andreas Henriksson wrote:
> Hello Patrick and co.
>
> I was hoping you might have some time to help out with a problem in tc
> related to iptables modules. A bit of historical knowledge about
> libipt_MARK.c is probably useful.
>
> The full bug-report is available at:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510924
>
> In iproute2's tc/m_ipt.c there's a function called get_target_name with
> some logic to look up a symbol with the same name as the so-file. (ie.
> "mark" for libipt_MARK.so or libxt_MARK.so).
> There seems to have been a structure with that name in the past, but
> nowadays there are several ones which are jacked in with a registration
> hook.
>
> Does this sound about right? Do you have any suggestions on how the tc
> modules functionality could be fixed up to find what it needs properly?
> The structures doesn't even seem to be exported in the ABI anymore...
We've added a shared library to iptables so m_ipt doesn't have
to reimplement things, which is pretty much guaranteed to break
occasionally. It doesn't contain all the functionality thats
needed yet, but it should be fairly easy to add. Most likely
you just need to move the code around.
prev parent reply other threads:[~2009-01-12 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 13:24 Problem using iptables MARK from tc Andreas Henriksson
2009-01-12 4:10 ` Patrick McHardy [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=496AC2B1.4010603@trash.net \
--to=kaber@trash.net \
--cc=andreas@fatal.se \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).