Date: Thu, 5 Oct 2017 15:53:43 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: rainer@ultra-secure.de Cc: freebsd-net@freebsd.org Subject: Re: lagg interface doesn't work Message-ID: <59D5F317.8030104@grosbein.net> In-Reply-To: <90efe3d3524854f2a28e14f6496b8d88@ultra-secure.de> References: <F95A6802-8EC3-4027-8AA0-B38118F9A8D9@ultra-secure.de> <59D5E81A.5080700@grosbein.net> <90efe3d3524854f2a28e14f6496b8d88@ultra-secure.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05.10.2017 15:36, rainer@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. Also, you have not specified FreeBSD version you use.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59D5F317.8030104>