Changes between Initial Version and Version 2 of Ticket #17022
- Timestamp:
- Aug 20, 2017 4:04:09 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17022 – Description
initial v2 1 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.1 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`. 2 2 3 3 For example, the following prevents all packets from guest -> host: 4 4 {{{ 5 5 <Adapter slot="2" enabled="true" MACAddress="0002BC56CB29" cable="true" promiscuousModePolicy="AllowAll" type="virtio"> 6 6 <DisabledModes> … … 11 11 <HostOnlyInterface name="vboxnet1"/> 12 12 </Adapter> 13 }}} 14 Removing the `<BridgedInterface name="tap0"/>` line under `DisabledModes` allows host-only networking to work correctly. 13 15 14 Removing the <BridgedInterface name="tap0"/> line under DisabledModes allows host-only networking to work correctly. 15 16 It seems some items under DisabledModes are still processed, which sounds like a bug. 16 It seems some items under `DisabledModes` are still processed, which sounds like a bug.
