From owner-freebsd-net@FreeBSD.ORG Fri Aug 22 00:11:47 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 F0DD916A4BF for ; Fri, 22 Aug 2003 00:11:46 -0700 (PDT) Received: from hysteria.spc.org (hysteria.spc.org [195.206.69.234]) by mx1.FreeBSD.org (Postfix) with SMTP id 8060343FAF for ; Fri, 22 Aug 2003 00:11:45 -0700 (PDT) (envelope-from bms@hysteria.spc.org) Received: (qmail 16084 invoked by uid 5013); 22 Aug 2003 07:08:44 -0000 Date: Fri, 22 Aug 2003 08:08:44 +0100 From: Bruce M Simpson To: Wes Peters Message-ID: <20030822070844.GF1417@spc.org> Mail-Followup-To: Bruce M Simpson , Wes Peters , freebsd-net@freebsd.org References: <20030821142201.GE1417@spc.org> <200308212235.03055.wes@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308212235.03055.wes@softweyr.com> User-Agent: Mutt/1.4.1i Organization: SPC cc: freebsd-net@freebsd.org Subject: Re: IP_ONESBCAST and upcoming RELENG_4_9 freeze 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: Fri, 22 Aug 2003 07:11:47 -0000 On Thu, Aug 21, 2003 at 10:35:03PM -0700, Wes Peters wrote: > Your change makes it so that broadcasts sent to 255.255.255.255 will > be transmitted on all interfaces marked with a ONES_BCAST flag, right? It really is a very simple addition. It's a protocol-level socket option, so doesn't interfere with the legacy behaviour unless processes specifically request it, but that's about the gist of it. It is an identical API to that documented by Stevens in "UNIX Network Programming" and present in BSD/OS from 4.x onwards. Ours is slightly more complete in that it will heed the option for a raw IP socket without IP_HDRINCL. It is less obfuscated due to our delayed checksumming than the BSD/OS code. > A nice solution to the problem; I was gonna hack it so such packets > were sent on all interfaces with IFF_BROADCAST. I like your solution > better. I'm happy to know that will be in 5.2 and I have PR or two > to assign over to you so you can close them. ;^) No problemo. Will do. BMS