Date: Thu, 05 Oct 2017 16:44:28 +0200 From: rainer@ultra-secure.de To: Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-net@freebsd.org, owner-freebsd-net@freebsd.org Subject: Re: lagg interface doesn't work Message-ID: <d848575a3638a20298274d82136b372b@ultra-secure.de> In-Reply-To: <59D6439B.6010000@grosbein.net> References: <F95A6802-8EC3-4027-8AA0-B38118F9A8D9@ultra-secure.de> <59D5E81A.5080700@grosbein.net> <90efe3d3524854f2a28e14f6496b8d88@ultra-secure.de> <59D5F317.8030104@grosbein.net> <436c7745802ce7ca9d196cccf600828a@ultra-secure.de> <59D621C9.1070704@grosbein.net> <9cc65618239aeb15abe707e9734b493a@ultra-secure.de> <59D626EB.50006@grosbein.net> <90c8f62dfa88a6ade5265fed68473a6e@ultra-secure.de> <59D6439B.6010000@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> This shows that systems sends outgoing LACP multicast ethernet frames > just fine, > but NIC chip does not deliver incoming multicast frames (unless > switched to promisc. mode). > > It may be possible that non-LACP and non-lagg configuration affected > too, > like multicast-based protocols OSPF, RIPv2 or even IPv6 that relies on > multicast heavily. > > SomeOne(TM) with real bxe hardware in hands and code knowledge should > commit more tests... Maybe some admin of bugzilla can assign the above mentioned bug to authors of the driver? How does one contact them?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d848575a3638a20298274d82136b372b>