From: KOVACS Krisztian <hidden@sch.bme.hu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org,
Balazs Scheidler <bazsi@balabit.hu>,
Toth Laszlo Attila <panther@balabit.hu>
Subject: Re: [PATCH] Transparent Proxying Patches, Take 3 - userspace
Date: Mon, 1 Oct 2007 00:05:04 +0200 [thread overview]
Message-ID: <200710010005.04553@nessa> (raw)
In-Reply-To: <Pine.LNX.4.64.0709302330270.7130@fbirervta.pbzchgretzou.qr>
Hi Jan,
On Sunday 30 September 2007, Jan Engelhardt wrote:
> On Sep 30 2007 23:18, KOVACS Krisztian wrote:
> >Hi Patrick,
> >
> >Here is the patch adding iptables components of the 'socket' match
> >and the 'TPROXY' target. The code is pretty straightforward and basic
> >manual pages describing what the two modules do are included in the
> >patch.
>
> Hm, you asked me for my kernel patch, well you could have also asked
> for the iptables part :-p
>
> Uses the kernel-level xt_TPROXY.
Thanks, but this one is old: the userspace patch I've sent has received
significant updates since than.
As Attila has already done the userspace ipt->xt conversion we could
update it to xt_* anytime: it's just that I don't think it's worth it --
it's heavily IPv4 dependent anyway.
The 'socket' match does not support IPv6 either, however, we could add
support _without_ any changes to the userspace, so that's why it's an
x_tables match.
--
KOVACS Krisztian
next prev parent reply other threads:[~2007-09-30 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 21:18 [PATCH] Transparent Proxying Patches, Take 3 - userspace KOVACS Krisztian
2007-09-30 21:39 ` Jan Engelhardt
2007-09-30 22:05 ` KOVACS Krisztian [this message]
2007-09-30 22:40 ` [PATCH] libxt_socket, libxt_TPROXY 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=200710010005.04553@nessa \
--to=hidden@sch.bme.hu \
--cc=bazsi@balabit.hu \
--cc=jengelh@computergmbh.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=panther@balabit.hu \
/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;
as well as URLs for NNTP newsgroup(s).