From owner-freebsd-questions Mon Feb 3 5:53:47 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0624837B401 for ; Mon, 3 Feb 2003 05:53:47 -0800 (PST) Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F88343F43 for ; Mon, 3 Feb 2003 05:53:46 -0800 (PST) (envelope-from tinguely@web.cs.ndsu.nodak.edu) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id h13DrjY56412; Mon, 3 Feb 2003 07:53:45 -0600 (CST) (envelope-from tinguely) Date: Mon, 3 Feb 2003 07:53:45 -0600 (CST) From: mark tinguely Message-Id: <200302031353.h13DrjY56412@web.cs.ndsu.nodak.edu> To: freebsd-questions@FreeBSD.ORG, lamontfung@yahoo.com Subject: Re: mrouted configuration question In-Reply-To: <20030131180206.79248.qmail@web13501.mail.yahoo.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sounds like you want to enable the "noflood" option in the mrouted.conf. Flooding session data will speed up the starting/restarting the multicast connection at the expense of bandwidth. The next thing I would suggest is to dump the internal routing and cache tables on both multicast routers to see if there is any strange subscriptions on the network that has the switch. --Mark Tinguely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message