Bug #3182: VMware vmxnet interfaces are not detected as VLAN capable - pfSense - pfSense bugtracker

Actions

Copy link

Bug #3182

closed

VMware vmxnet interfaces are not detected as VLAN capable

Added by Jim Pingle over 10 years ago. Updated over 9 years ago.

Status:

Resolved

Priority:

Low

Assignee:

Ermal Luçi

Category:

Interfaces

Target version:

2.2

Start date:

09/04/2013

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.1

Affected Architecture:

All

Description

A VMware vmxnet interface, e.g. vxn0 is capable of using VLANs with a reduced MTU, but they do not appear in the list of VLAN parent interfaces.

This is probably due to the fact that "ifconfig vxn0 list caps" returns an error, which may be related to how the data is polled from the NIC, and thus it fails the test that checks what the NIC is capable of handling.

If the test is bypassed and the VLAN added to the NIC, it does configure and pass traffic and generally work as expected.

Actions

Copy link

Updated by Ermal Luçi over 10 years ago

From what i see the driver has proper flags defined.
The code of fetching the capabilities is generic.

Probably there is something more going here that needs to be checked.

Actions

Copy link

Updated by Phil Jaenke about 10 years ago

ifconfig list caps shouldn't be used any longer. Case in point, also doesn't work for em(4) on 10.0-RELEASE. Should change to instead use ifconfig -m $interface and parse the capabilities.

vmx(4) uses VGT though, so will return "SIOCGVH: Protocol not supported" if the desired VLAN is not present on the host. (This is by design.) So if you want to use VLAN 20 as an example it must also exist on the vSwitch and the relevant interface must also be mapped correctly. So SIOCGVH should not be used as a reliable test.

Other than those two points, this has appears to have been fixed upstream for vmx(4):

: ifconfig -m vmx0
vmx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=61039b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6>
capabilities=61079b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,TSO6,LRO,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6>

vmx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=61039b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6>
        ether 00:0c:29:e7:71:7b
        inet6 fe80::20c:29ff:fee7:717b%vmx0 prefixlen 64 scopeid 0x3
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
vmx0_vlan20: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 00:0c:29:e7:71:7b
        inet6 fe80::20c:29ff:fee7:717b%vmx0_vlan20 prefixlen 64 scopeid 0x8
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
        vlan: 20 vlanpcp: 0 parent interface: vmx0

Actions

Copy link