From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
djones@rossove.com, LKML Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org
Subject: Re: Scaling Max IP address limitation
Date: Mon, 25 Jun 2007 11:36:04 +0200 [thread overview]
Message-ID: <467F8C84.9020404@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0706242153240.11964@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Jun 24 2007 15:08, Kyle Moffett wrote:
>
>>Do you really need that many IP addresses? When somebody finally gets
>>around to implementing REDIRECT support for ip6tables then you could
>>just redirect them all to the same port on the local system.
>
>
> The way I see it, it's: "if someone gets around to implement *IPv6 NAT*"
> (which, if its designers were asked, is contrary to the idea of ipv6).
You don't necessarily need NAT for REDIRECT, so we might actually have
an ip6tables REDIRECT some day. Check out the current TPROXY patches
for an example how to do it without NAT in case you're interested.
prev parent reply other threads:[~2007-06-25 9:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <467EA7C1.4080006@rossove.com>
2007-06-24 18:02 ` Scaling Max IP address limitation Andrew Morton
2007-06-24 19:59 ` Robert Iakobashvili
2007-06-25 0:03 ` David Jones
2007-06-25 8:47 ` Robert Iakobashvili
2007-06-25 9:30 ` Jan Engelhardt
2007-06-25 9:41 ` Robert Iakobashvili
2007-06-25 12:38 ` Jan Engelhardt
2007-06-25 12:44 ` Robert Iakobashvili
2007-06-25 17:26 ` David Jones
[not found] ` <7e63f56c0706260756q504bc4c2sa8905fbaeed4308d@mail.gmail.com>
2007-06-26 14:58 ` Robert Iakobashvili
2007-06-24 20:19 ` Robert Iakobashvili
2007-06-24 19:08 ` Kyle Moffett
2007-06-24 19:54 ` David Stevens
2007-06-24 19:58 ` Jan Engelhardt
2007-06-24 20:44 ` david
2007-06-24 20:52 ` Jan Engelhardt
2007-06-24 21:51 ` Kyle Moffett
2007-06-25 9:36 ` Patrick McHardy [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=467F8C84.9020404@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=djones@rossove.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=netdev@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).