From owner-freebsd-net@FreeBSD.ORG Tue Jan 15 09:59:25 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE56916A417; Tue, 15 Jan 2008 09:59:25 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog13.obsmtp.com (s200aog13.obsmtp.com [207.126.144.127]) by mx1.freebsd.org (Postfix) with SMTP id DED8813C457; Tue, 15 Jan 2008 09:59:24 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([217.206.187.80]) by eu1sys200aob013.postini.com ([207.126.147.11]) with SMTP; Tue, 15 Jan 2008 09:59:23 UTC Received: from bill.mintel.co.uk (bill.mintel.co.uk [10.0.0.89]) by rodney.mintel.co.uk (Postfix) with ESMTP id 68C5218141E; Tue, 15 Jan 2008 09:59:23 +0000 (GMT) Message-ID: <478C83FA.7070907@tomjudge.com> Date: Tue, 15 Jan 2008 09:59:22 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: "Bruce M. Simpson" References: <478B7AB7.5010208@tomjudge.com> <478B88EE.7090307@FreeBSD.org> <478B9020.3000402@tomjudge.com> <478B982B.304@FreeBSD.org> <478BAC60.9030506@tomjudge.com> <478BAE70.9050702@FreeBSD.org> In-Reply-To: <478BAE70.9050702@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: Programming interface MAC filter without enabling PROMISC on an interface from user space. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2008 09:59:25 -0000 Bruce M. Simpson wrote: > Tom Judge wrote: >> Personally I can't see why this approach would be a problem, but I am >> not a expert. The address is defined in IEEE Std 802.1D-2004 as to >> not be forwarded by bridges (which I interpret as it being link local >> in a sense as switches/bridges are not allowed to forward the frame), >> so I can't see it being a problem registered on multiple interfaces. > > SIOCADDMULTI memberships are specific to the interface you request them > on. I can't speak for the bridging code -- I don't think it does any > special handling of multicast frames, however I'm not sure if it's smart > enough not to forward this group. Like IN_LOCALGROUP() it might need its > own 'don't forward this' clause. > Just for the record it seems that if_bridge replaces the destination MAC of a Ethernet multicast packet with its own MAC therefore making sure that the packets are not forwarded. Andrew can you confirm this assumption? (Based on sys/net/if_bridge.c lines 2011-2018 on RELENG_6_2) Tom