Re: [cobalt-users] multiple web servers behind firewall

[Kris Dahl <kris@xxxxxxxxxxxxx>]

on 3/6/00 6:11 PM, Nathan Martinez at nathanm@xxxxxxxxxx wrote:

> I have name-based hosting setup right now...but it is only on one machine.
> How would I go about having outside requests to the same IP address go to a
> different internal ip address?  Can name-based hosting do this for me?  Do I
> just have a webserver setup on the firewall that has all of the virtual
> hosts setup pointing to the correct internal IP address?  I am going to
> setup some test machines tomorrow and try some different stuff.  I will
> report my findings if anyone is interested.
> 
> -Nathan Martinez
> 
> -----Original Message-----
> From: Kris Dahl <kris@xxxxxxxxxxxxx>
> To: cobalt-users@xxxxxxxxxxxxxxx <cobalt-users@xxxxxxxxxxxxxxx>
> Date: Monday, March 06, 2000 5:17 PM
> Subject: Re: [cobalt-users] multiple web servers behind firewall
> 
> 
>> on 3/6/00 4:05 PM, Nathan Martinez at nathanm@xxxxxxxxxx wrote:
>> 
>>> This may be slightly off topic for this list, but I figured that it could
>>> still prove useful for some people.  I have a firewall setup with
> multiple
>>> webservers behind it.  Because we are running on a DSL connection, we do
> not
>>> have very many IP's and are trying to only use one of our "real" IP's for
>>> all of our webservers.  Is it possible to do something similar to port
>>> forwarding here?  I want to be able to do port forwarding based upon the
>>> domain name that is trying to be reached.  For example, abc.com will be
>>> forwarded to 192.168.0.10 and xyz.com will be forwarded to 192.168.11.
>>> Everything that I have read so far indicates that the only condition that
>>> can be used here is the IP that is trying to be reached.  Since I have
>>> multiple different private IP's all masqueraded under the same single IP,
>>> this does not work out.  Is there a way to do this?  Or am I just wasting
> my
>>> time trying?  Thank you very much for any help that you can give.
>> 
>> I was thinking about how to overengineer this problem, and then realized it
>> is all possible using name-based virtual hosting.
>> 
>> There should be some documentation in the knowledgebase about how to set up
>> name-based virtual hosting.

So you actually have multiple physical servers?

I suppose it wouldn't be all that hard to do Apache Re-writes--fairly
similar to what Cobalt does for their /admin directory.

Take a look at the httpd.conf and search for /admin.

Basically you'll be able to rewrite to another *port* and the firewall
should be able to redirect that to a different internal IP.

-k