From owner-freebsd-current@FreeBSD.ORG Mon Jun 18 10:41:43 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 BEDAF16A469 for ; Mon, 18 Jun 2007 10:41:43 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 9A67F13C4AD for ; Mon, 18 Jun 2007 10:41:43 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 9B176130E; Mon, 18 Jun 2007 06:21:56 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 18 Jun 2007 06:21:56 -0400 X-Sasl-enc: 6cKcAUDHS3oqRwPuvYVGxnSLLg2NwqY4q2H5Oihx+fmm 1182162116 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id A4F6D28C3; Mon, 18 Jun 2007 06:21:56 -0400 (EDT) Message-ID: <46765CB9.9020105@incunabulum.net> Date: Mon, 18 Jun 2007 11:21:45 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) 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: current@freebsd.org Subject: Re: Multicast problems 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, 18 Jun 2007 10:41:43 -0000 Ian FREISLICH wrote: > Hi > > I have a problem with quagga running on a CURRENT (15 June). It > appears that it's registering the multicast address on the wrong > interface. In fact, no matter which network I tell quagga to use > as the OSPF network, it always registers the multicast addresses > on the same incorrect vlan. It works with a May 24 kernel. > What is the format of the IP_ADD_MEMBERSHIP call used by the version of Quagga you are running to join the OSPF group? Does it use 'struct ip_mreqn' ? Does it use IP_ADD_SOURCE_MEMBERSHIP or IP_BLOCK_SOURCE ioctls? Other folks reported issues with the new code. As you're probably aware, ipv4 multicast group memberships must be bound to an interface. When they are not, the interface selected as the source for the IGMP join uses a routing table lookup on the group. The newer code changed to perform this lookup by interface index as well as by address, as interfaces used for ipv4 multicast traffic are generally assumed to have a protocol-level address. BMS