From: Susan Hinrichs <shinrich@network-geographics.com>
To: msk@cloudmark.com
Cc: netfilter@vger.kernel.org
Subject: Re: nfqueue vs. tproxy
Date: Wed, 07 Dec 2011 19:43:41 -0600 [thread overview]
Message-ID: <1323308622.17564.190.camel@kiki> (raw)
In-Reply-To: <201112080025.pB80PGIe091691@medusa.blackops.org>
You could do that, but the second recipient of the code would lose the
original destination address and port information.
This would be more like the REDIRECT target in iptables.
On Wed, 2011-12-07 at 16:25 -0800, msk@cloudmark.com wrote:
> I've been reading up on tproxy and nfqueue. Just to confirm my understanding
> of the two:
>
> Could one write a layer of code that uses the nfq_*() functions to basically
> implement what tproxy can do by simply adjusting the destination information
> and checksum, and then returning NF_REPEAT verdicts for each?
>
> Thanks,
> -MSK
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-08 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 0:25 nfqueue vs. tproxy msk
2011-12-08 1:43 ` Susan Hinrichs [this message]
2011-12-08 4:21 ` Jan Engelhardt
2011-12-08 10:49 ` Susan Hinrichs
2011-12-08 2:21 ` Jan Engelhardt
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=1323308622.17564.190.camel@kiki \
--to=shinrich@network-geographics.com \
--cc=msk@cloudmark.com \
--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