This appears to be a good situation for reverse proxying. The proxy can
behave as a single web server, while mapping to different servers inside
a firewall. Access control may also be applied at the proxy server,
since the controls are applied after name translation.
Of course, the usual constraints may be applied to the firewall so that
only the proxy server can access the content servers internally.
> Here's my problem. I have Gauntlet installed with three web servers behind
> it. The web servers are very light usage/testbeds and the machines they're
> on are used for other things. It's not practical to move the web servers
> outside of the firewall and the network behind the the firewall has private
> (non-routable) IP addresses. Is there any way to get to the three
> different web servers through the firewall?
>
> I thought of running a web server on the firewall with an initial page that
> pointed to the other webservers, but that was rejected by managment.
>
> If it were just one web server I could just plug port 80. If they ran at
> different ports I could plug different ports--but they don't.
>
> I was thinking that perhaps I could assign multiple IP address to the
> outside interface of the firewall, give the firewall different aliases with
> different IP addresses and somehow run different instances of plug-gw based
> on which IP address was connected to. It's the "somehow" part that I'm
> having trouble with.
>
> Any ideas?
> ---
> christopher michael*rms business systems*<cm @
rmsbus .
com>
--
Mike J Oropeza
--------------------------------
Those who hear not the music, think the dancers mad ~{';'}~
References:
|
|
