ixl - VLAN tagging does not work

nbari

Hi, probably this is related to https://redmine.pfsense.org/issues/13381,

The card with problems:

ixl0@pci0:1:0:0:        class=0x020000 rev=0x02 hdr=0x00 vendor=0x8086 device=0x1572 subvendor=0x8086 subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Controller X710 for 10GbE SFP+'
    class      = network
    subclass   = ethernet

To test my settings I used instead an em0: (worked as expected)

em0@pci0:0:31:6:        class=0x020000 rev=0x00 hdr=0x00 vendor=0x8086 device=0x0d4d subvendor=0x1462 subdevice=0x7c81
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Connection (11) I219-V'
    class      = network

I create the vlan in PFSENSE, then for testing, Iam using vm-bhyve, and creating a switch with:

vm switch create -i ixl1.20 public

(this will use the existing interface with VTAG 20)

The created bridge is something like this:

vm-public: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 0e:2a:af:57:cc:0c
        id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
        member: tap3 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 28 priority 128 path cost 2000000
        member: tap2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 27 priority 128 path cost 2000000
        member: tap1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 26 priority 128 path cost 2000000
        member: ixl1.20 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 17 priority 128 path cost 2000
        groups: bridge vm-switch viid-4c918@
        nd6 options=1<PERFORMNUD>

What I notice is that all traffic flows as if it were not tagged, I can ping the pfsense router but not any of the other hosts from the VLAN network, if instead, I use an em0 interface, with the same configuration:

vm switch create -i em0.20 public

This worked as expected.

Is there something I could probably do to support better covering the bug?