From owner-freebsd-bugs@FreeBSD.ORG Fri Aug 10 12:50:06 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C07E716A418 for ; Fri, 10 Aug 2007 12:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A779213C46C for ; Fri, 10 Aug 2007 12:50:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l7ACo6h1010644 for ; Fri, 10 Aug 2007 12:50:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7ACo6lk010643; Fri, 10 Aug 2007 12:50:06 GMT (envelope-from gnats) Date: Fri, 10 Aug 2007 12:50:06 GMT Message-Id: <200708101250.l7ACo6lk010643@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: James Carlson Cc: Subject: Re: bin/111493: routed doesn't use multicasts for RIPv2 via P2P interfaces X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: James Carlson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2007 12:50:06 -0000 The following reply was made to PR bin/111493; it has been noted by GNATS. From: James Carlson To: Vernon Schryver Cc: bms@incunabulum.net, dan@obluda.cz, freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/111493: routed doesn't use multicasts for RIPv2 via P2P interfaces Date: Fri, 10 Aug 2007 08:46:56 -0400 Vernon Schryver writes: > What do you think of the enclose patch? It differs from the original > in two ways that should reduce behavior changes seen by people with > IFF_POINTOPOINT interfaces without IFF_MULTICAST. If it makes sense, > I'll generate a bundle on http://www.rhyolite.com/src/ It seems reasonable to me for RIP. Looking at the code, it seems that rdisc already handles this case -- despite the comment to the contrary on send_adv's and send_rdisc's 'dst' argument, the value can be a multicast destination (not just 0 or unicast), and often is. -- James Carlson 42.703N 71.076W