Re: [v6ops] new draft: draft-elkins-v6ops-multicast-virtual-nodes

Nick Hilliard <nick@foobar.org> Sat, 20 September 2014 09:16 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE5A1A03A9 for <v6ops@ietfa.amsl.com>; Sat, 20 Sep 2014 02:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=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 t6RNu8i4BkWZ for <v6ops@ietfa.amsl.com>; Sat, 20 Sep 2014 02:16:50 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (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 875A51A00DF for <v6ops@ietf.org>; Sat, 20 Sep 2014 02:16:50 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from vpn-251.int.inex.ie (vpn-251.int.inex.ie [193.242.111.251]) (authenticated bits=0) by mail.netability.ie (8.14.9/8.14.5) with ESMTP id s8K9GCP4012683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 20 Sep 2014 10:16:37 +0100 (IST) (envelope-from nick@foobar.org)
Message-ID: <541D45DB.5010703@foobar.org>
Date: Sat, 20 Sep 2014 10:16:11 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: Nalini Elkins <nalini.elkins@insidethestack.com>, Andrew 👽 Yourtchenko <ayourtch@gmail.com>
References: <201409191147.s8JBl1Fe016458@irp-lnx1.cisco.com> <CAPi140O_WkcS9uFCSK0+tVDF3Z1sB4_UF5Zv9kpNEMh7m94Vww@mail.gmail.com> <1411154671.21942.YahooMailNeo@web125102.mail.ne1.yahoo.com> <CAPi140Ob+TeDyYfw_1A2Q55gEF5-rNrLynQ1LkGHOVnGcNcpLA@mail.gmail.com> <1411164118.44574.YahooMailNeo@web125106.mail.ne1.yahoo.com> <CAPi140M+RjEr_edAXZBuUv9dYTztQUHq5J6rTd6Ca0qHcuhrCA@mail.gmail.com> <1411170563.16646.YahooMailNeo@web125101.mail.ne1.yahoo.com> <CAPi140PC_rjguOVpyes74=by-Y504hcpsbWFxVfQ8GiudbR6sA@mail.gmail.com> <1411185266.51203.YahooMailNeo@web125102.mail.ne1.yahoo.com>
In-Reply-To: <1411185266.51203.YahooMailNeo@web125102.mail.ne1.yahoo.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/A1-k56bbXu-WJODf3AArMwqs4jU
Cc: "draft-elkins-v6ops-multicast-virtual-nodes@tools.ietf.org" <draft-elkins-v6ops-multicast-virtual-nodes@tools.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] new draft: draft-elkins-v6ops-multicast-virtual-nodes
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 20 Sep 2014 09:16:52 -0000

On 20/09/2014 04:54, Nalini Elkins wrote:
> On Windows, I did a :  ping ff02::1 -n 10
>
> where the -n is the count.
>
> So for each 1 ping request I send out, each of my neighbors sends me 10
> responses.

The "-n" parameter specifies how many icmp echo requests are sent out, not 
how many replies are solicited.

> Such as what?  BTW, I have sent Nick the trace & can send to you as well.

The pcap file shows 10 icmp echo requests and 2840 echo replies, and that 
the echo replies used 284 unique link-local ipv6 addresses associated with 
284 unique MAC addresses.  This looks both correct and consistent with the 
figures in the draft.  The lesson is that if you have a lot of ipv6 hosts 
on the same broadcast domain, you will get lots of echo replies from a ping 
to ff02::1.

Nalini, if you feel that there is an issue here, you should talk to your 
hosting provider and suggest that they don't put as many ipv6 hosts on the 
same broadcast domain.  This isn't a protocol level problem: it's expected 
and correct behaviour.

Nick