IETF Logo Mail Archive

Re: [v6ops] When IPv6 breaks IPv4

Erik Kline <ek@google.com> Thu, 26 April 2018 03:21 UTC

Return-Path: <ek@google.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 021EB12711E for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 20:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 cCN07VwzQkZ3 for <v6ops@ietfa.amsl.com>; Wed, 25 Apr 2018 20:20:58 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::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 3F9E6124B17 for <v6ops@ietf.org>; Wed, 25 Apr 2018 20:20:58 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id w2so6831521wmw.1 for <v6ops@ietf.org>; Wed, 25 Apr 2018 20:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BbnmLx0/geXtZh5ktJ7LXATWuMKiLMhdV9e2Tn6iTW8=; b=KdjqRfqnmBv0+5g2KbMJge+1weVUzWmRBQzDYP8G8LCz62026lSOpC2ui3d4WsYglM WIcCf6KHoMyieN9X01/N8DBjR07ldFSBRQHpluu87HOuTNI2lOaKkN4sINjm0fAmxDYV 4BryrQBBMT1ZjycKEmo2AUZuTvMi+2Pzrp5CyJSkyZ2HsT+qE6YS76nxB8og8pdImZra 6G2yR0zwvpWl5WLNRLTNoDoh3MOrS/ory5YlinElsjixFJyOjlWCkGBWfj3Xh5Twc2t9 LxwFf0a8RV+oyB4uB0+utBLjG35PwTIYb9APHiFhjcs6qDs9VGmYa7XOgC+qHpa0gbZm h8BQ==
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=BbnmLx0/geXtZh5ktJ7LXATWuMKiLMhdV9e2Tn6iTW8=; b=clEgpTViThjECMGSmo6+KQS8v9AjB/1x0Qgcu7M0dQapVLcJXw475DNrcctN28muws sC1E9KChGHRk/hKH81W5d3X4TAD9WzrUaAIlJVUspJmyNNG+xsLhS2a9kaMaY8qJH7xz gdB6zfchdx/AXsuaNIpUbpObjmYyPbOMdbYeG7jeEPoKEf6rRQUcvKipWknYDepUclkS 6Ed8Ckw9u5SSRwd5Q7gcJNoWU0F+mhg6NXaUK3Jxm71bdWac33tsARi6MMTg6HO7vO9D Ec4sKaYrf/nzVgCh3HS1npYBnU3lOgJNt7myKrioM5wa/5l+Jaak5rluV7uzuWHonYdZ o/Lg==
X-Gm-Message-State: ALQs6tCJW6BgAY7XUEnZjETwYqXx7wDcmQGHBA3A1SX6NwSpXGSF1N73 eDjjMIGn/yM+uG9I0D7jmIt63BzupMOtH+XBis8GQA==
X-Google-Smtp-Source: AB8JxZplSMOo95avmuXdKbL1G+wn4WYjEegFN7eOEzcxSlsnrLxe12WLVoG5jaVRoQdHs1xk/dm45JvvH0CKfnATxo0=
X-Received: by 10.28.125.74 with SMTP id y71mr13870896wmc.89.1524712856444; Wed, 25 Apr 2018 20:20:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.146.143 with HTTP; Wed, 25 Apr 2018 20:20:35 -0700 (PDT)
In-Reply-To: <5e02c3d9-5382-205e-f552-496da5c529bc@gmail.com>
References: <5e02c3d9-5382-205e-f552-496da5c529bc@gmail.com>
From: Erik Kline <ek@google.com>
Date: Thu, 26 Apr 2018 12:20:35 +0900
Message-ID: <CAAedzxp=J8Pf5XSzTg6tJPWuBzkr2a7Yj8UsoZcEdCH8G8Fs6g@mail.gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a1149742e3868a6056ab7e0bc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/jR3rvZd3Y0KWF_0TYPOv-y8vkNs>
Subject: Re: [v6ops] When IPv6 breaks IPv4
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: Thu, 26 Apr 2018 03:21:00 -0000

Stock Android does not support manually setting any IPv6 parameters whatsoever.

This means you were using some feature added by someone else.  Proper
integration with the rest of the platform may not have been easy.

On 26 April 2018 at 01:26, Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:
> There was a presentation at an IETF meeting in v6ops, about when people
> recommend to rather turn off IPv6 on some consumer electronics (Netgear was
> that?).  The GUI was telling in red characters to rather turn off IPv6,
> instead of risking IPv4 not working either.
>
> Today I had a similar experience.
>
> The hardened Android tablet Aaeon by ASUS (described in AAEON_RTC-700B.PDF)
> has an Ethernet port which is great.  The Android GUI allows to set an IPv6
> address in a field.  I put there "1::1" because it is very fast to type on a
> virtual keyboard.  After that, the Ethernet stopped working in IPv4
> altogether.  Long press reboot button does not solve it.  There is no means
> to revert back, not possible to remove that IPv6 address.
>
> Now I can throw out a window this tablet, for two reasons: neither IPv6 is
> working, nor IPv4 is working.  There is no reset button, no documentation
> about 'cold reset' and there are are two batteries: one main and one backup.
> The backup can be removed but the main is hardened.  I suspect that even if
> the main battery dies out the GUI config file containing that "1::1" will
> still be there for many years a writeable RAM lasts.
>
> Worse, I did this in front of partner, in my good intentions to illustrate
> proof how IPv6 is so present everywhere already.
>
> Next time I will be more moderate about my trust in IPv6 availability.
>
> Alex
>
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email