All of lore.kernel.org
 help / color / mirror / Atom feed
From: KOVACS Krisztian <hidden@balabit.hu>
To: netfilter-devel@lists.netfilter.org
Cc: Yoshioka Tsuneo <tsuneo.yoshioka@f-secure.com>,
	Patrick McHardy <kaber@trash.net>,
	tproxy@lists.balabit.hu
Subject: Re: Request: including tproxy patch to official iptables/kernel.
Date: Tue, 17 Oct 2006 16:38:24 +0200	[thread overview]
Message-ID: <200610171638.25425@nienna> (raw)
In-Reply-To: <45331D32.5070209@trash.net>


  Hi,

On Monday 16 October 2006 07:48, Patrick McHardy wrote:
> > So, I would like to suggest to include tproxy patch to official
> > iptables/kernel release.
>
> These look quite old (2.4). The TPROXY developers were working on
> a new approach last year at the netfilter workshop, but I don't
> know if there was any further progress. Please talk to them directly
> and ask them if they want to merge it upstream, and if so to submit
> patches.

  Yes, there was significant progress since then, we're testing the 
patches at the moment. There still are a couple of problems with the new 
approach, but it certainly looks promising. I'll post the patches on 
netfilter-devel for review and comments as soon as things have settled 
down a bit.

  Instead of trying to get the 2.0 branch of tproxy merged into mainline 
we're concentrating our efforts on getting the new code working. As the 
maintainer of the current tproxy patchset, I do not consider it clean and 
safe enough to have it merged upstream.

  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. 
That's why I don't even try to get it merged.

-- 
 Regards,
  Krisztian Kovacs

  parent reply	other threads:[~2006-10-17 14:38 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 [this message]
2006-10-17 15:01     ` [tproxy] " Lennert Buytenhek
2006-10-19 14:53       ` Patrick McHardy
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=200610171638.25425@nienna \
    --to=hidden@balabit.hu \
    --cc=kaber@trash.net \
    --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.