netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amos Jeffries <squid3@treenet.co.nz>
To: KOVACS Krisztian <hidden@sch.bme.hu>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: TPROXY / DIVERT
Date: Mon, 13 Jul 2009 10:22:53 +1200	[thread overview]
Message-ID: <f5c0fcbe39b48cd430b31abeb0d0c046@mail.treenet.co.nz> (raw)
In-Reply-To: <20090712171702.GA1668@sch.bme.hu>

On Sun, 12 Jul 2009 19:17:02 +0200, KOVACS Krisztian <hidden@sch.bme.hu>
wrote:
> Hi,
> 
> On Fri, Jul 10, 2009 at 11:55:12PM +1200, Amos Jeffries wrote:
>> Amos Jeffries wrote:
>> >TPROXY is turning out alright for most of our users. The iptables and 
>> >kernel changes seem to work perfectly. Thanks a lot guys.
>> >
>> >We are just working our way through how it needs to fit into various 
>> >other network toolchains and re-documenting.
>> >
>> >
>> >Two netfilter relevant questions have arisen:
>> >
>> >The old one: How long until IPv6 TPROXY support is available?
>> >
>> >
>> >The new one: How to configure TPROXY on a bridge?
>> >
>> 
>> Alright Nevermind the bridge Q. has been resolved now.
> 
> Cool. What was the problem?

Broken NIC drivers on the test machine. :(

> 
>> The IPv6 Q. is still open. hint, hint :)
> 
> As far as I know noone is working on this. Theoretically, shouldn't be
too
> complicated, though.
> 
> I'll try to look into this once I find the time.

I keep hearing that, but don't have anywhere near the knowledge level or
time to follow up myself. Thank you for anything you can do towards this.
There seem to be a fair number of people seeking it.

AYJ

      reply	other threads:[~2009-07-12 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  6:24 TPROXY / DIVERT Amos Jeffries
2009-07-10 11:55 ` Amos Jeffries
2009-07-12 17:17   ` KOVACS Krisztian
2009-07-12 22:22     ` Amos Jeffries [this message]

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=f5c0fcbe39b48cd430b31abeb0d0c046@mail.treenet.co.nz \
    --to=squid3@treenet.co.nz \
    --cc=hidden@sch.bme.hu \
    --cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).