From owner-freebsd-current@FreeBSD.ORG Mon Jun 18 12:37:30 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 E76B116A400 for ; Mon, 18 Jun 2007 12:37:30 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id A7D0C13C45D for ; Mon, 18 Jun 2007 12:37:30 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l5ICbP5w018710; Mon, 18 Jun 2007 08:37:25 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Mon, 18 Jun 2007 08:37:25 -0400 (EDT) Date: Mon, 18 Jun 2007 08:37:25 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "Bruce M. Simpson" In-Reply-To: <46765CB9.9020105@incunabulum.net> Message-ID: References: <46765CB9.9020105@incunabulum.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ian FREISLICH , current@freebsd.org Subject: Re: Multicast problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen 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 12:37:31 -0000 On Mon, 18 Jun 2007, Bruce M. Simpson wrote: > > 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. What happens when you join a group without an interface (INADDR_ANY)? Assume there is no route for the multicast group. Does the new code select the interface that the default route is on? This is the behavior we expect to see and what occurs on other OSs. -- DE