IETF Logo Mail Archive

Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

Tore Anderson <tore@fud.no> Mon, 17 July 2017 10:04 UTC

Return-Path: <tore@fud.no>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABBCD131771 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 03:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbygmsHr6CWz for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 03:04:38 -0700 (PDT)
Received: from mail.fud.no (mail.fud.no [IPv6:2a02:c0:4f0:bb02:f816:3eff:fed3:8342]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFECC12F28A for <v6ops@ietf.org>; Mon, 17 Jul 2017 03:04:38 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=53196 helo=echo.ms.redpill-linpro.com) by mail.fud.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from <tore@fud.no>) id 1dX2tI-00013g-VB; Mon, 17 Jul 2017 12:04:36 +0200
Date: Mon, 17 Jul 2017 12:04:36 +0200
From: Tore Anderson <tore@fud.no>
To: jordi.palet@consulintel.es
Cc: v6ops@ietf.org
Message-ID: <20170717120436.598ca19e@echo.ms.redpill-linpro.com>
In-Reply-To: <D0BB59E5-90DB-4930-92B3-6AC7E0AF7391@consulintel.es>
References: <7643C1DC-76A3-4652-9BB1-D0D42801F37E@consulintel.es> <CAEqgTWYOe=jWp=zVZNLx6DjKjNpPTYaq2jmjryudrGZHKZNq6g@mail.gmail.com> <A5D0385C-F755-4B44-86D8-6E618E77193F@consulintel.es> <CAPt1N1kroh2cPkTr8HRfNjLTdG0hkC1oQsUZdhQzQA5tA9-xug@mail.gmail.com> <9AF791E9-1E12-425E-93A4-2913E2D18CBA@consulintel.es> <CAPt1N1kU4cpVCsp7W3XNAZupYqjTWVH+BNp9bwtznnWD_uP2oQ@mail.gmail.com> <CAEqgTWZzZW0wKggDXjY=-aMfDxzd5-GoRqju1829XwY3aHQuYg@mail.gmail.com> <0FAF1E05-DA4B-47BF-95F7-7EFCD1BED9B0@cable.comcast.com> <42188852-BBEB-4D75-967F-4BED79BBBCAE@consulintel.es> <20170717105929.5a6b7997@echo.ms.redpill-linpro.com> <56F96ACC-E55F-4C07-94D9-C3BE511836B1@apple.com> <D0BB59E5-90DB-4930-92B3-6AC7E0AF7391@consulintel.es>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/duo6tdZdxkuDLUaJhGOHRKaY67A>
Subject: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jul 2017 10:04:43 -0000

* JORDI PALET MARTINEZ <jordi.palet@consulintel.es>

> I’ve investigated this with OpenVPN right now using the ietf-nat64
> SSID.
> 
> The remote OpenVPN server is IPv4-only, has a domain name (so not
> using literals), however, it seems the name is resolved to the
> IPv4-only address (maybe not using Apple Sierra OS – latest version-
> all updated- system APIs), so it fails to work with the NAT64.

Which OpenVPN version is this? If you're not running v2.4.0 or newer,
try upgrading. I believe this this have improved there, cf.
https://github.com/OpenVPN/openvpn/blob/release/2.4/Changes.rst:

[...]

  Dualstack round-robin DNS client connect
    Instead of only using the first address of each --remote OpenVPN
    will now try all addresses (IPv6 and IPv4) of a --remote entry.

[...]

  * proto udp and proto tcp now use both IPv4 and IPv6. The new options
    proto udp4 and proto tcp4 use IPv4 only.

Tore

v2.23.0 | Report a Bug | By Email