From owner-freebsd-bugs Thu Jul 15 11: 0: 8 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BB9EB14CA3 for ; Thu, 15 Jul 1999 11:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA06427; Thu, 15 Jul 1999 11:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 15 Jul 1999 11:00:02 -0700 (PDT) Message-Id: <199907151800.LAA06427@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Garrett Wollman Subject: kern/12646: IGMP reports not sent if no multicast route Reply-To: Garrett Wollman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/12646; it has been noted by GNATS. From: Garrett Wollman To: kbracey@acorn.co.uk Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: kern/12646: IGMP reports not sent if no multicast route Date: Thu, 15 Jul 1999 13:54:49 -0400 (EDT) < The problem is that ip_output() will not output multicast packets if > it can't find a route for the destination IP address, even if the caller > has provided an interface in the multicast options, as igmp_sendpkt() does. This is a wart resuling from a path of development which was never completed. What was supposed to happen eventually was that the underlying protocols would be modified to do the work of ip_output() themselves, implementing only that part of the functionality which was actually necessary. Unfortunately, this work basically stopped when I changed jobs (the previous employer was paying for it), so things were left in this intermediate state. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message