From owner-freebsd-net@FreeBSD.ORG  Thu Apr 17 08:56:00 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 129DF1065672;
	Thu, 17 Apr 2008 08:56:00 +0000 (UTC) (envelope-from bms@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 02C488FC17;
	Thu, 17 Apr 2008 08:56:00 +0000 (UTC) (envelope-from bms@FreeBSD.org)
Received: from freefall.freebsd.org (bms@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m3H8txa4094074;
	Thu, 17 Apr 2008 08:55:59 GMT
	(envelope-from bms@freefall.freebsd.org)
Received: (from bms@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m3H8twoK094070;
	Thu, 17 Apr 2008 08:55:58 GMT (envelope-from bms)
Date: Thu, 17 Apr 2008 08:55:58 GMT
Message-Id: <200804170855.m3H8twoK094070@freefall.freebsd.org>
To: 4pr@legis.krsn.ru, bms@FreeBSD.org, freebsd-net@FreeBSD.org
From: bms@FreeBSD.org
Cc: 
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2008 08:56:00 -0000

Synopsis: [multicast] FreeBSD 7 multicast routing problem

State-Changed-From-To: open->feedback
State-Changed-By: bms
State-Changed-When: Thu 17 Apr 2008 08:49:01 UTC
State-Changed-Why: 
The symptoms you describe do not sound like a multicast routing issue.
Given your description it sounds like the ethernet drivers are not
implementing ALLMULTI correctly.

If the ALLMULTI flag is appearing in the ifconfig output for the
interfaces involved, that is the correct behaviour.
The multicast forwarding code *requires* that the card supports ALLMULTI
correctly.

However ALLMULTI has historically been known not to work correctly with
certain network adapters, and in this case it could be a firmware issue.

For example I saw an issue with fxp last week whereby the card wouldn't
send multicast traffic unless the group had also been joined, which
violates POLA.

Can you ping Pyun YongHyeon and/or Jack Vogel about this? Both have
been working on the msk and em drivers recently so they can better
advise you about possible driver problems. Thanks.



http://www.freebsd.org/cgi/query-pr.cgi?pr=122839