From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 894 invoked by alias); 20 Jul 2007 19:44:42 -0000 Received: (qmail 886 invoked by uid 22791); 20 Jul 2007 19:44:42 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 20 Jul 2007 19:44:37 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IByOs-0008CO-8d for ecos-discuss@sources.redhat.com; Fri, 20 Jul 2007 21:44:30 +0200 Received: from c-76-17-159-202.hsd1.mn.comcast.net ([76.17.159.202]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Jul 2007 21:44:30 +0200 Received: from grante by c-76-17-159-202.hsd1.mn.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 20 Jul 2007 21:44:30 +0200 To: ecos-discuss@sources.redhat.com From: Grant Edwards Date: Fri, 20 Jul 2007 19:44:00 -0000 Message-ID: References: <20070708185139.GE24630@lunn.ch> <20070709083403.GL24630@lunn.ch> <20070717160027.GA6777@lunn.ch> <20070720192200.GA28161@lunn.ch> User-Agent: slrn/0.9.8.1 (Linux) X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: Multi-cast support in Ethernet drivers X-SW-Source: 2007-07/txt/msg00163.txt.bz2 On 2007-07-20, Andrew Lunn wrote: > On Thu, Jul 19, 2007 at 02:42:45PM +0400, Alexander Aganichev wrote: >> On 7/17/07, Andrew Lunn wrote: >>> > The stack sets up multi-cast MAC to 01:00:5e:00:00:01 and cannot talk >>> > to my DHCP anymore. >>> >>> My first guess is that you are programming the filter incorrectly in >>> your MAC chip. It could be you are blocking the broadcast address, or >>> the unicast address for your device. Is the DHCP server broadcasting >>> is response, or unicasting it? >> >> Shouldn't the upper layer provide broadcast address in the >> list to ETH_DRV_SET_MC_LIST if it wants to receive broadcast >> packets? I've never seen that behavior. >> My guess it is upper layer responsibility to do so, because of >> otherwise I do not see any sense for that call... I think it's there to allow multiple unicast addresses to be used. However, none of the drivers I've looked at implement that. > No, i would expect the default is that the upper layer expects > the device to always receive broadcast. Based on the Ethernet drivers I've worked on, that certainly seems to be the case. > However maybe your device does not? If the Ethernet driver didn't pass on to the stack received broadcast packetsARP wouldn't work, and you couldn't even ping the device. > It is at least something to test. Maybe take a look at the > Linux driver and see what it does for its multicast call. You > cannot directly use the code, since it is GPL, but you can > look and see if it does anything interesting. -- Grant Edwards grante Yow! at BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI-BI- visi.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss