From: Patrick McHardy <kaber@trash.net>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: squid3@treenet.co.nz, netfilter-devel@lists.netfilter.org,
netfilter@lists.netfilter.org, kaber@trash.net
Subject: Re: REDIRECT and IPv6
Date: Thu, 19 Jul 2007 12:20:39 +0200 [thread overview]
Message-ID: <469F3AF7.6040006@trash.net> (raw)
In-Reply-To: <20070719.182116.64281593.yoshfuji@linux-ipv6.org>
YOSHIFUJI Hideaki / 吉藤英明
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: squid3@treenet.co.nz, netfilter-devel@lists.netfilter.org,
netfilter@lists.netfilter.org, kaber@trash.net
Subject: Re: REDIRECT and IPv6
Date: Thu, 19 Jul 2007 12:20:39 +0200 [thread overview]
Message-ID: <469F3AF7.6040006@trash.net> (raw)
In-Reply-To: <20070719.182116.64281593.yoshfuji@linux-ipv6.org>
YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[ wrote:
> In article <469F280B.3070900@trash.net> (at Thu, 19 Jul 2007 10:59:55 +0200), Patrick McHardy <kaber@trash.net> says:
>
>
>>You're right, nf_conntrack_ipv4 only registeres SO_ORIGINAL_DST for
>>AF_INET, changing that should make it work I believe. I feel like
>>I'm missing something though ..
>
>
> BTW, the name of the socket option is rather bogus.
> It should be named IP_xxx, not SO_xxx because
> it is in IP level, not in socket level...
True, but its too late to change, we'd need to keep it around at
least for userspace. With TPROXY redirection should work with all
families, so presuming we'll merge it some day this might actually
be useful.
next prev parent reply other threads:[~2007-07-19 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 0:25 REDIRECT and IPv6 squid3
2007-07-19 8:59 ` Patrick McHardy
2007-07-19 9:21 ` YOSHIFUJI Hideaki / 吉藤英明
2007-07-19 10:20 ` Patrick McHardy [this message]
2007-07-19 10:20 ` Patrick McHardy
2007-07-19 9:48 ` Yasuyuki KOZAKAI
[not found] ` <200707190948.l6J9mk02018250@toshiba.co.jp>
2007-07-22 9:22 ` Amos Jeffries
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=469F3AF7.6040006@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=squid3@treenet.co.nz \
--cc=yoshfuji@linux-ipv6.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.