From owner-freebsd-multimedia Fri Feb 27 23:25:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05408 for freebsd-multimedia-outgoing; Fri, 27 Feb 1998 23:25:59 -0800 (PST) (envelope-from owner-freebsd-multimedia@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA05393 for ; Fri, 27 Feb 1998 23:25:48 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id GAA17253; Sat, 28 Feb 1998 06:52:55 +0100 From: Luigi Rizzo Message-Id: <199802280552.GAA17253@labinfo.iet.unipi.it> Subject: Re: private mbone setup? To: brian@worldcontrol.com Date: Sat, 28 Feb 1998 06:52:54 +0100 (MET) Cc: freebsd-multimedia@FreeBSD.ORG In-Reply-To: <19980227191951.A632@top.worldcontrol.com> from "brian@worldcontrol.com" at Feb 27, 98 07:19:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'd like to setup a private mbone, or basically I would like to > do the following: > > run vic on one computers and record the session on another using > mbone_vcr. I think I've got everything setup right however > the sessions I create on sdr are not appearing on the sdr > running on the other computer. somebody suggested using route add 224.0.0.0 -netmask 0xf0000000 -interface {de0|ed0|lo0|tun0} where you put the right name for the interface to use for multicast traffic. remember that sdr annountcements are sent every so often (not sure about the rate) so it might take some time if you miss one to see the next one. A better way to test things is just to start a vic sender and receiver on known addresses and see if packets get through. another thing to keep in mind is the behaviour of the mbone tools when a send/sendto fails: in some cases (e.g. vic and vat) a permanent error status was retained on the socket preventing further sends. Bill Fenner has both a kernel patch (since the problem is there) and application patches to fix this problem. You should check what happens on other tools such as sdr. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message