From owner-freebsd-current@FreeBSD.ORG  Tue Sep  6 15:36:15 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4424E16A41F;
	Tue,  6 Sep 2005 15:36:15 +0000 (GMT)
	(envelope-from tinguely@casselton.net)
Received: from casselton.net (casselton.net [63.165.140.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DA73B43D45;
	Tue,  6 Sep 2005 15:36:14 +0000 (GMT)
	(envelope-from tinguely@casselton.net)
Received: from casselton.net (localhost [127.0.0.1])
	by casselton.net (8.12.11/8.12.11) with ESMTP id j86FZlHX086190;
	Tue, 6 Sep 2005 10:35:47 -0500 (CDT)
	(envelope-from tinguely@casselton.net)
Received: (from tinguely@localhost)
	by casselton.net (8.12.11/8.12.11/Submit) id j86FZl8D086184;
	Tue, 6 Sep 2005 10:35:47 -0500 (CDT) (envelope-from tinguely)
Date: Tue, 6 Sep 2005 10:35:47 -0500 (CDT)
From: Mark Tinguely <tinguely@casselton.net>
Message-Id: <200509061535.j86FZl8D086184@casselton.net>
To: rwatson@freebsd.org, yar@comp.chem.msu.su
In-Reply-To: <20050906073438.GA64567@comp.chem.msu.su>
X-Spam-Status: No, score=1.4 required=5.0 tests=REPLY_TO_EMPTY autolearn=no 
	version=3.0.4
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on ccn.casselton.net
X-Mailman-Approved-At: Wed, 07 Sep 2005 11:22:14 +0000
Cc: freebsd-current@freebsd.org
Subject: Re: 6.0BETA3 panic in ip_output (vlan/RIP related?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2005 15:36:15 -0000


> So it sounds like we need to figure out how the multicast code should 
> behave on interface removal -- I wonder what other operating systems do 
> here?  Do they simply invalidate current membership related with the 
> interface, or do they leave the multicast sockets in a state such that if 
> the interface comes back, the memberships are re-bound?

In the case of a non-local multicast sessions, the saved multicast socket
state would need to keep a timestamp of the last a multicast router IGMP
session probe to detect the possibility of session pruning.

--Mark Tinguely.