From owner-freebsd-net Fri Aug 18 23:15:36 2000 Delivered-To: freebsd-net@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id A9F2B37B423 for ; Fri, 18 Aug 2000 23:15:30 -0700 (PDT) Received: from localhost (shuttle.sixyards.wide.toshiba.co.jp [3ffe:501:100f:0:200:f8ff:fe01:61cf]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id PAA16549; Sat, 19 Aug 2000 15:01:43 +0900 (JST) Date: Sat, 19 Aug 2000 15:11:09 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: gbnaidu@sasi.com Cc: freebsd-net@FreeBSD.ORG Subject: Re: multicast packets & tcpdump... In-Reply-To: In your message of "Sat, 19 Aug 2000 11:36:22 +0530 (IST)" References: User-Agent: Wanderlust/2.3.0 (Roam) Emacs/20.6 Mule/4.0 (HANANOEN) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 19 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> On Sat, 19 Aug 2000 11:36:22 +0530 (IST), >>>>> "G.B.Naidu" said: >> (however, I admit the current BSD's behavior is *worse* than one of >> linux. It simply allows normal user to send invalid packets to the >> wire.) > Any patches for this or is it just over looked? I think the latter is the case. It is easy to just prevent packets with multicast source addresses from being sent, but it is a bit harder to implement the same behavior as linux (i.e. choose another valid address). I'm not even sure if such a behavior is really "correct". JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message