On Tue, 1 Jun 2004, Suraj wrote:
- R Deepak wrote on Tue, Jun 01, 2004 at 07:08:15PM +0530:
- | I think the problem is that what internal host the client needs to
- | connect to will be decided based on the link the user clicks in
- | his/her browser.
- | You cannot do it at the firewall in this case I think. Especially if
- | you have multiple internal 10.x.x.x hosts that are being used.
- no no... to the client it will still seem like its connecting to the
- external machine. However, the external machine wont handle the
- request, it will simply forward the request (at the TCP level) to the
- 10.x machine. and similarly the response from the 10.x will go to the
- external machine and _then_ to the client (so yes, this also needs to
- be setup while doing port forwarding). If you read up on port
- forwarding all of this will be clear to you :)
I do understand what port forwarding is. :)
external machine runs the webserver. And a link in a doc there points to a
doc on another machine that has a 10.x.x.x IP. This is the problem right?
I do not think the initial poster had round robin port forwarding in mind.
Maybe he can clarify.