IETF Logo Mail Archive

Re: [v6ops] out-of-focus: why DHCPv6 breaks Android computers?

Scott Morizot <tmorizot@gmail.com> Mon, 28 October 2019 22:53 UTC

Return-Path: <tmorizot@gmail.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 231A612006B for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2019 15:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 T9myczZDJP3x for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2019 15:53:35 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 7E064120033 for <v6ops@ietf.org>; Mon, 28 Oct 2019 15:53:35 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id k1so3639501iom.9 for <v6ops@ietf.org>; Mon, 28 Oct 2019 15:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OON8ZZ76sN7cRoNOgivpCgVVZ/VbPu2m3b6lpUgelt4=; b=mKkX1mwxFvh4GvWGKLdpjunIxTAnWlrC15MIz3KYkScKWRVtl+E9PEdkj30ibkXfSB QH7iMAsaHDKJ/7Hw4WJi2BtH1Ij7E98zThZavstxBtxFPRmAPG6tXA4Jw1RMeSEPBMbw aVM0fycO7xxvTsQMGwCDRelyx27cW/v1K4QTHK8RVt4KZl01Fm8MEXOhLteFD9w45Kdu IrZ8ZPQ8TBJBAAkDa5zuBaxj3BbzusOtypZAkyuWGUQHpBezS2MJGzJ+PuyfUHRD8jDM 9jg/fCyTasnHcyxk36iuY7bOLSRL9s7MA6y3IzrbJ70OMAZ2tOcMQQ99LlCqxXOrwjJs Me8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OON8ZZ76sN7cRoNOgivpCgVVZ/VbPu2m3b6lpUgelt4=; b=TewhKzJ46F3MWYYysK0/2rjYnL7t2Yrg5LkwBYdnqMQDR2GtPuLKCFQEUdALhe+3L5 pksU4+pw+3UHAHJXaiABhxW3KmJ/CfGcFm2ejRrCuMkaGvrTuJS+o0iNQQ1xFqBlH5oj ewDWeKQtsW2culBmwPnTdUFAsENgjJ6Ro5wYogHFMLjWM0qVBRSiAokpXCw6tyYSwiMX NrysE8ZfbsS/vBupykEKoe+oJGyzR8N2Zr7H11o+CUk5K1ReLeIDbOOsstEfRgQR+NHO QQLrgHIBzjCCWP1EmAm0BUfPOT+eM8GhcCbcWxCDf02wBkQlC2Q0KK/jdEDBOuH1rGPd b3Ew==
X-Gm-Message-State: APjAAAXJG3RpCY9nEGC5VHx3XMEVH8dxsjqPiFyGCDm/MOc1myYMzamf EiY4+X55E2EFZQPEQ8opL0vo5JagDX+m5yO/JRnW
X-Google-Smtp-Source: APXvYqz9nt9WdqclGNJWtpdDiEALNs5AwQ24zw+Eq8rzFwecCi7GQr4KT+L2l6sLmNh/OaMbBGu36QHhcwpFIfV50Es=
X-Received: by 2002:a5d:9dcf:: with SMTP id 15mr428914ioo.83.1572303214626; Mon, 28 Oct 2019 15:53:34 -0700 (PDT)
MIME-Version: 1.0
References: <2b617ab1-018a-8f03-4d8b-081c09c9c88a@gmail.com> <3843CFD2-80EE-4DEF-AE59-ED9F2B271048@cisco.com> <F32C6581-59AA-4598-BFA8-4D98BBA9335C@thehobsons.co.uk>
In-Reply-To: <F32C6581-59AA-4598-BFA8-4D98BBA9335C@thehobsons.co.uk>
From: Scott Morizot <tmorizot@gmail.com>
Date: Mon, 28 Oct 2019 17:53:23 -0500
Message-ID: <CAFy81rk6fvJ3_JgmDMzW-T=FpjyRNY28XagS-zdE=7nUcBGCqw@mail.gmail.com>
To: Simon Hobson <linux@thehobsons.co.uk>
Cc: IPv6 Operations <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000964ef30596005ef7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_7rMu-rmeL5ZsySWhpl8E1hsAt8>
Subject: Re: [v6ops] out-of-focus: why DHCPv6 breaks Android computers?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Oct 2019 22:53:37 -0000

On Mon, Oct 28, 2019, 16:11 Simon Hobson <linux@thehobsons.co.uk> wrote:

> Could an alternative explanation be along the lines of :
> User turns on DHCPv6 server -> CPE configures it's RA service to label the
> network as managed
> End user device receives RA and finds the network is managed -> it turns
> off SLAAC
> As the EU device has disabled SLAAC and doesn't support DHCPv6, it now
> loses IPv6 connectivity
>

No. Managed and autoconfig are separate and independent parts of the RA. We
turn the former on and the latter off on most subnets at work, but I
definitely know from experience that if you turn both on operating systems
that support both will usually happily configure *both* a DHCPv6 *and* a
SLAAC address.

>

v2.23.0 | Report a Bug | By Email