Re: IPv4 traffic on "ietf-v6ONLY"

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 17 November 2017 04:50 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E959F120727 for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 20:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 RWYeG141XLZm for <ipv6@ietfa.amsl.com>; Thu, 16 Nov 2017 20:50:08 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2651120726 for <ipv6@ietf.org>; Thu, 16 Nov 2017 20:50:08 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id vAH4o7kx024230 for <ipv6@ietf.org>; Fri, 17 Nov 2017 05:50:07 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 16808200DA8 for <ipv6@ietf.org>; Fri, 17 Nov 2017 05:50:07 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 01DD6200C9E for <ipv6@ietf.org>; Fri, 17 Nov 2017 05:50:07 +0100 (CET)
Received: from [132.166.84.12] ([132.166.84.12]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id vAH4o5rt021250 for <ipv6@ietf.org>; Fri, 17 Nov 2017 05:50:06 +0100
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
To: ipv6@ietf.org
References: <f9805855-68cf-a3e8-a13f-c6ac31b09058@gmail.com> <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com> <D631CE54.8C0F5%lee@asgard.org> <m1eEvEP-0000G3C@stereo.hq.phicoh.net> <D75288D5-B571-46EB-A35E-0DBD79F930E5@google.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b05f3549-585f-f834-2df3-3b458f67ba2d@gmail.com>
Date: Fri, 17 Nov 2017 05:50:04 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <D75288D5-B571-46EB-A35E-0DBD79F930E5@google.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jT7CwR0OOq0wv1Joex63Mw9AivA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Nov 2017 04:50:13 -0000


Le 15/11/2017 à 20:15, james woodyatt a écrit :
> On Nov 15, 2017, at 02:47, Philip Homburg 
> <pch-ipv6-ietf-4@u-1.phicoh.com <mailto:pch-ipv6-ietf-4@u-1.phicoh.com>> 
> wrote:
>>
>> The safest option to do that is a DHCPv4 option that says 'no IPv4 
>> service here, go away'.
> 
> Better: extend ARP with a signal that says, “ARP is not welcome here."

During changes between the 3 SSIDs I noticed often the message "Windows 
detected an IP address conflict" popped up.  The explanation says that 
another computer on the network has the same address, contact the 
sysadmin, and more details are available.

This makes wonder whether someone put a computer there that responds to 
all ARP resolution requests for LLs 169, claiming them all.

It happens systematically when changing the ESSID from "ietf" to 
"ietf-v6ONLY".  If, prior to that change, I disable the IPv4 checkbox in 
interface Properties, the message does not pop up.

However, this message appears also when changing attachment from SSID 
"ietf-v6ONLY" to "ietf".

Alex

> 
> --james woodyatt <jhw@google.com <mailto:jhw@google.com>>
> 
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>