#15061 closed defect (worksforme)
NAT DHCP is broken in vbox 5.0.X on OSX ALL VMs get an IP of 10.0.2.15 !
| Reported by: | clive darra | Owned by: | |
|---|---|---|---|
| Component: | network/NAT | Version: | VirtualBox 5.0.12 |
| Keywords: | nat, dhcp, | Cc: | |
| Guest type: | Linux | Host type: | Mac OS X |
Description
NAT DHCP is broken in vbox 5.0.X on OSX ALL VMs get an IP of 10.0.2.15 so you cant run more than one at once affects linux and windows guests
Change History (5)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
If you are using "NAT" as network attachment then this behavior is completely normal. Each VM has it's own NAT engine. So running several VMs in parallel is possible but the VMs will not be able to communicate. If you want to have several VMs behind one NAT engine then you need to use the network attachment "NAT network".
Closing as "works for me".
comment:3 by , 9 years ago
i see so vbox builtin NAT network functionality has changed completely from 4.x to 5.x it would be nice if this was documented somewhere
comment:4 by , 9 years ago
NAT networks were introduced with VBox 4.3.x. This network attachment mode is mentioned in section 6.2 and in section 6.4 of the user manual.
comment:5 by , 9 years ago
sorry my fault for not noticing massive change in functionality in virtualbox in 4.3 i normally use vmware and only rarely use virtualbox and mistakenly thought it worked the same
see also https://www.virtualbox.org/ticket/14987