From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx.spodhuis.org (smtp.spodhuis.org [IPv6:2a02:898:31:0:48:4558:736d:7470]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id BAD2F21F182 for ; Mon, 10 Dec 2012 00:45:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=spodhuis.org; s=d201210; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=pxiAM94fNQr9cRJ5rPuXOrmbu4KlolWIewarsGzdFE0=; b=N5OPB242rqf3LRp5Xjky7IoGcMQdPwQMRu/3zBtCmYBtBw6syNu4PLBnOIFb02TWlx3sB0fRFF74XS5V02QqGVifIma0dtzJRFl5v5E2mHwTHbMyQv1RsGdVZxjxVAurRbaB90hNw0ZrhRrTXRuPlbUiAhVok2pFib0aStbpHMI=; Received: from authenticated user by smtp.spodhuis.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1ThyzL-000OOp-F8; Mon, 10 Dec 2012 08:45:23 +0000 Date: Mon, 10 Dec 2012 03:45:22 -0500 From: Phil Pennock To: Michael Richardson Message-ID: <20121210084522.GA93640@redoubt.spodhuis.org> References: <3147.1355105084@obiwan.sandelman.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3147.1355105084@obiwan.sandelman.ca> X-Mailman-Approved-At: Mon, 10 Dec 2012 00:46:36 -0800 Cc: cerowrt-users Subject: Re: [Cerowrt-users] 6in4 links X-BeenThere: cerowrt-users@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Support for user problems regarding cerowrt List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Dec 2012 08:45:28 -0000 On 2012-12-09 at 21:04 -0500, Michael Richardson wrote: > The problem is that the interface that is created is a /128, and it's > the ::2, but since it is a /128, the ::1 isn't "On-network", so the > static route fails. Er, a /128 means there can be no route associated with it, this is used typically for things like additional aliases on an interface. To use this for sending traffic, you'd need a concept of "pump to far side" which exists for things like a tunnel, but not for stf0, which is able to talk to arbitrary end-points. For stf0, perhaps you want a /16 ? You might want a /127 per RFC 6164 (and RFC 6547 explicitly recategorised the /127s-harmful RFC as historic). Note that a ::1 and a ::2 would still be on different networks for a /127. You perhaps want ::2 and ::3 (or a /126 but then consider the ping-pong issues). -Phil