From owner-freebsd-bugs Sun Mar 23 00:59:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA29958 for bugs-outgoing; Sun, 23 Mar 1997 00:59:28 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA29951 for ; Sun, 23 Mar 1997 00:59:24 -0800 (PST) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15048(3)>; Sun, 23 Mar 1997 00:58:52 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177486>; Sun, 23 Mar 1997 00:58:46 -0800 To: Jun-ichiro Itoh cc: freebsd-bugs@freefall.freebsd.org Subject: Re: i386/3048: multicast support necessery in some drivers. In-reply-to: Your message of "Sat, 22 Mar 97 06:10:03 PST." <199703221410.GAA25631@freefall.freebsd.org> Date: Sun, 23 Mar 1997 00:58:35 PST From: Bill Fenner Message-Id: <97Mar23.005846pst.177486@crevenia.parc.xerox.com> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This patch will always keep the card in promiscuous mode. There is always at least one group membership (224.0.0.1) on any given interface. Doesn't FIL_GROUP mean "receive multicasts"? I was under the impression that the code in the driver didn't keep track of multicast membership because 3com cards don't have multicast group filters; their level of multicast granularity is "on" or "off". (This dates back from the days of VME boards for Sun3's... and they still haven't learned... sigh) Bill