Setting up a remote test environment correctly

Question

My setup:

- Main Box (connected to network)
  - VM1 : Linux
  - VM2 : Windows 7

Both the VMs are running off VM Player and using Bridged: connected directly to the physical network and replicating the physical network state. The user will connect to the Windows 7 box via a remote application like LogMeIn then have access to the Linux box as well via the Windows box to development testing.

This however would in turn give them direct access to my personal inside network as well if I am right. Is there a way to set this up and prevent that?

Answer 1

If we treat this like a networking problem, one solution could be as follows;

    internet
       |
   adsl_router
       |
    -------------------------------
    |              |              |  
firewall      dirty_host_a   dirty_host_b
    |
    |
    --------------------------------------
    |                  |                 |
clean_host_a      clean_host_b      clean_host_c

In order for your clean network to remain safe;

• Forward whatever ports you like on the router nat to your dirty hosts.
• Configure your firewall to disallow all inbound connections.
• Configure your firewall to only allow administration from the LAN side.

The 'firewall' node could be an actual hardware firewall, like a netgear FVS338, or a linux machine with two network interfaces, coupled with a switch and running iptables. Whatever you have lying around.

Answer 2

Change the vmplayer networking type to NAT, Firewall on the virtual server to prevent outgoing external connections from the VMs, except to LogMeIn and the other vm.

I, personally, like the VirtualBox networking better. 2 nics on the Win7 vm, one NATted, the other connected to an internal virtual network. 1 nic on the Linux vm connected to the internal virtual network. Firewall on the virtual server to prevent outgoing external connections (Except to LogMeIn).