IETF Logo Mail Archive

Re: IPv4 traffic on "ietf-v6ONLY"

Lee Howard <lee@asgard.org> Wed, 15 November 2017 02:59 UTC

Return-Path: <lee@asgard.org>
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 4DFCC129438 for <ipv6@ietfa.amsl.com>; Tue, 14 Nov 2017 18:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.698
X-Spam-Level:
X-Spam-Status: No, score=-4.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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 XAyxxsucnKk3 for <ipv6@ietfa.amsl.com>; Tue, 14 Nov 2017 18:59:16 -0800 (PST)
Received: from atl4mhob23.registeredsite.com (atl4mhob23.registeredsite.com [209.17.115.117]) (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 A076B127137 for <ipv6@ietf.org>; Tue, 14 Nov 2017 18:59:16 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob23.registeredsite.com (8.14.4/8.14.4) with ESMTP id vAF2xCQn128136 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ipv6@ietf.org>; Tue, 14 Nov 2017 21:59:14 -0500
Received: (qmail 31339 invoked by uid 0); 15 Nov 2017 02:59:12 -0000
X-TCPREMOTEIP: 31.133.153.67
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?31.133.153.67?) (lee@asgard.org@31.133.153.67) by 0 with ESMTPA; 15 Nov 2017 02:59:11 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Wed, 15 Nov 2017 10:59:06 +0800
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
From: Lee Howard <lee@asgard.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ipv6@ietf.org
Message-ID: <D631CE54.8C0F5%lee@asgard.org>
Thread-Topic: IPv4 traffic on "ietf-v6ONLY"
References: <f9805855-68cf-a3e8-a13f-c6ac31b09058@gmail.com> <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com>
In-Reply-To: <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kBfCzh07dWtH3ZmzMjnQb2bueEU>
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: Wed, 15 Nov 2017 02:59:18 -0000


On 11/15/17, 10:44 AM, "ipv6 on behalf of Brian E Carpenter"
<ipv6-bounces@ietf.org on behalf of brian.e.carpenter@gmail.com> wrote:

>On 15/11/2017 15:13, Alexandre Petrescu wrote:
>> There is much IPv4 traffic on the "ietf-v6ONLY" ESSID.
>
>Also on the DNS64 network. But it is all one-way, you
>will notice. No replies as far as I can see. Most of them
>are sourced from 169.254.*.*, but there are some oddities such as
>31.130.227.98	224.0.0.1	IGMPv2	42	Membership Query, general


Does that return us to the question of how to tell hosts that IPv4 doesn’t
live here, and to stop trying?

Lee

>
>I have a couple of Wireshark capture files if anyone cares.
>
>   Brian
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email