From owner-freebsd-hackers Tue Jun 23 13:11:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26046 for freebsd-hackers-outgoing; Tue, 23 Jun 1998 13:11:04 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25965 for ; Tue, 23 Jun 1998 13:10:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA06830; Tue, 23 Jun 1998 13:10:51 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Amancio Hasty cc: freebsd-hackers@FreeBSD.ORG Subject: Re: option MROUTING In-reply-to: Your message of "Tue, 23 Jun 1998 10:39:36 PDT." <199806231739.KAA22683@rah.star-gate.com> Date: Tue, 23 Jun 1998 13:10:51 -0700 Message-ID: <6826.898632651@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any reason why MROUTING is not enabled in the default kernel configuration. Sure. Because for 99% of the userbase, it would only constitute unnecessary bloat. How many here out of the some 10,000 readers of this list are using multicast? 100? 500? You don't need to respond with a yes/no on this (please don't! :), my point simply being that it's a small fraction of the user base and even those who really want to run multicast these days still often find themselves blocked upstream by ISPs who DON'T want to run multicast traffic. :-) I've also never heard any complaints from the remaining 1% that it was difficult to enable or anything. If you're clued-in enough to even know how to get multicast traffic at your site, you probably also know how to compile a kernel. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message