From owner-freebsd-multimedia Tue Feb 27 16:39:06 1996 Return-Path: owner-multimedia Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA28313 for multimedia-outgoing; Tue, 27 Feb 1996 16:39:06 -0800 (PST) Received: from homer27.u.washington.edu (junkins@homer27.u.washington.edu [140.142.77.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA28306 for ; Tue, 27 Feb 1996 16:39:05 -0800 (PST) Received: by homer27.u.washington.edu (5.65+UW96.02/UW-NDC Revision: 2.33 ) id AA63251; Tue, 27 Feb 96 16:38:34 -0800 X-Sender: junkins@homer27.u.washington.edu Date: Tue, 27 Feb 1996 16:38:33 -0800 (PST) From: "D. Junkins" To: "Jordan K. Hubbard" Cc: multimedia@freebsd.org Subject: Re: Seeking advice on mrouted configuration.. In-Reply-To: <14046.825455087@time.cdrom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-multimedia@freebsd.org Precedence: bulk >From a traceroute it looks like you are using 192.216.222.2 (with a name jkh-sl.cdrom.com) for the slip interface on whisker. Freefall and who are also on network 192.216.222/28. This means that your slip link on freefall is also on the same network (192.216.222/28). Mrouted may not be able to handle routing information out an interface on the same subnet the way unicast routing can. I can think of two solutions for this problem: 1) Renumber the slip link to be on the same IP network as time and whisker instead of freefall and who. 2) Run mrouted on either time or whisker and setup a tunnel from mrouted running on who or freefall. I don't know what other circumstances may be keeping you from renumbering the slip link, but it is probably a more attractive solution since you loose the extra 20 bytes/packet overhead of a second IP header when you tunnel over an already slow slip link. - Doug +------------------------------+------------------------------------------+ | Doug Junkins | See my home page for my PGP Public Key | | Network Engineer +------------------------------------------+ | Computers & Communications | junkins@u.washington.edu | | University of Washington | http://weber.u.washington.edu/~junkins | +------------------------------+------------------------------------------+ On Tue, 27 Feb 1996, Jordan K. Hubbard wrote: > I'll try and save everyone's time with a quick diagram here of the > various machines involved: > > ----------------------------------------------------------------- > jkh home side || walnut creek side > \/ > time whisker > ed0 <---------> ed0 freefall > sl0 <---------> sl0 who > ed0 <---------> ed0 <---> BARRNET > > > who, which is the primary point of entry for WC's mbone feed, > runs mrouted with a very simply mrouted.conf: > > tunnel 192.216.222.3 192.216.178.67 metric 1 threshold 64 rate_limit 400 > > Which is our tunnel to BARRNET. However, I also want who to forward > multicast traffic to freefall which should in turn route it to whisker > (my LAN's gateway) which should then put it on the wire for any of my > hosts to see, right? > > Well, at least in theory.. I'm still battling mrouted on freefall, > trying to get it to stop doing this: > > 13:02:53.546 mrouted version 3.8 > 13:02:53.643 Getting vifs from kernel interfaces > 13:02:53.644 installing ed0 (192.216.222.4 on subnet 192.216.222.0/28) as vif #0 - rate=0 > 13:02:53.645 warning - ignoring sl0, same subnet as ed0 > > That kind of scotches my route to whisker, naturally. > > So the question of the hour for me is: How do I get it to stop > ignoring this second interface? Any configuration tips in general? > I'm definitely a newbie when it comes to multicast! > > Jordan >