From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Cloning Traffic had having it processed by two different hosts - TEE
Date: Wed, 23 Apr 2008 14:40:15 -0500 [thread overview]
Message-ID: <480F909F.1050100@riverviewtech.net> (raw)
In-Reply-To: <480F2A96.3020603@rz.uni-karlsruhe.de>
On 04/23/08 07:24, Bjoern Weiland wrote:
> Now I am wondering, if my undertaking is realizable and how it can be
> done most efficiently... I am open for any hints, maybe there are some
> other solutions as well...
I'm not sure if it will work or not, but have you considered using the
user space daemons to process the traffic? I think you can use the
NFQUEUE (?) target to redirect the packets as they are to user space
which could then send one packet on as is and duplicate and modify the
second packet before sending it on.
Grant. . . .
prev parent reply other threads:[~2008-04-23 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 12:24 Cloning Traffic had having it processed by two different hosts - TEE Bjoern Weiland
2008-04-23 15:07 ` Jan Engelhardt
2008-04-24 13:21 ` Bjoern Weiland
2008-04-23 19:40 ` Grant Taylor [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=480F909F.1050100@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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