From owner-freebsd-net@FreeBSD.ORG Fri Dec 19 04:11:26 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53C2DD62 for ; Fri, 19 Dec 2014 04:11:26 +0000 (UTC) Received: from webmail2.jnielsen.net (webmail2.jnielsen.net [50.114.224.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 334771CFF for ; Fri, 19 Dec 2014 04:11:25 +0000 (UTC) Received: from [192.168.2.123] (c-50-160-123-105.hsd1.ut.comcast.net [50.160.123.105]) (authenticated bits=0) by webmail2.jnielsen.net (8.14.9/8.14.9) with ESMTP id sBJ4BI3q060800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 18 Dec 2014 21:11:24 -0700 (MST) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail2.jnielsen.net: Host c-50-160-123-105.hsd1.ut.comcast.net [50.160.123.105] claimed to be [192.168.2.123] From: John Nielsen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: IPv6 multicast routing Message-Id: Date: Thu, 18 Dec 2014 21:11:18 -0700 To: "freebsd-net@freebsd.org" X-Mailer: iPhone Mail (12B440) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2014 04:11:26 -0000 Hi all- Does anyone do IPv6 multicast routing on FreeBSD? If so, what software do yo= u use? Any caveats or other things to be aware of? The only options I have seen are all in net/mcast-tools and I'm having some t= rouble with each of them. I do have "options MROUTING" in my kernel and IPv6= forwarding enabled on each host. I've had the best luck with "mfc": I can get packets to traverse a single ro= uter. However I can't get them to traverse a second one in either direction (= though that may or may not be a problem with mfc itself). The big downer of c= ourse is that each unicast source and multicast destination has to be explic= itly spelled out in each direction in the config file. Not at all scalable a= nd not compatible with the auto-configuration goals of my project. The one I think I'd like to use is pim6sd. However I have had no luck with e= ither it or pim6dd. Both will run but not pass packets, and they each compla= in that they cannot assign the requested ff02::2 address on either interface= . Any advice or suggestions appreciated. JN=