From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Follow packets in rules
Date: Mon, 18 Jun 2007 14:49:36 +0200 [thread overview]
Message-ID: <46767F60.5080208@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0706181208160.13474@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> Attached you can find the reworked TRACE target, which does not suffer
> from backward incompatibility. Unfortunately I had to steal one unused
> bit from skbuff to be able to mark the packets so that it surely does
> not clash with any rules using the standard "MARK" target. Logging
> level, flags and type are hardcoded. What do you think?
Looks pretty good. Maybe we can avoid using the skb bit though, what
do you think about letting the user set a special "trace-mark" value
through /proc and using that? Not sure if thats better or worse :)
next prev parent reply other threads:[~2007-06-18 12:49 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
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 [this message]
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=46767F60.5080208@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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 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.