Timeline for Bridged vs. NAT: a Virtualbox and VMWare Comparison
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 20, 2011 at 18:20 | comment | added | David Spillett | IIRC under VMWare in NAT mode, VMs that are using the same interface can see each other. In host-only mode a VM will only see the host directly though the host could still perform routing/NAT so the VM can access anything the host allows it to (it just defaults to only being able to see the host and nothing else). From your description is sounds like VB uses "NAT network" to mean something like what VMWare calls "host only". I generally use bridged for everything in my environments anyway, so I may not be remembering accurately. In either case 10.x.x.x is as valid as 192.168.x.x. | |
| Jun 20, 2011 at 16:58 | comment | added | sinni800 | "The 10.10.2.x range is only visible to virtualbox and the VMs it is running with a NATed network adaptor." tell me if I understood it wrong, but if every VM is in that virtual network, they could connect to each other, which is not possible in NAT mode. This is possible in "Host Network" mode. | |
| Jun 20, 2011 at 16:52 | history | answered | David Spillett | CC BY-SA 3.0 |