From owner-cvs-all Tue Jul 17 14: 0:17 2001 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ED15537B401; Tue, 17 Jul 2001 14:00:07 -0700 (PDT) (envelope-from dcs@FreeBSD.org) Received: (from dcs@localhost) by freefall.freebsd.org (8.11.4/8.11.4) id f6HL07q82265; Tue, 17 Jul 2001 14:00:07 -0700 (PDT) (envelope-from dcs) Message-Id: <200107172100.f6HL07q82265@freefall.freebsd.org> From: "Daniel C. Sobral" Date: Tue, 17 Jul 2001 14:00:07 -0700 (PDT) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/sys/netinet ip_output.c X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG dcs 2001/07/17 14:00:07 PDT Modified files: sys/netinet ip_output.c Log: (forced commit for more info on the previous change) According to RFC 1112, which deals with multicasting, an application must specify the interface on which it wished to send a multicast packet. In the absence of such an interface, a default is selected. Previous behavior in ip_output.c erroneously checked for a route to the destination multicast address, rejecting the packet if none existed. Applications got around this with a FAQ recommending a 224.0.0.0/29 route to loopback. This worked because the multicast code in ip_output.c discards route information if an interface was selected. The previous commit skips the route check in the case where a multicast packet is being send to an application-defined interface. The only change in behavior, if no bugs were introduced, is the lack of rejection of a multicast packet for which no route exists sent to an application-defined interface. MFC after: 2 weeks Revision Changes Path 1.129 +1 -1 src/sys/netinet/ip_output.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message