Re: IPv4 traffic on "ietf-v6ONLY"

joel jaeggli <joelja@bogus.com> Wed, 15 November 2017 03:11 UTC

Return-Path: <joelja@bogus.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 45F92126C22 for <ipv6@ietfa.amsl.com>; Tue, 14 Nov 2017 19:11:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 D7skWEwo34Rj for <ipv6@ietfa.amsl.com>; Tue, 14 Nov 2017 19:11:55 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 5C6F01292D3 for <ipv6@ietf.org>; Tue, 14 Nov 2017 19:11:54 -0800 (PST)
Received: from mb.local ([IPv6:2001:67c:370:1998:78fa:30c8:8d1d:2a52]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id vAF3BlJ7039629 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 15 Nov 2017 03:11:49 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2001:67c:370:1998:78fa:30c8:8d1d:2a52] claimed to be mb.local
Subject: Re: IPv4 traffic on "ietf-v6ONLY"
To: Lee Howard <lee@asgard.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, ipv6@ietf.org
References: <f9805855-68cf-a3e8-a13f-c6ac31b09058@gmail.com> <bbd4e1d2-047f-6758-76f8-fd591c51dad7@gmail.com> <D631CE54.8C0F5%lee@asgard.org>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <81557db0-2335-f2f8-530c-4648ca5c85fd@bogus.com>
Date: Wed, 15 Nov 2017 11:11:01 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:56.0) Gecko/20100101 Thunderbird/56.0
MIME-Version: 1.0
In-Reply-To: <D631CE54.8C0F5%lee@asgard.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8Ewg5RmNvY5B-s35VBNMCbBKgQk>
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 03:11:57 -0000

On 11/15/17 10:59, Lee Howard wrote:
> 
> 
> 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?

Ah but it does, because in the absence of ipv4 network instruction you
still build an adhoc network, just as you do for ipv6.

J@mb:nobackup$dns-sd  -G v4 "mb.local"
DATE: ---Wed 15 Nov 2017---
11:04:02.802  ...STARTING...
Timestamp     A/R Flags if Hostname
Address                                      TTL
11:04:02.804  Add     2  5 mb.local.
169.254.36.108                               120

J@mb:nobackup$dns-sd  -G v4 "Zamboni.local"
DATE: ---Wed 15 Nov 2017---
11:06:42.643  ...STARTING...
Timestamp     A/R Flags if Hostname
Address                                      TTL
11:06:42.644  Add     2  5 zamboni.local.
169.254.150.104                              120

if you turn off your ipv4 stack you'll no longer do that.

There is some (possibly misguided) assumption that if you have only
adhoc networking available for a given address faily that your network
is broken. In fact it is not, it is working.


joel

> 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
>> --------------------------------------------------------------------
>>
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>