Opened 9 years ago
Last modified 9 years ago
#13678 new defect
Networking Still Works After Not Installing
| Reported by: | Pearson.S2 | Owned by: | |
|---|---|---|---|
| Component: | network/NAT | Version: | VirtualBox 4.3.20 |
| Keywords: | network NAT install installer | Cc: | |
| Guest type: | other | Host type: | other |
Description
During installation it's possible to opt out of installing VirtalBox's networking features. However, despite this, it's still possible for VMs to connect to the host's network via NAT under the networking tab within its settings.
For the purposes in which the VM is to be used, I don't want it to be possible for the user to connect to the network/internet in any shape or form. I have tried this on both the stable, and the test version of VirtualBox (4.3.21).
Note:
See TracTickets
for help on using tickets.
NAT doesn't need any custom network components and thus can't be globally disabled. NAT uses the host's normal IP functionality (socket interface, for TCP, UDP and to a limited amount ICMP, just enough to have ping support).
To me this sounds like the user simply should not use NAT networking mode, but only internal networking and/or host-only (or no network at all).
I see no bug in VirtualBox, but maybe you can give additional details which are convincing.