From owner-freebsd-current@FreeBSD.ORG Mon Jul 2 11:34:48 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C6C5E16A485; Mon, 2 Jul 2007 11:34:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 9AB1513C469; Mon, 2 Jul 2007 11:34:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 2F30F59C6; Mon, 2 Jul 2007 07:34:48 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 02 Jul 2007 07:34:48 -0400 X-Sasl-enc: Aga3U1xcI5QU76Zo0wkCgGJc/07tEfiMHJP+f3yzcUcN 1183376087 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 67DE11A73; Mon, 2 Jul 2007 07:34:47 -0400 (EDT) Message-ID: <4688E2D6.8050608@FreeBSD.org> Date: Mon, 02 Jul 2007 12:34:46 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.4 (X11/20070630) MIME-Version: 1.0 To: Ian FREISLICH References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , Poul-Henning Kamp , current@freebsd.org Subject: Re: Multicast problems [PATCH] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2007 11:34:48 -0000 Ian FREISLICH wrote: >> Has there been any outcome here, ie. have folks who were seeing problems >> with multicast in the system tested this patch and found it to fix their >> problems? >> > > The quagga issue I have with the OSPF multicast address landing up > on the wrong interface remains. > Is Quagga still incorrectly using 0.0.0.0/8 to select a multicast source interface by index? If so this is a Quagga issue and needs to be fixed there, not in the kernel, as this behaviour has now been deprecated and should not have been relied on. Quagga will have to be patched to explicitly select an interface using the appropriate ioctls (see my routed patches). If not, this is a separate issue and will need to be analysed as such. Was the need for a 224/4 route resolved by my patch? If so I will commit it -- this is the issue the patch was intended to fix. regards, BMS