Re: [v6ops] Happy eyeballs suggestions, was: Re: Apple and IPv6, a few clarifications

Iljitsch van Beijnum <> Mon, 13 July 2015 13:04 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 069521B2A6B for <>; Mon, 13 Jul 2015 06:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bdgd1fvhMbOl for <>; Mon, 13 Jul 2015 06:04:41 -0700 (PDT)
Received: from ( [IPv6:2001:1af8:3100:a006:1::]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 44C661B2A69 for <>; Mon, 13 Jul 2015 06:04:41 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.13.3/8.13.3) with ESMTP id t6DD3NCn000717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <>; Mon, 13 Jul 2015 15:03:24 +0200 (CEST) (envelope-from
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Iljitsch van Beijnum <>
In-Reply-To: <>
Date: Mon, 13 Jul 2015 15:04:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: " WG" <>
X-Mailer: Apple Mail (2.2098)
Archived-At: <>
Subject: Re: [v6ops] Happy eyeballs suggestions, was: Re: Apple and IPv6, a few clarifications
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 13 Jul 2015 13:04:43 -0000

On 22 Jun 2015, at 16:33, Iljitsch van Beijnum <> wrote:

> About the test DNS64/NAT64 implementation:

> Obviously the test network isn't a "real" NAT64 test network when there's no native IPv6 present. And obviously there's no easy way to have native IPv6 materialize out of thin air. But someone who wants to test more thoroughly may want to get native IPv6 or set up a tunnel broker tunnel. It would be nice if the test NAT64 setup could work with that, so the devices on the test network can connect to IPv6 destinations over IPv6 and IPv4 destinations through the NAT64.

> Basically, what's needed for this is that if the interface in question is configured with "real" IPv6 addresses, those are kept and the prefix in question is advertised in RAs.

See here for a workaround, although I can't seem to figure out these disappearing default routes: