From owner-freebsd-bugs@FreeBSD.ORG Fri Aug 10 13:00:11 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 AA6B416A418 for ; Fri, 10 Aug 2007 13:00:11 +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 9105A13C458 for ; Fri, 10 Aug 2007 13:00:11 +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 l7AD0BwN010893 for ; Fri, 10 Aug 2007 13:00:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l7AD0BVe010892; Fri, 10 Aug 2007 13:00:11 GMT (envelope-from gnats) Date: Fri, 10 Aug 2007 13:00:11 GMT Message-Id: <200708101300.l7AD0BVe010892@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce M Simpson 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: Bruce M Simpson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2007 13:00:11 -0000 The following reply was made to PR bin/111493; it has been noted by GNATS. From: Bruce M Simpson To: James Carlson Cc: Vernon Schryver , 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 13:54:18 +0100 James Carlson wrote: > 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. > > +1 here. It is OK to allow the use of multicast addressing on links which do not natively multicast. Indeed it is necessary for IPv4 and IPv6 multicast forwarding to work across generic point-to-point links, as no special encapsulation is performed. RIPv2's multicast address falls in the 224.0.0.0/8 link local scope, so it should never be seen outside of the link anyway. I would just suggest that it should default to off to avoid confusing folk. If Zebra/Quagga is disallowing multicasted RIP across non-multicast links, that's another story entirely. Regards, BMS