memilanuk
November 27th, 2009, 12:47 PM
Hello,
I am running Virtualbox 3.0.12 with Windows Vista as the host OS and a handful of Linux distros as the guest machines. What I would like to do is create a virtual LAN where only *one* machine has actual 'direct' access to the real network (that the host is on).
I was envisioning something where my existing physical LAN would become 'the Internet', and the virtual machine acting as a gateway with two NICs would be the connection between the physical LAN and the internal virtual LAN. The object here is to get some experience setting up and running various services on the virtual gateway machine (firewall, proxy, port forwarding, port knocker, VPN, etc.) and then do other interesting things with the guest machines inside the virtual LAN.
So... the first machine would be the gateway machine, with two NICs: the first one I was thinking of using a bridged connection vs. a NAT connection, so that it can access the real world network but also be reachable (i.e. offer services to) from the physical LAN. The second one, the 'inward facing' NIC is where I'm a little less confident of what I want/need. I've been looking at the Virtualbox manual and at the article here (http://www.dedoimedo.com/computers/virtualbox-network-sharing.html) and I'm still not entirely sure of the difference between 'host only' and 'internal network' for this application.
If anyone has any tips or suggestions, I'm open. In the mean time I'll keep reading & searching... ):P
Thanks,
Monte
I am running Virtualbox 3.0.12 with Windows Vista as the host OS and a handful of Linux distros as the guest machines. What I would like to do is create a virtual LAN where only *one* machine has actual 'direct' access to the real network (that the host is on).
I was envisioning something where my existing physical LAN would become 'the Internet', and the virtual machine acting as a gateway with two NICs would be the connection between the physical LAN and the internal virtual LAN. The object here is to get some experience setting up and running various services on the virtual gateway machine (firewall, proxy, port forwarding, port knocker, VPN, etc.) and then do other interesting things with the guest machines inside the virtual LAN.
So... the first machine would be the gateway machine, with two NICs: the first one I was thinking of using a bridged connection vs. a NAT connection, so that it can access the real world network but also be reachable (i.e. offer services to) from the physical LAN. The second one, the 'inward facing' NIC is where I'm a little less confident of what I want/need. I've been looking at the Virtualbox manual and at the article here (http://www.dedoimedo.com/computers/virtualbox-network-sharing.html) and I'm still not entirely sure of the difference between 'host only' and 'internal network' for this application.
If anyone has any tips or suggestions, I'm open. In the mean time I'll keep reading & searching... ):P
Thanks,
Monte