TeeJayHoward
Limpness Supreme
- Joined
- Feb 8, 2005
- Messages
- 12,268
Imagine the following scenario: You're in charge of a small-medium sized network. Say, 4,000 users. You use the 10.x.x.x IP range. Certain blocks are reserved for certain things. For example, the 10.0.2.x range is used by the networking team. Obviously your DHCP server doesn't hand out IPs in that range. While browsing the DNS entries recently, you noticed that a lot of clients have IPs in the 10.0.2.x range. Confused, you track them down. They're all clients running VirtualBox.
Apparently, VirtualBox includes a built-in DHCP server when using NAT, which hands out IPs in the 10.0.2.x range for the first NIC, 10.0.3.x for the second, etc. This is creating an issue. If the clients switch to bridged networking, they use your DHCP server, and everything is gravy. Tracking down every user who is using VirtualBox and having them change their settings manually is a pain. Instead, you decide that there must be a way to prevent the VMs from talking to your network unless bridged networking is set up.
How would you go about doing that?
Apparently, VirtualBox includes a built-in DHCP server when using NAT, which hands out IPs in the 10.0.2.x range for the first NIC, 10.0.3.x for the second, etc. This is creating an issue. If the clients switch to bridged networking, they use your DHCP server, and everything is gravy. Tracking down every user who is using VirtualBox and having them change their settings manually is a pain. Instead, you decide that there must be a way to prevent the VMs from talking to your network unless bridged networking is set up.
How would you go about doing that?