From owner-freebsd-questions Sat Oct 7 16:28:05 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA00844 for questions-outgoing; Sat, 7 Oct 1995 16:28:05 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id QAA00836 for ; Sat, 7 Oct 1995 16:27:59 -0700 Received: from puffin.pelican.com by pelican.com with smtp (Smail3.1.28.1 #5) id m0t1iej-000K2mC; Sat, 7 Oct 95 16:27 WET DST Received: by puffin.pelican.com (Smail3.1.29.1 #9) id m0t1iej-0000ReC; Sat, 7 Oct 95 16:27 PDT Message-Id: Date: Sat, 7 Oct 95 16:27 PDT From: pete@puffin.pelican.com (Pete Carah) To: questions@freebsd.org Subject: Re: multiple httpd's listening to different IP addresses? In-Reply-To: <199510071800.LAA25658@aslan.cdrom.com> Sender: owner-questions@freebsd.org Precedence: bulk In article <199510071800.LAA25658@aslan.cdrom.com>, Justin T. Gibbs wrote: >>I have multiple domains served by my site and I want to be able to have >>multiple http daemons listening to different IP addresses (but all on port >>80). This, of course, is so that I can allocate a separate IP address to >>each domain, alias the network interface to receive the multiple addresses >>and then voila!, be able to use URLs such as: >Check out Apache's "virtual host" settings. Apache is in the FreeBSD >ports collection. Works great. A note that probably isn't with apache; the proper syntax to use with ifconfig alias is ifconfig inet www.anglelinear.com netmask 255.255.255.255 alias (we put the extra ifconfig's in rc.local right before the startup of apache) (and that address is real). An advantage of putting these ifconfigs that late in startup is that the dns is running by then so the addresses can be symbolic. (look at www1.clubnet.net or www.macom-phi.com for others of the virtual servers on that machine) AND - routing doesn't seem to work right if any of the IP addresses in a set of aliases is in another subnet. (we tried to handle a IP change from a provider block to our own CIDR by routing both in the router (which works fine) and aliasing the nameserver to both subnet addresses. UDP fails completely and TCP sometimes does.) If anyone know how to make *that* work it'd be nice... What we ended up with was separate boxes temporarily; it's nice that it is so easy to shadow nameservers (news is a little harder since we don't have 9g drives running out our ears. :-(. -- Pete