From owner-freebsd-net@FreeBSD.ORG Tue Nov 18 09:19:02 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05A2916A4CE for ; Tue, 18 Nov 2003 09:19:02 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA9643FBD for ; Tue, 18 Nov 2003 09:19:00 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.9p2/8.12.9) with ESMTP id hAIHJ0Tb029015 for ; Tue, 18 Nov 2003 12:19:00 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.9p2/8.12.9/Submit) id hAIHJ0m3029014 for freebsd-net@freebsd.org; Tue, 18 Nov 2003 12:19:00 -0500 (EST) (envelope-from barney) Date: Tue, 18 Nov 2003 12:19:00 -0500 From: Barney Wolff To: freebsd-net@freebsd.org Message-ID: <20031118171900.GA28864@pit.databus.com> References: <20031118130200.GA87978@saboteur.dek.spc.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031118130200.GA87978@saboteur.dek.spc.org> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.38 Subject: Re: Straw poll - All-interface broadcast/multicast X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 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, 18 Nov 2003 17:19:02 -0000 On Tue, Nov 18, 2003 at 01:02:00PM +0000, Bruce M Simpson wrote: > On the subject of hacking the network stack to output broadcast/multicast > datagrams on all appropriate interfaces:- > > Who would like a switch to do this in the kernel? > > Who would be happier with a userland convenience function to do it? > > Who would rather roll their own? > > I have a diff in the works to do this, 'just for the heck of it', but I am > very wary of putting anything in the stack 'just for the heck of it' as > the current IP_ONESBCAST workaround strikes me as 'good enough'. Some questions, because I'd like to be an educated voter. 1. How does multicast routing work now? Presumably something takes a mcast packet and sends it out to every interface behind which some host has indicated group membership. Is this kernel or userland? Does it work at all? 2. How is "appropriate" defined - by administrator choice or by some inherent property of the interface hardware type? 3. How do other OS's do it, if at all? 4. How will this interact with IPv6? IPsec? Thanks, Barney -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.