IETF Logo Mail Archive

RE: ICMPv6 question

"Manfredi, Albert E" <albert.e.manfredi@boeing.com> Fri, 01 September 2017 00:44 UTC

Return-Path: <albert.e.manfredi@boeing.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 3B8B3132E6A for <ipv6@ietfa.amsl.com>; Thu, 31 Aug 2017 17:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 gtBaRUPH6Og2 for <ipv6@ietfa.amsl.com>; Thu, 31 Aug 2017 17:44:43 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 BF530132E7D for <ipv6@ietf.org>; Thu, 31 Aug 2017 17:44:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v810igsC045206; Thu, 31 Aug 2017 17:44:43 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v810idXv045189 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <ipv6@ietf.org>; Thu, 31 Aug 2017 17:44:39 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 31 Aug 2017 17:44:38 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1320.000; Thu, 31 Aug 2017 17:44:38 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, 6man WG <ipv6@ietf.org>
Subject: RE: ICMPv6 question
Thread-Topic: ICMPv6 question
Thread-Index: AdMirYG7EwN54XmxT+uCHTYv5GBqHgAAw0HQAACxZAAAAdWkAA==
Date: Fri, 01 Sep 2017 00:44:38 +0000
Message-ID: <ed43135fad224edbac43c045e64eeb36@XCH15-06-11.nw.nos.boeing.com>
References: <952aab1a2c824a79b98a3f9d2b3a473a@XCH15-06-08.nw.nos.boeing.com> <956f0877cf0f4d2a9e67cbf5b8bdeec6@XCH15-06-11.nw.nos.boeing.com> <b8a0cd9adfbb4c2d8c92dddc49b41cf3@XCH15-06-08.nw.nos.boeing.com>
In-Reply-To: <b8a0cd9adfbb4c2d8c92dddc49b41cf3@XCH15-06-08.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_mx5WEQt9IE75qfsnyzhTpgr6S4>
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, 01 Sep 2017 00:44:45 -0000

-----Original Message-----
From: Templin, Fred L 

> I am assuming that the bogus packet uses a correct MAC destination
> address but with an incorrect IPv6 destination address. So, the packet
> gets handed up to the IPv6 layer.

Or maybe there's another more or less legitimate reason, Fred. Ethernet in promiscuous mode. In which case, it's working as intended. Still, like Mark showed aptly, a destination host wouldn't be sending host unreachable ICMP messages.

Bert

v2.23.0 | Report a Bug | By Email