virtualbox.org

Hey guys, ive got this issue im trying to resolve. Im used to the world of VMware where almost everything is done automatically.

Im trying to get a private network set up with VirtualBox to do some GPO and Active Directory testing but i dont want any of this traffic to go out to the rest of my network. I still want to be able to use access the Internet though.

I was thinking of doing it this way... i use the "Host Interface" option and instead of using the IP address that is being assigned by default which is something in the range of 10.2.3... (which is what my Host OS is currently assigned) i want to assign DHCP address in a different range all together (like 192.168.1...)

I just moved a NAT VM from 2.0.6 to 2.1.0. I just went to settings and selected "host interface" and booted it. The VM came up and acquired its address from my ADSL router -- just as easy as VMware.

Yea, im able to do that also. Works just fine, but i dont want IPs handed out by the router/gateway... i want to be able to assign different IPs in a different range and bridge them to my host so the guests can get to the internet.

One way to achive something like what I think you want.

Give each guest two interfaces. One is a host interface and gets its ip from your router and one with type "Internal network" which just connects the guests securely. One of the guests must run a dhcp server on this interface. Does that fit the bill ?

Hmm...sounds good, but what do u mean by DHCP server, like an instance of MS server with DHCP roles ?

Yes that's one of the possibles.

Scooby006 wrote:Yea, I'm able to do that also. Works just fine, but I don't want IPs handed out by the router/gateway... I want to be able to assign different IPs in a different range and bridge them to my host so the guests can get to the internet.

Most current routers have a configuration page for their DHCP function where you can lock individual MAC addresses to specific IP addresses. I use this as a matter of course for all of the PCs and devices which offer services because its a pain to have these addresses flipping. This gives the the ability to fix IP addresses but at a central location. Some routers have a build in DNS which automatically creates a private domain (e.g. home) so that you can use domain addressing to this as well. I just use fixed MAC addresses for my VMs and dish out addresses the same way. This has the nice side effect that is I move a VM from one machine to another the IP address, etc., stays the same.

I am not sure what you mean by "bridge them to my host so the guests can get to the internet" since the VBox driver effectively bridges the guests. They can get to the Internet just like any physical PC. The router doesn't see then as any different from a physical PC. Yes you can use other devices / PCs as a DHCP server, but if this is an "always on" device then you do get into problems. I keep this all simple, stupid.