Opened 7 years ago
Closed 7 years ago
#17686 closed defect (invalid)
A virtual machine with networking bridged to a vlan host interface, cannot communicate
Reported by: | AlexSmirnoff | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 5.2.6 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Linux |
Description
Hi! I have a vlan interface named vlan100:
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 74:46:a0:90:c3:7d brd ff:ff:ff:ff:ff:ff 3: vlan100@eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 74:46:a0:90:c3:7d brd ff:ff:ff:ff:ff:ff inet 172.17.100.222/24 brd 172.17.100.255 scope global noprefixroute vlan100 valid_lft forever preferred_lft forever inet6 fe80::45a2:1264:44:3154/64 scope link noprefixroute valid_lft forever preferred_lft forever
And I want a virtual machine bridged to this interface:
<Network> <Adapter slot="0" enabled="true" MACAddress="0800276C0E92" type="82540EM"> <DisabledModes> <InternalNetwork name="intnet"/> <NATNetwork name="NatNetwork"/> </DisabledModes> <BridgedInterface name="vlan100"/> </Adapter> </Network>
In this case the virtual machine cannot communicate, because of packets going to virtual machine appears tagged. You can see it tagged in attached screenshot of tcpdump in virtual machine.
Attachments (1)
Change History (3)
by , 7 years ago
Attachment: | VirtualBox_Zulip_15_04_2018_14_05_08.png added |
---|
comment:1 by , 7 years ago
comment:2 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Please close this ticket. This issue is related to operating system configuration. Everything works as expected when I set flags NM_VLAN_FLAG_REORDER_HEADERS (0x1) and NM_VLAN_FLAG_LOOSE_BINDING (0x4) on vlan100 interface. Thank You.