lagg interface doesn't work

[rainer at ultra-secure.de]

Am 2017-10-05 10:53, schrieb Eugene Grosbein:
> On 05.10.2017 15:36, rainer at ultra-secure.de wrote:
> 
>>> Promiscuous mode may disable hardware vlan processing and switch to
>>> software processing temporary.
>>> It seems bxe(4) driver may have issues with hardware vlan processing.
>>> Please show output of "ifconfig bxe0" command.
>> 
>> 
>> bxe0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> 
>> metric
>> 0 mtu 9170
>> 	options=527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
>> 	ether 2c:44:fd:8e:0a:68
>> 	hwaddr 2c:44:fd:8e:0a:68
>> 	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>> 	media: Ethernet autoselect (10Gbase-SR <full-duplex>)
>> 	status: active
>> 
>> 
>>> You should try to disable hardware vlan processing with "ifconfig 
>>> bxe0
>>> -vlanhwtag" and repeat your tests.
>>> If it helps, you could replace ifconfig_bxe0="up" with
>>> ifconfig_bxe0="-vlanhwtag"
>>> as temporary workaround and raise a problem report against bxe(4)
>>> driver.
>> 
>> 
>> (server-prod </root>) 0 # ifconfig bxe0 -vlanhwtag
>> ifconfig: -vlanhwtag: Invalid argument
> 
> It seems bxe(4) driver does not allow voluntary disable of vlanhwtag.
> Anyway, your problem seems to be hardware-dependent as lagg/LACP works 
> just
> fine with Intel cards, for example.

Indeed:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606



D'oh.

Not sure if we've got an Intel 10G card somewhere.