Opened 7 years ago
Last modified 7 years ago
#17022 closed defect
Host-only networking breaks if BridgedInterface is listed under DisabledModes — at Version 2
| Reported by: | Prolixium | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.26 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description (last modified by )
When switching between networking modes on a VM, VBoxManage will apparently store the previous modes under the <DisabledModes> tag in the .vbox file. I recently ran into a situation where the BridgedInterface mode was still being erroneously applied even though it was listed under DisabledModes and caused host-only networking to break (unidirectional connectivity). This required me to manually edit the .vbox file and remove the BridgeInterface line from DisabledModes.
For example, the following prevents all packets from guest -> host:
<Adapter slot="2" enabled="true" MACAddress="0002BC56CB29" cable="true" promiscuousModePolicy="AllowAll" type="virtio">
<DisabledModes>
<BridgedInterface name="tap0"/>
<InternalNetwork name="intnet"/>
<NATNetwork name="NatNetwork"/>
</DisabledModes>
<HostOnlyInterface name="vboxnet1"/>
</Adapter>
Removing the <BridgedInterface name="tap0"/> line under DisabledModes allows host-only networking to work correctly.
It seems some items under DisabledModes are still processed, which sounds like a bug.
Change History (2)
comment:1 by , 7 years ago
comment:2 by , 7 years ago
| Description: | modified (diff) |
|---|


Some additional information about the setup is available here:
https://www.prolixium.com/blog?id=1029