From owner-freebsd-current Mon Jul 28 10:47:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20576 for current-outgoing; Mon, 28 Jul 1997 10:47:53 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA20568 for ; Mon, 28 Jul 1997 10:47:47 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id KAA11373; Mon, 28 Jul 1997 10:47:43 -0700 (PDT) Message-Id: <199707281747.KAA11373@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: lamaster@george.arc.nasa.gov cc: current@freebsd.org Subject: Re: Your message of "Fri, 25 Jul 1997 17:53:59 PDT In-reply-to: Your message of "Mon, 28 Jul 1997 10:33:22 PDT." <199707281733.KAA13863@george.arc.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jul 1997 10:47:42 -0700 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, we used to have an mrouted capable kernel by default however it got taken out for some reason... Perhaps, someone from the FreeBSD core team care to explain? Regards, Amancio >From The Desk Of lamaster@george.arc.nasa.gov : > > > My statement was in reference to NT's ip stack not being capable of > > supporting mrouted so the next logical thing is to get a > > tcp/ip stack which can support mrouted . > > I see what you mean now. I have no idea if alternative stacks > are available as they were for Windows. It seem unlikely, > because TCP/IP is supported by default, and isn't considered > an extra layer as it was under Windows 3.1, requiring the "Winsock" > solution. > > Also, as Steve Casner said, the real question is whether or not > the OS/stack combination supports multicast forwarding, not just > multicast. > > I haven't done a survey, but, AFAIK, the only system that supports > forwarding *by default* is Irix. Even with FreeBSD, you have > to recompile the kernel that way, and, with Solaris, you have > to patch the default release with one or two recompiled modules. > > SGI may have its problems, but, it is cool that they have been > in multicast for such a long time. > > > Regards, > Hugh LaMaster > >