Trying to learn something but not sure what to Google...

[jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org (Jarod Wilson)]

On Sun, Sep 12, 2010 at 11:36 PM, Edward Ned Harvey <blu-Z8efaSeK1ezqlBn2x/YWAg at public.gmane.org> wrote:
>> From: discuss-bounces-mNDKBlG2WHs at public.gmane.org [mailto:discuss-bounces-mNDKBlG2WHs at public.gmane.org] On
>> Behalf Of Jarod Wilson
>>
>> > You can't forward a single inbound IPaddress/port to two separate
>> > (and different) internal websites.

^ Note that there is no specific mention of NAT here. ^

>> Yes, actually, you can (been there, done that). However, it requires a
>> web server running on the gateway system, proxying them.
>
> I think that's what I said.  You can't NAT to two separate and different
> internal IP's & ports, but you can NAT to a single one, which then knows how
> to forward/redirect/proxy whatever page was requested.

See above. You said "You can't forward a single inbound IPaddress/port
to two separate (and different) internal websites." Yes, you can. No,
you can't NAT them, but you can certainly forward them, using a proxy
on the gateway. NAT is hardly the only way to get traffic passed from
outside to inside. Fine, so I'm being pedantic, but choose your words
carefully... ;)

> But the fact
> remains, this is still being handled by a single internal IP address and
> port, which is then choosing some other server(s) to use in reality.

Sure. And like I said, its possible to do this all from a gateway
system, but if the gateway isn't equipped to do proxying, then your
suggestion to NAT to one machine, and have it proxy to the other is a
viable solution as well.

-- 
Jarod Wilson
jarod-ajLrJawYSntWk0Htik3J/w at public.gmane.org