Date: Sat, 10 Feb 1996 12:19:33 PST From: Bill Fenner <fenner@parc.xerox.com> To: "Ron G. Minnich" <rminnich@sarnoff.com> Cc: hackers@freebsd.org Subject: Re: multicast config confusion: can't get mrouted to work Message-ID: <96Feb10.121941pst.177478@crevenia.parc.xerox.com> In-Reply-To: Your message of "Fri, 09 Feb 96 08:55:55 PST." <Pine.SUN.3.91.960209115224.20566A-100000@terra>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.SUN.3.91.960209115224.20566A-100000@terra> you write: >[mrouted says "can't forward; no enabled vifs"] > >Here's a sample ifconfig -a >lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 lp0 is multicast-capable but is down. >ep0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX> mtu 1500 > inet 130.33.10.216 netmask 0xfffff800 broadcast 130.33.15.255 ep0 is not multicast-capable; this driver has been kind of in limbo for a while and several different sets of multicast patches have been floating around. If you are running -current, one version of the patches got committed on January 29th, but there have been enough other changes that you can't just grab the if_ep.c out of -current. You could *try* applying just these patches to your sources; check out http://www.freebsd.org/cgi-bin/cvsweb/src/sys/i386/isa/if_ep.c?r1=1.38?r2=1.39 for the diffs that got put into -current. >lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 lo0 is loopback so gets ignored. >sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 sl0 is multicast-capable but is down. >tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 tun0 is multicast-capable but is down. I don't see any enabled vifs either. What is it that you *want* to do with mrouted? Even after you get the multicast-capable ep0, you will still only have a single enabled vif. Bill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96Feb10.121941pst.177478>