[156726] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: IPv6 Address allocation best practises for sites.

daemon@ATHENA.MIT.EDU (Tony Finch)
Mon Sep 24 19:56:45 2012

Date: Tue, 25 Sep 2012 00:56:13 +0100
From: Tony Finch <dot@dotat.at>
To: William Herrin <bill@herrin.us>
In-Reply-To: <CAP-guGWG46GDUCWriLBzyn_N7EnedLSACPZhvs2YcSWNkrfctw@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

William Herrin <bill@herrin.us> wrote:
>
> but I also can't imagine hosting more than 65,000 sites on a single
> server.

Demon's homepages service was based on IPv4 virtual hosting and had IIRC a
/16 and two /18s allocated to it. It was a single web server with a few
reverse proxies that took most of the load and that also had all the IP
addresses. The Irix version used a cunning firewall configuration to
accept connections to all the addresses without stupid numbers of virtual
interfaces; the BSD version used a kernel hack.
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/12071

On the web server we stuffed the IP address into the filesystem path name
to find the document root. (Or used various evil hacks to map the IP
address to a canonical virtual server host name before stuffing the latter
in the path.)

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.


home help back first fref pref prev next nref lref last post