i used "server interface" in types of network settings, in virtualbox, vm properties, then, vm took the ip from dhcp in network, just as the host machine did.
On Thu, Mar 26, 2009 at 5:20 AM, Jordan Brown <[email protected]> wrote: > I am not yet entirely sure how I want to connect my VMs to the outside > world, but it seems like two variations that would be interesting, but > are not trivial to achieve, would be: > > 1) NAT connecting an "internal net" to the outside. This would be kind > of a combination of the "NAT" setting and the "Internal Network" > setting, where N virtual machines would all be on the same virtual > network, using private IP addresses, with a NAT connection to the > outside world. > > 2) Router connecting an "internal net" to the outside. Sort of a > combination of "host interface" and "Internal Network". N virtual > machines would be connected to the same virtual subnet, using public IP > addresses, with a virtual router connecting that network to the outside > world. > > It seems like you can do these by having a VM act as a router or NAT - > that is, it would have one interface set to "Host Interface" or "NAT", > and the other set to "Internal Network", running some sort of routing or > NAT software in the VM. That seems pretty heavyweight, though - it > seems like VirtualBox should supply this sort of virtual network > infrastructure. > > Is there some combination that I'm missing that would allow these two > configurations to be created easily? > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users > _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
