From owner-freebsd-isp Wed Dec 16 07:52:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00899 for freebsd-isp-outgoing; Wed, 16 Dec 1998 07:52:33 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00894 for ; Wed, 16 Dec 1998 07:52:31 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id QAA30170; Wed, 16 Dec 1998 16:52:04 +0100 Date: Wed, 16 Dec 1998 16:52:03 +0100 (CET) From: N To: Troy Settle cc: freebsd-isp@FreeBSD.ORG Subject: Re: Aliased IPs In-Reply-To: Message-ID: <981216164530.29668A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As our web hosting business grows, I'm finding myself aliasing more and > more IP addresses to accomodate. FreeBSD and apache are holding up like > champs, but my local routing tables are getting a little big. Why do you need one IP address per website? You can use Apache's ability to distinguish between different virtual hosts based on the server name passed by almost all browsers currently in use. > I'm about to dedicate a full /24 to hosting, and would like to get it > configured in such a way that I only see a summary route to cover the > whole subnet, and not each individual /32. > > If it helps, I'm running gated (needed for OSPF until I can get our NAS > onto a seperate ethernet segment). If you need to configure gated to only announce a summary, ask on gated-people@merit.edu. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message