VMWare vmxnet3 drivers and VLANs...

[Martinezio]

Hi

I saw last time, that there is some issue with VLANs using VMXNET3 network interface.
Only the first created VLAN is working. Next vlan's aren't detected at all, even after reboots.
Hardware offload is disabled.

For now, I've bypassed this by creating physical interfaces instead, but this is not the way I want, because I can't add new network interfaces on-line to OpnSense and adding them offline can destroy all previous network assignements.
I know, that I can use E1000E adapter type, but this limits the traffic to 1Gbps.

What is current status of vmxnet3 drivers for OpnSense? Is there any work in progress for them?
Thanks in advance for any reply

[sorano]

I'm using VMXNET3 and multiple vlans in OPNsense just fine.

Can create new vlan interfaces while the hosts still are up without issues.

[Martinezio]

What's Your vswitch settings for this interface? Do You pass all vlans to this VM?

I can create vlans as well, but they do not pass any traffic over that vlan. Only the first created one is working. None of later created are passing the traffic: I can't ping this interface from other hosts using same vlan. Even after reboot.

I have ESXi 6.7 for this hypervisor, if that matters... But I have other setup, where is the same hypervisor version, the OpnSense machine have E1000E interface and VLANs are working fine...

[Patrick M. Hausen]

Have you allowed promiscuous mode for that vSwitch/portgroup/VM? I don't know from the top of my head at which level that setting can be found.

[Martinezio]

Have this settings:

Properties
    Network label    vpnHubTrunk
    VLAN ID    All (4095)

Security
    Promiscuous mode    Accept
    MAC address changes    Accept
    Forged transmits    Accept

Traffic shaping
    Average bandwidth    --
    Peak bandwidth    --
    Burst size    --

Teaming and failover
    Load balancing    Route based on IP hash 

vSwitch have 3 bonded interfaces to Cisco switch (C2690) as etherchannel.