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

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 17 July 2017 10:23 UTC

Return-Path: <prvs=13714351ed=jordi.palet@consulintel.es>
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 61A64129B5B for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 03:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 lvjwVrXkzNno for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 03:23:20 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 555DB1252BA for <v6ops@ietf.org>; Mon, 17 Jul 2017 03:23:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1500286998; x=1500891798; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=OpZ0yVn0Ugo2n3vAV4BLxg1sU x3jKBggZPNgZc1P65o=; b=D9tTnvotqgayj3ZfCuaGtDjV+HJ3lX42U2SXqySas rHOMuDjXoyfx07ooW9YH9yi2WB7tF+I92uYA43nz/IAj+BJvrTVoMDuRf+UphZAr rgvwkEV3nL4paB68n8KJfVdwo6TcNWko/0WS3epLZdQ3zlU/wTTD/RQkPYA1CPLe fM=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=axDiKM0HYmf9WClLzY60L1dHTyTNXe2X+/wz6rbRHmL9+hBN89ZSJ4SNMHWw CgIHBBWTTnJQ0+IRoMQdrjI/pvUWByHkwQcM0GhNfom+ne5nZ3qvsURMa v+13WYjsE6glvmAlKJgZ/xtT5QgmxnEGukS/zl3ySemtdf+adRSiT4=;
X-MDAV-Processed: mail.consulintel.es, Mon, 17 Jul 2017 12:23:18 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 17 Jul 2017 12:23:17 +0200
Received: from [31.133.186.43] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005478338.msg for <v6ops@ietf.org>; Mon, 17 Jul 2017 12:23:16 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170717:md50005478338::61JGTXftdqeRYmIL:0000BUMA
X-Return-Path: prvs=13714351ed=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.24.0.170702
Date: Mon, 17 Jul 2017 12:23:13 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <AC20C61D-5F52-451E-A626-B6CBF9E42773@consulintel.es>
Thread-Topic: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings
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> <20170717120436.598ca19e@echo.ms.redpill-linpro.com>
In-Reply-To: <20170717120436.598ca19e@echo.ms.redpill-linpro.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Ft6QyHDplic2T71q5hqPIOYZvRk>
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:23:22 -0000

Using latest version, both at the server and client. I will check later what specific version on both sides, but they are using >2.4.2 for sure.

Regards,
Jordi
 

-----Mensaje original-----
De: Tore Anderson <tore@fud.no>
Responder a: <tore@fud.no>
Fecha: lunes, 17 de julio de 2017, 12:04
Para: <jordi.palet@consulintel.es>
CC: <v6ops@ietf.org>
Asunto: Re: [v6ops] Incremental Deployment of IPv6-only Wi-Fi for IETF Meetings

    * 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
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.