On Wed, 2 Jun 2004, Suresh Krishna S wrote:
-
- On Tue, 1 Jun 2004, R Deepak wrote:
-
- > On Tue, 1 Jun 2004, Praveen wrote:
- >
- > - Suraj wrote:
- > -
- > - > Yes its possible. Port forwarding is what needs to be done.
- > -
- > - If I get your correct, I think what you talk about is a bi-directional
NAT.
- > -
- > - Assume, I am 61.11.75.244 and I want the to access a machine 10.1.1.1, I
- > - should have a bi-directional NAT say 168.192.1.1 having port 40000 mapped
to
- > - 10.1.1.1's port 80; now 61.11.75.244 should say the destination IP
address as
- > - 168.192.1.1 and destination port as 40000 to reach 10.1.1.1.
- >
- > Yes. This is how it should work. :)
-
-
- My setup is,
-
- Internet ---------> Machine A --------- Machine B
- (has global-IP) (has local IP, 10.x.x.x)
- dns.domain.com
- host1.domain.com
-
-
- Machine A -> running HTTP for domain.com, host1.domain.com
- Machine B -> running HTTP
-
- (web contents for host1.domain.com are uploaded in 10.x.x.x)
-
- The people from Internet should able to browse the web contents of
- Machin-B (ie URL : http://host1.domain.com).
-
- Yes, I can try with bi-directional NAT.
-
- Can it be done via VirtualHost, RedirectPermanent from the Machine-A
- httpd.conf.??
You cannot redirect an external machine to a 10.x.x.x address without port
forwarding. If you use RedirectPermanent, the external client will try to
connect to the 10.x.x.x address.
You will have to use redirect permanent to redirect the external client to
a different port on Machine A. And then map that port to port 80 on
10.x.x.x.
Regards
Deepak
