From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter@lists.netfilter.org
Subject: Re: How to find the chain which calls the match
Date: Tue, 10 Oct 2006 11:24:08 +0200 [thread overview]
Message-ID: <452B66B8.3060805@plouf.fr.eu.org> (raw)
In-Reply-To: <452A68BE.8030605@it.uc3m.es>
Hello,
aoliva a écrit :
>
> Hi all, I am writing a match for iptables and I would like it to have a
> different behaviour when it is called from different chains (e.g.
> different behaviour when called from INPUT than OUTPUT) anyone knows how
> to check in the match which is the chain that is calling it?
I do not have the answer to your question, but you could watch the code
of the NETMAP target which does destination NAT in the PREROUTING chain
and source NAT in the POSTROUTING chain. By the way, how does it behave
in the OUTPUT chain ?
prev parent reply other threads:[~2006-10-10 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 14:51 How to find out packet latency? Mohammad Farooq
2006-10-09 15:13 ` How to find the chain which calls the match aoliva
2006-10-09 15:20 ` aoliva
2006-10-09 15:58 ` Gáspár Lajos
2006-10-09 16:53 ` aoliva
2006-10-10 9:24 ` Pascal Hambourg [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=452B66B8.3060805@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@lists.netfilter.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