public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zehetbauer <thomasz@hostmaster.org>
To: linux-kernel@vger.kernel.org
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: netfilter IPv6 support
Date: Fri, 27 Aug 2004 12:02:24 +0200	[thread overview]
Message-ID: <1093600944.3497.51.camel@hostmaster.org> (raw)
In-Reply-To: <20040826211107.GA30080@havoc.gtf.org>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

On Don, 2004-08-26 at 17:11 -0400, Jeff Garzik wrote:
> For example, a NAT box behind which 32,000 hosts sit, or something like
> that :)

NAT is limited to count(official addresses)*65535 connections anyway.

One of the most important features of IPv6 is to reconcile today's
interNAT to a homogenous internet as it was before and intended to be.
If someone wants then to put 32k hosts behind a single linux router he
would better provide the necessary hardware for it.

Tom

-- 
  T h o m a s   Z e h e t b a u e r   ( TZ251 )
  PGP encrypted mail preferred - KeyID 96FFCB89
      finger thomasz@hostmaster.org for key

Sacrilegia minuta puniuntur, magna in triumphis feruntur
                                      - Seneca



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

      reply	other threads:[~2004-08-27 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 18:52 netfilter IPv6 support Thomas Zehetbauer
2004-08-26 20:00 ` David S. Miller
2004-08-26 21:25   ` Thomas Zehetbauer
2004-08-26 22:05     ` Willy Tarreau
2004-08-27 10:02       ` Thomas Zehetbauer
2004-08-26 20:25 ` Jeff Garzik
2004-08-26 21:06   ` David S. Miller
2004-08-26 21:11     ` Jeff Garzik
2004-08-27 10:02       ` Thomas Zehetbauer [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=1093600944.3497.51.camel@hostmaster.org \
    --to=thomasz@hostmaster.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox