Opened 9 years ago
#15343 new defect
Internal networking remark on same UID policy is misleading
| Reported by: | wodny | Owned by: | |
|---|---|---|---|
| Component: | documentation | Version: | VirtualBox 5.0.18 |
| Keywords: | intnet network host-only | Cc: | |
| Guest type: | other | Host type: | other |
Description
The User Manual states that "As a security measure, the Linux implementation of internal networking only allows VMs running under the same user ID to establish an internal network". This would be correct if the sentence ended with "(by default)".
Current wording suggests that if I wanted to create two VMs using two UIDs I would have to use e.g. a host-only interface instead. This requires more work, e.g. configuring a firewall so the traffic is allowed only between those two VMs.
It seems that "internal networking" interfaces work the same as "host-only" interfaces used to. Anyone who tried to share a vboxnet interface in older versions of VirtualBox had to use RestictAccess=0. Apparently the same works for "internal networking" interfaces. Both types are managed by the same parts of code and show up in logs as "intnet" interfaces so maybe it's not that surprising.
So even if authors do not want to write about RestrictAccess and AccessPolicy settings the manual should at least suggest there is a possibility of creating a shared "internal networking" interface.
