Johann,

Right, DNS will not really work since port forwarding is one to one
mapping, and not one to many. You will still be hitting the same ip
address on the internal natted IP.

Rafael already mentioned squid/apache as reverse proxy role. That is
one solution. Another alternative is to use a poor man's ala VPN,
underrated socks support on newer ssh.

On the remote site, configure:
router: public ip to NAT on ssh ip address port 22
server: configured ssh server. optional: DNS server

On the client side:
ssh client(with -D argument) + firefox(optionally, foxyproxy addons,
use socks5 option.)

on firefox, configure  socks support, and in the URL, just type:
http://remoteip_of_vm_1or http://remoteip_of_vm_2 and you are ready to
go.

Bonus:
  * since you are using ssh, end to end encryption is given to you for free.
  * https will work very well. Been doing this for a couple of years,
with my dokuwiki internally.
  * A good addons for firefox is foxyproxy. This can use DNS on the
remote server via socks(fixing the DNS socks leak), and can be
configured to access public internet and internal natted ip address
via socks seamlessly.
  * And you can extend it more. If you have a very good socks client,
you can tunnel RDP, vnc, UDP protocols, even act as wrapper to any
application which does not support socks in the first place.

regards,
Andre | http://www.varon.ca

On Tue, Jan 20, 2009 at 9:10 AM, Johann Vincent Paul Tagle
<[email protected]> wrote:
> On Tue, Jan 20, 2009 at 9:33 PM, jan gestre <[email protected]> wrote:
>>
>> Simplest solution would be to add each VM's hostname and ip address to
>> each server's /etc/hosts file.
>
> How does that make the webserver on the VM accessible from the Internet?
> Maybe I did not state my requirements clearly.  One machine with one public
> IP.  The VM's all have private addresses.  Previously each VM had specific
> services, e.g. only one had a webserver running so I just configured port
> forwarding on the host machine.  Now I need more than one VM with webserver
> and all webservers need to be accessible from the net.  That's why I think a
> squid/apache proxy or a LVS director might be what I need.
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph

Reply via email to