On 8/30/06, Michael Nolan <[email protected]> wrote:
> Situation in a nutshell:
>
> Production and test databases are on two separate systems inside the
> firewall. The web server is at an ISP, outside the firewall.
>
> The firewall sends all data coming from the ISP, port 5432 to a specific IP
> address inside the firewall: port 5432, which is the production serve.
>
> Test transactions need to go to the other server, which has to be the same
> IP address (the address of the firewall), so it needs to be a different
> port, but I'm not sure if the port translator in the firewall will do any
> better at getting a response that than a port translator on the test server
> does.
>
> However, I also need the test database responding to requests on port 5432.
Your firewall can probably redirect firewallhost:5431 to
insidehost:5432. If not, you could use something like simpleproxy on
insidehost to do what you want.
<http://sourceforge.net/projects/simpleproxy/>
-K
