From owner-freebsd-net@FreeBSD.ORG Fri Apr 24 13:57:12 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDB2D1065673 for ; Fri, 24 Apr 2009 13:57:12 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (unknown [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id B013A8FC13 for ; Fri, 24 Apr 2009 13:57:12 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 42892 invoked by uid 89); 24 Apr 2009 13:57:17 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 24 Apr 2009 13:57:17 -0000 Message-ID: <49F1C53F.5040202@ibctech.ca> Date: Fri, 24 Apr 2009 09:57:19 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Nathan Lay References: <49F1128A.3080501@comcast.net> In-Reply-To: <49F1128A.3080501@comcast.net> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: IPv6 Ideas X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Apr 2009 13:57:13 -0000 Nathan Lay wrote: > I started playing with IPv6 on my home network with the intent to > transition over. While many things work quite well, IPv6 technology in > general still seems to have some rough edges. I disagree. I believe the "rough edges" do not belong to IPv6, the "rough edges" are the applications that are not compatible, the network devices that are not compatible, and the ISP's who have the mindset that they will never need IPv6, and refuse to look at it. > To be backward compatible with IPv4, I had a look at faith and faithd > and while these tools are ingenius, I don't think they are good enough > for transitioning to IPv6. I imagine it is possible to write an > IPv6->IPv4 NAT daemon that uses faith to capture and restructure > IPv6/IPv4 packets. Though, it really seems like this is the firewall's job > > A pf rule like: > > nat on $inet4_if inet to any from $lan_if:network6 -> ($inet4_if) > > would be extremely convenient. I'm aware pf doesn't support the token > :network6 ... its just a wishful example. The IPv6 mapped IPv4 > addresses would be the standard ::ffff:0:0/96 prefix. I imagine that > this is very difficult to implement but I don't see why it wouldn't be > possible. If a firewall supported this kind of NAT, a home network > could easily deploy IPv6 and be backward compatible. Well, not quite, I > guess BIND would have to serve IPv6 mapped IPv4 addresses to IPv6 queries. My hope is that I never have to deal with anything where IPv6 and NAT are in the same sentence :) > Comments? - ask your ISP about their IPv6 deployment plans, and how soon they can provide it to you - get a tunnel set up to a tunnel broker (sixxs.net, he.net etc) - ask your ISP how soon they can provide it to you - play, play play > Other than that, this has been one hell of a fun experience. A tad bit different, huh ;) Steve