All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshioka Tsuneo <tsuneo.yoshioka@f-secure.com>
To: netfilter-devel@lists.netfilter.org
Subject: Request: including tproxy patch to official iptables/kernel.
Date: Mon, 16 Oct 2006 12:17:58 +0900	[thread overview]
Message-ID: <20061016114331.AF36.TSUNEO.YOSHIOKA@f-secure.com> (raw)

Hello netfilter developers

There is tproxy patch for netfilter(iptables).
tproxy enables application to set source IP address.
I think that only tproxy patch can enable transparent proxy keeping
source IP addresses.

And, until now, tproxy is developed and is used for long term, and seems
stable to include official iptables/kernel release. There is also a patch
for latest kernel.

So, I would like to suggest to include tproxy patch to official
iptables/kernel release.
Can you think about including this patch to official iptables/kernel
release, if possible ?

   TPROXY
       http://www.balabit.com/products/oss/tproxy/

   patch-o-matic extra repository
     tproxy - iptables TPROXY target
       http://www.iptables.org/projects/patch-o-matic/pom-extra.html#pom-extra-tproxy


Thank you !

-- 
Nihon F-Secure Corporation
(Yoshioka Tsuneo)
E-MAIL: Tsuneo.Yoshioka@f-secure.com

             reply	other threads:[~2006-10-16  3:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16  3:17 Yoshioka Tsuneo [this message]
2006-10-16  5:48 ` Request: including tproxy patch to official iptables/kernel 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
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=20061016114331.AF36.TSUNEO.YOSHIOKA@f-secure.com \
    --to=tsuneo.yoshioka@f-secure.com \
    --cc=netfilter-devel@lists.netfilter.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 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.