Date: Tue, 27 Feb 1996 13:04:47 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: multimedia@freebsd.org Subject: Seeking advice on mrouted configuration.. Message-ID: <14046.825455087@time.cdrom.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14046.825455087>