Date: Tue, 6 Sep 2005 17:00:31 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Mark Tinguely <tinguely@casselton.net> Cc: yar@comp.chem.msu.su, freebsd-current@freebsd.org Subject: Re: 6.0BETA3 panic in ip_output (vlan/RIP related?) Message-ID: <20050906165955.S78038@fledge.watson.org> In-Reply-To: <200509061535.j86FZl8D086184@casselton.net> References: <200509061535.j86FZl8D086184@casselton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 6 Sep 2005, Mark Tinguely wrote: >> 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. I was assuming that, at the very least, it would be necessary to issue a new IGMP join when binding the socket to a new interface... Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050906165955.S78038>