IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Mon, 17 July 2017 10:26 UTC

Return-Path: <mellon@fugue.com>
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 0EEA8131838 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 03:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 y6ssej0m7AVz for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 03:26:54 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 871C81317D5 for <v6ops@ietf.org>; Mon, 17 Jul 2017 03:26:44 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id e199so13323819pfh.2 for <v6ops@ietf.org>; Mon, 17 Jul 2017 03:26:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Vl91t5ih0fA5vnLcf+H1hjRL4EzZxVkx9EHGa9UFbVk=; b=HdkPuF44YVx9ax+BOLk3nGOOpBlPA/T+ZlxQaEXg05z++X2ZHhocG2tLZAcTNp+QSa iMYufP2jLGN8dyPqpu0d8/gw2Jm069SP/G0q+0WDjdk9LVz8+6yqyWVsDuhSVVzYJzrb ZM6/U92TKt7reMDuEQ+1nsdZww6MBeqJJ7OAa61jPMRJ09EoGZTvKCHYYbUgPVBoAOPG ayyXKNbq9twdSs48g3yCKXnPszEnicZGoWFVNR3RgAn2ioOrXdHeMGghfoQa847lwqzr SLlhB7kMQkmmpBqlVcJx43rufgmfGV+uiQdIviQ50SL59FWixcMJptt+/v7l7EqdiJym sJzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Vl91t5ih0fA5vnLcf+H1hjRL4EzZxVkx9EHGa9UFbVk=; b=g2ZldZBSMe/w7iNMrSFgYT70xNd4fIAHD7PLphKciB8XjmRL9h06BsZypaUzCbDvTW o7nm0Av2q15jv2F49hnIJNuhJJuyUO3Dek4vYcfb5BKNP6HVGGjoGlgjwvvhEcntaLTL mYeTE9Ltu6fGBd72/j/IEh+wdxD9uyEi++/j58h+Li+JGXgkBfrCPaUS1J/MA/cEfwG7 P1dy2JsDRqv8XiuRl68qXwgJQqRrq50kNQ/ikeEmdoHkMi8Ozo6Xa2yrl/81dTnNan9s k9dp6O/HqzSqZrQjVqmOAP+QJG5vbaslJnWZjHTPr77symdQ//5sXHPYPpB992lv7GKQ dC5w==
X-Gm-Message-State: AIVw113qU56kmxC7MGLL0lDS5MfQ8jwu+dvaIUGEqtvXNAG3ZlVNIYMI 2iFLhNZ65CMWke7Ai6j9EOpH2AS1dk3U
X-Received: by 10.98.193.68 with SMTP id i65mr3855371pfg.142.1500287203837; Mon, 17 Jul 2017 03:26:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Mon, 17 Jul 2017 03:26:03 -0700 (PDT)
In-Reply-To: <AC20C61D-5F52-451E-A626-B6CBF9E42773@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> <20170717120436.598ca19e@echo.ms.redpill-linpro.com> <AC20C61D-5F52-451E-A626-B6CBF9E42773@consulintel.es>
From: Ted Lemon <mellon@fugue.com>
Date: Mon, 17 Jul 2017 12:26:03 +0200
Message-ID: <CAPt1N1naJ16ot_jqdgDsGU7h9AjiONk-dN+wnO=uWxak0rZA4Q@mail.gmail.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c184720d8b50c055480d526"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/OpHVlQxd1pqD7KcaapYqyb09mwc>
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:26:56 -0000

OpenVPN requires that the client be configured to use either IPv4 or IPv6.
  If you configure the client to use IPv6, it will work just fine through
NAT64 to an IPv4 OpenVPN server.   This is an unfortunate limitation of
OpenVPN; the maintainers are aware of it, but apparently it's not a
priority to fix. :(

On Mon, Jul 17, 2017 at 12:23 PM, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> 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.
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email