From owner-freebsd-net@FreeBSD.ORG Tue Nov 18 05:02:17 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 1B99C16A4CE for ; Tue, 18 Nov 2003 05:02:17 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id F123043FBD for ; Tue, 18 Nov 2003 05:02:15 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id BFD09654C3 for ; Tue, 18 Nov 2003 13:02:14 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 45773-01-2 for ; Tue, 18 Nov 2003 13:02:14 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 41708654C2 for ; Tue, 18 Nov 2003 13:02:14 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id 685083C; Tue, 18 Nov 2003 13:02:01 +0000 (GMT) Date: Tue, 18 Nov 2003 13:02:00 +0000 From: Bruce M Simpson To: freebsd-net@freebsd.org Message-ID: <20031118130200.GA87978@saboteur.dek.spc.org> Mail-Followup-To: freebsd-net@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: 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 13:02:17 -0000 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'. BMS