From: Patrick McHardy <kaber@trash.net>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Yoshioka Tsuneo <tsuneo.yoshioka@f-secure.com>,
netfilter-devel@lists.netfilter.org, tproxy@lists.balabit.hu,
KOVACS Krisztian <hidden@balabit.hu>
Subject: Re: [tproxy] Re: Request: including tproxy patch to official iptables/kernel.
Date: Thu, 19 Oct 2006 16:53:29 +0200 [thread overview]
Message-ID: <45379169.4030504@trash.net> (raw)
In-Reply-To: <20061017150147.GD1598@xi.wantstofly.org>
Lennert Buytenhek wrote:
> On Tue, Oct 17, 2006 at 04:38:24PM +0200, KOVACS Krisztian wrote:
>
>
>> Moreover, I think there's no general consensus between networking
>>maintainers whether or not the features tproxy provides are worth the
>>hassles. Transparent proxying features have been removed during the 2.3
>>development as there seemed little interest in those. Of course there are
>>a handful of companies interested in having the feature in mainline, but
>>let's face the facts: the majority of users do not care about tproxy.
>
>
> There's other features and drivers in Linux where a similar thing
> applies. If tproxy doesn't get into the way when it's not used or
> turned off, why shouldn't it be merged?
Thats exactly what I was going to say :)
next prev parent reply other threads:[~2006-10-19 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 3:17 Request: including tproxy patch to official iptables/kernel Yoshioka Tsuneo
2006-10-16 5:48 ` Patrick McHardy
2006-10-16 7:28 ` Yoshioka Tsuneo
2006-10-16 7:56 ` Patrick McHardy
2006-10-17 14:38 ` KOVACS Krisztian
2006-10-17 15:01 ` [tproxy] " Lennert Buytenhek
2006-10-19 14:53 ` Patrick McHardy [this message]
2006-10-17 16:17 ` Yoshioka Tsuneo
2006-10-19 14:58 ` Patrick McHardy
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=45379169.4030504@trash.net \
--to=kaber@trash.net \
--cc=buytenh@wantstofly.org \
--cc=hidden@balabit.hu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=tproxy@lists.balabit.hu \
--cc=tsuneo.yoshioka@f-secure.com \
/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.