From owner-freebsd-questions Mon Nov 20 4:38:38 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 38EE637B479 for ; Mon, 20 Nov 2000 04:38:36 -0800 (PST) Received: (qmail 97748 invoked by uid 100); 20 Nov 2000 12:38:35 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14873.6987.340558.516226@guru.mired.org> Date: Mon, 20 Nov 2000 06:38:35 -0600 (CST) To: Pontius Malmberg Cc: questions@freebsd.org Subject: Re: multiple web servers behind firewall In-Reply-To: <104801544@toto.iv> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pontius Malmberg types: > i have one ip coming in on a cable modem, is it > possible for me to setup a "gateway server" (maybe > using name-based hosting) and provide multiple > physical web servers behind firewall??? if possible, > then how would i go about doing this? Of course it's possible. You need to run an http proxy on the firewall that lets you redirect to different IP addresses via name-based hosting. The question is whether or not such a proxy already exists. You may be able to make Apache do this with a proxy module. If there isn't a proxy, you'll have to write it (which will give you a much better understanding of what's going on in web servers). > i am fully aware of the bandwidth constraint that > comes with cable modem, but i just want to have the > experience when i am going out there looking for a > job? :o) You're not likely to run into this problem when you're looking for a job. Companies that want to run multiple web servers typically find it easier just to buy the extra IP addresses they need. If you want experience running multiple name or ip-based servers on one machine, you can do that behind your firewall. Even if there's only one of you behind the firewall, there's a reasonable reason for wanting three servers: 1) Your real web server, 2) A test server - a clone of the web server that you install new things on to test before pushing them to #1, 3) An internal server - that runs things you don't want to make available to the outside world. You can run the last two on a machine you don't expose the to the world.