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

Gert Doering <gert@space.net> Mon, 17 July 2017 11:37 UTC

Return-Path: <gert@space.net>
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 A64D6129B62 for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 04:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 oQDHdsZgB5_X for <v6ops@ietfa.amsl.com>; Mon, 17 Jul 2017 04:37:39 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 886F21288B8 for <v6ops@ietf.org>; Mon, 17 Jul 2017 04:37:39 -0700 (PDT)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 1FA4D41B95 for <v6ops@ietf.org>; Mon, 17 Jul 2017 13:37:38 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id EFE4041B75; Mon, 17 Jul 2017 13:37:37 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id E22B792F4; Mon, 17 Jul 2017 13:37:37 +0200 (CEST)
Date: Mon, 17 Jul 2017 13:37:37 +0200
From: Gert Doering <gert@space.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: IPv6 Ops WG <v6ops@ietf.org>
Message-ID: <20170717113737.GQ45648@Space.Net>
References: <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> <CAPt1N1naJ16ot_jqdgDsGU7h9AjiONk-dN+wnO=uWxak0rZA4Q@mail.gmail.com> <1EA41531-B9F2-481B-BD59-8925DF84B49E@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <1EA41531-B9F2-481B-BD59-8925DF84B49E@consulintel.es>
X-NCC-RegID: de.space
User-Agent: Mutt/1.8.2 (2017-04-18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ofIBPrKDgaLqTu0ToB0gi0jvs34>
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 11:37:42 -0000

Hi,

On Mon, Jul 17, 2017 at 01:32:35PM +0200, JORDI PALET MARTINEZ wrote:
> Responding also to Gert.
> 
> I just tried again, no need to upgrade the client or server, as both of them were running the latest available versions.
> 
> As you said, it is a ???strange??? configuration ???language???. Even if you don???t have the server with IPv6, it needs to be enabled in both sides to work thru a NAT64.

Actually, no.  The server can be happily IPv4-only, but of course you
need to enable dual-stack mode on the client (which is the default, to
point this out explicitely).

If you force the client to IPv4-only "because the server is!", this is
what you'll get: something which is broken if you are in a DNS64/NAT64
network - but that's a misconfiguration, and there is no need to do so.

Same thing if you put a literal v4 address in your config - it's a 
misconfiguration, and it needs to break so people are made aware of it,
and can fix things.

(In your case it seems the VPN provider has created that config for you,
and if that provider puts "ipv4 only!" in the config, they need to be
told in no uncertain terms that this is a buggy client config - if the
DNS name resolves to v4-only, the client will automatically be v4-only,
so what)


> Of course, this means we ???thechies??? find the work around with some help from others that already suffered the problem, but a regular user not. If we were running CLAT, it just works and the most important, we get it reported/logged automatically, which is what I???m insisting on.
> 
> However ???. I???m still on the ietf-nat64 and Outlook (last release 15.36) for Mac refuses to send this message. I need to turn to another SSID to keep working thru the meeting. This is what we want?

This is what "we" *need*, otherwise it will just silently work and
nobody will ever escalate this high enough into Microsoft to fix it.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279