you might consider setting up a DNS record privately that sends all requests to example.com to the internal ip.
On Sat, Nov 14, 2009 at 12:49 PM, Eduardo J. Ortega U. <[email protected]> wrote: > Hi: > > I have the setup show in http://imagebin.ca/view/L7Qut2Xn.html .eBox > has Firewall, DNS, transparent proxy and mail services. Server with IP > address 10.10.1.13 hosts a website that needs to be publicly > available. eBox DNS has a corresponding hostname, say www.example.com, > that resolves to the IP of interface eth0 - Web, and a corresponding > Port redirection rule forwarding everything directed to ebox TCP port > 80 on interface eth0 - Web to 10.10.1.13 port 80. This works without > issues. > > Now, the problem arises when a machine from the internal network, say > 10.10.1.220, needs to access the website at www.example.com. When the > address is entered on the browser, I get a connection refused error. I > also defined a redirection rule saying that anything coming from > interface eth1 - Interna to ebox TCP port 80 should be redirected to > 10.10.1.13. See http://imagebin.ca/view/BrO81knn.html > But the redirection does not work. > > Any hints? > > THanks. > > > -- > Eduardo J. Ortega U. > _______________________________________________ > ebox-user mailing list > [email protected] > http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user > -- Random quote of the week/month/whenever i get to updating it: "Quis custodiet ipsos custodes?": "who shall watch the watchers themselves?" - Juvenal _______________________________________________ ebox-user mailing list [email protected] http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user
