From owner-freebsd-isp Sun Mar 8 02:54:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10111 for freebsd-isp-outgoing; Sun, 8 Mar 1998 02:54:10 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10106 for ; Sun, 8 Mar 1998 02:54:07 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id VAA26880; Sun, 8 Mar 1998 21:54:00 +1100 (EST) Date: Sun, 8 Mar 1998 21:53:59 +1100 (EST) From: "Daniel O'Callaghan" To: mikel@cynet.net.au cc: freebsd-isp@FreeBSD.ORG Subject: Re: To IP or not to IP WWW servers In-Reply-To: <199803080816.TAA02881@esimene.cynet.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Mikel, On Sun, 8 Mar 1998 mikel@cynet.net.au wrote: > With IP space dwindling what are the lists thoughts on using individual IP IP address space is not dwindling as much as people think. As far as class C address allocations go, we are about 2/3 of the way through the address space 192-223. However, large ISPs are being allocated class A networks for subdivision, and the real problem is routing table management, whereby ISPs don't adequately aggregate the networks they advertise. In Australia the problem was magnified by the policy of AARnet to allocate IPs to anyone who requested until last year, when it suddenly became impossible for even small ISPs to get addresses. If you want to do virtual ftp or telnet, you *must* use IPs. If you intend having lots of web servers, get a netblock from your upstream ISP (Connect.com.au, I believe) > Also, at what point do the practical limits start getting reached with > aliasing IPs onto the VWS server card, or are they sufficiently high that > other issues such as capacity/reliability come into play first? If you are putting lots of web servers on, you would do better to put the /24 or more onto lo0 and treat the web server machine's ethernet IP address as the gateway to the web network. A couple of years ago someone tested FreeBSD 2.0.5 with 5000 IP addresses with no ill effects. After that it got too boring an exercise for them to continue. Cheers, Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message