From owner-freebsd-net@FreeBSD.ORG Fri Apr 24 15:38:13 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 A7EA21065688 for ; Fri, 24 Apr 2009 15:38:13 +0000 (UTC) (envelope-from bob@veznat.com) Received: from mail.ttora.com (mail.ttora.com [208.75.243.236]) by mx1.freebsd.org (Postfix) with ESMTP id 69D358FC1F for ; Fri, 24 Apr 2009 15:38:13 +0000 (UTC) (envelope-from bob@veznat.com) DomainKey-Signature: s=two; d=veznat.com; c=nofws; q=dns; h=X-MID:X-IronPort-AV:X-IronPort-AV:Received:User-Agent: Date:Subject:From:To:Message-ID:Thread-Topic:Thread-Index: In-Reply-To:Mime-version:Content-type: Content-transfer-encoding; b=EqqlzHc+/DRuUNR2xKM83PveOtKJ6VEGlIGNTDQpv7U41ugeBURkeR3b 3rJaIiO3Vnq7AG79OEjZbqSw21WWJ1o3jkHphbK8/1KJHYM61HJ4P2lrB nNHYtIBeWKjH27spyCjgp8RS5Z0ugE6m+DTHuqjnLaVP9HctkIW7Y4oMc 0=; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=veznat.com; i=bob@veznat.com; q=dns/txt; s=one; t=1240587493; x=1272123493; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Bob=20Van=20Zant=20|Subject:=20R e:=20IPv6=20Ideas|Date:=20Fri,=2024=20Apr=202009=2008:09: 18=20-0700|Message-ID:=20 |To:=20|Mime-version:=201.0 |Content-transfer-encoding:=207bit|In-Reply-To:=20<200904 24120022.DE524106568C@hub.freebsd.org>; bh=xluhHGVBn205ixxxTnpD80poGF8z6y0JuwfBbixl04w=; b=lT0fMCG7Qwjy8veSBWABJGcaNyJTYzqnQPDW1cVfUxJz2F4NqynvD3CU UKdNn0LRD69i4Gck2i6jTrbAsSsKwunyTFPBgYQ11At7aesPyjsk3hv3U t4RSlMnS+mQg3zCPoTpdmFOKOW+ReF0v904bUb22u+p/7J44AEQL9h46+ Q=; X-MID: 823627 X-IronPort-AV: E=McAfee;i="5300,2777,5594"; a="823627" X-IronPort-AV: E=Sophos;i="4.40,242,1239001200"; d="scan'208";a="823627" Received: from unknown (HELO [192.168.1.172]) ([24.5.4.92]) by mail.ttora.com with ESMTP/TLS/DES-CBC3-SHA; 24 Apr 2009 08:09:20 -0700 User-Agent: Microsoft-Entourage/12.15.0.081119 Date: Fri, 24 Apr 2009 08:09:18 -0700 From: Bob Van Zant To: Message-ID: Thread-Topic: IPv6 Ideas Thread-Index: AcnE7qNvVK69Y7GgZEaoUE918kAnbw== In-Reply-To: <20090424120022.DE524106568C@hub.freebsd.org> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit 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 15:38:14 -0000 I was in a similar position to you not that long ago. I got my LAN all dual stack and was a happy camper. I wanted 100% IPv6 and never to see another RFC 1918 address on my network again. Unfortunately it's just not practical. My ReadyNAS doesn't talk v6. My mac doesn't appear to like v6 for the file transfer protocols it supports. My iPhone doesn't do v6. The applications just aren't ready to live in a v6-only world. I suggest leaning on your vendors whenever you can so that they no longer can say "no one is asking for it." A boring, un-bumped thread asking for IPv6 support in the iPhone: http://discussions.apple.com/thread.jspa?threadID=1960260&tstart=0 Getting back to your question. It is my understanding that this IVI proposal is the most likely to become an officially adopted standard: http://tools.ietf.org/html/draft-xli-behave-ivi-01 That's being done as part of the behave working group: http://www.ietf.org/html.charters/behave-charter.html If anyone were to begin working on something like this this they'd probably want to think about following that proposal. I too am interested in working on this. Just haven't sat down to really start thinking about it yet. -Bob Message: 14 Date: Thu, 23 Apr 2009 21:14:50 -0400 From: Nathan Lay Subject: IPv6 Ideas To: freebsd-net@freebsd.org Message-ID: <49F1128A.3080501@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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. In terms of FreeBSD support, rtadvd and rtsol do not yet support (easily? -O option in rtadvd/rtsold) RFC5006 (Router Advertisements Option for DNS Configuration) which make it inconvenient to use mobile devices (like laptops) on an IPv6 network. I haven't had much luck with net/radvd. Is this something that could be improved? I'd be willing to implement this support, but I have very little time to spare (writing thesis). 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. Oh yeah, one annoyance on 7-STABLE, it seems like pf is started before IPv6 rc.conf options are processed (including IPv6 address assignment) breaking inet6 rules that involve $if:network. Comments? Other than that, this has been one hell of a fun experience. Best Regards, Nathan Lay