From: "Samuel Jean" <jix@bugmachine.ca>
To: "Juan León" <debjuanca@gmail.com>,
"Fabrice Rafart" <fabrice.rafart@efs.sante.fr>,
<netfilter-devel@lists.netfilter.org>, <pablo@netfilter.org>,
<kaber@trash.net>, <nicboul@gmail.com>
Subject: Re: Follow packets in rules
Date: Wed, 13 Jun 2007 16:28:59 -0000 [thread overview]
Message-ID: <twig.1181752139.4605@bugmachine.ca> (raw)
In-Reply-To: <6bb85d880706130843n31d8c1a6i19a4b119c85131a1@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Wed, Jun 13, 2007, Juan León <debjuanca@gmail.com> said:
> Hi Fabrice,
>
>
> 2007/6/13, Pablo Neira Ayuso <pablo@netfilter.org>:
>> Fabrice Rafart wrote:
>> > I look for a tool to follow a packets into rules of netfilter.
>> >
>> > For example :
>> >
>> > # iptables-test -s 192.168.1.1 -d 192.168.2.1 -p tcp --dport 25
>> > --> FORWARD line 1 : -p tcp --dport 25 -j SMTP
>> > --> SMTP line 3 : -s 192.168.1.0/24 -j DROP
>> >
>> > This show me which rules matches the packet until the end.
>> >
>> > Does this exist ?
There was the TRACE target born for this purpose a couple years ago.
http://svn.netfilter.org/cgi-bin/viewcvs.cgi/branches/patch-o-matic-ng/linux-2.6.11/TRACE/?rev=3680
It sure will require a bit of hacking for recent kernels.
Pablo, Patrick --
Is this an interesting feature that worths merging in mainline, or
patch-o-matic at least ?
Best regards,
Samuel
next prev parent reply other threads:[~2007-06-13 16:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 18:08 Follow packets in rules Fabrice Rafart
2007-06-12 21:41 ` Simon
2007-06-13 7:31 ` Fabrice Rafart
2007-06-18 16:12 ` Simon
2007-06-18 16:14 ` Patrick McHardy
2007-06-13 8:57 ` Pablo Neira Ayuso
2007-06-13 15:43 ` Juan León
2007-06-13 16:28 ` Samuel Jean [this message]
2007-06-13 16:53 ` Patrick McHardy
2007-06-13 19:43 ` Jozsef Kadlecsik
2007-06-14 7:55 ` Fabrice Rafart
2007-06-14 13:13 ` Patrick McHardy
2007-06-14 14:18 ` Jozsef Kadlecsik
2007-06-14 14:23 ` Patrick McHardy
2007-06-18 10:16 ` Jozsef Kadlecsik
2007-06-18 12:49 ` Patrick McHardy
2007-06-18 13:05 ` Jozsef Kadlecsik
2007-06-18 13:08 ` Patrick McHardy
2007-06-22 14:20 ` Patrick McHardy
2007-06-23 16:45 ` Jozsef Kadlecsik
2007-06-24 14:48 ` Patrick McHardy
2007-06-25 12:19 ` Patrick McHardy
2007-06-25 12:49 ` Jan Engelhardt
2007-06-25 12:52 ` Patrick McHardy
2007-06-25 13:00 ` Patrick McHardy
2007-06-25 13:52 ` Jan Engelhardt
2007-06-25 13:55 ` Patrick McHardy
2007-07-03 15:07 ` Fabrice Rafart
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=twig.1181752139.4605@bugmachine.ca \
--to=jix@bugmachine.ca \
--cc=debjuanca@gmail.com \
--cc=fabrice.rafart@efs.sante.fr \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nicboul@gmail.com \
--cc=pablo@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 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.