id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host
17686,"A virtual machine with networking bridged to a vlan host interface, cannot communicate",AlexSmirnoff,,"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. 
",defect,closed,network,VirtualBox 5.2.6,invalid,,,all,Linux