IETF Logo Mail Archive

[Snac] Router using Ipv6 prefix length = 67

"Collins, Alan" <alaclli@amazon.com> Sun, 04 June 2023 17:33 UTC

Return-Path: <prvs=5126c291a=alaclli@amazon.com>
X-Original-To: snac@ietfa.amsl.com
Delivered-To: snac@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47B00C14CF13 for <snac@ietfa.amsl.com>; Sun, 4 Jun 2023 10:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level:
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwpVSZ0C5jmp for <snac@ietfa.amsl.com>; Sun, 4 Jun 2023 10:33:28 -0700 (PDT)
Received: from smtp-fw-6002.amazon.com (smtp-fw-6002.amazon.com [52.95.49.90]) (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 EF2E4C14CF12 for <snac@ietf.org>; Sun, 4 Jun 2023 10:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1685900008; x=1717436008; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=iEWcTRSpcAPHKVjGmHCwXyP4Wp3u2NYYvbMO2leXIJI=; b=gggv+eA/jc9e6nUe2YR/OmkFEiPqyBgEa0dUctIQyau6ChXk9QY5pB2G 3TKrQFs4nZ+Rg1ETC5QiMk+XM3dUI0tWG4Xvv9Z7fqs+hnuWjTj2rk7vr SdZ4vHjzD3TaloFMWfOKNlOe2gAwHu25RtadnlijFGpP/h1RNxwPCsogQ Y=;
X-Amazon-filename: image001.png, image002.png
X-IronPort-AV: E=Sophos;i="6.00,217,1681171200"; d="png'150?scan'150,208,217,150";a="336506866"
Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-pdx-2b-m6i4x-189d700f.us-west-2.amazon.com) ([10.43.8.6]) by smtp-border-fw-6002.iad6.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Jun 2023 17:33:27 +0000
Received: from EX19MTAUWB001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan2.pdx.amazon.com [10.236.137.194]) by email-inbound-relay-pdx-2b-m6i4x-189d700f.us-west-2.amazon.com (Postfix) with ESMTPS id 77B0F40DE6; Sun, 4 Jun 2023 17:33:25 +0000 (UTC)
Received: from EX19D034UWB003.ant.amazon.com (10.13.138.30) by EX19MTAUWB001.ant.amazon.com (10.250.64.248) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Sun, 4 Jun 2023 17:33:25 +0000
Received: from EX19D034UWB003.ant.amazon.com (10.13.138.30) by EX19D034UWB003.ant.amazon.com (10.13.138.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Sun, 4 Jun 2023 17:33:24 +0000
Received: from EX19D034UWB003.ant.amazon.com ([fe80::9a47:296b:f13a:e721]) by EX19D034UWB003.ant.amazon.com ([fe80::9a47:296b:f13a:e721%6]) with mapi id 15.02.1118.026; Sun, 4 Jun 2023 17:33:24 +0000
From: "Collins, Alan" <alaclli@amazon.com>
To: "snac@ietf.org" <snac@ietf.org>
CC: Gabe Kassel <gabe@eero.com>
Thread-Topic: Router using Ipv6 prefix length = 67
Thread-Index: AQHZlWhSi1+2QKWeDUOfJ7mKiUdmMa96dSmA
Date: Sun, 04 Jun 2023 17:33:24 +0000
Message-ID: <10B44E76-01E1-4A09-881D-2228B4E07508@amazon.com>
References: <39BE8173-F4D2-4B8C-A136-A5A7F441B3BF@amazon.com>
In-Reply-To: <39BE8173-F4D2-4B8C-A136-A5A7F441B3BF@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.13.138.196]
Content-Type: multipart/related; boundary="_005_10B44E7601E14A09881D2228B4E07508amazoncom_"; type="multipart/alternative"
MIME-Version: 1.0
Precedence: Bulk
Archived-At: <https://mailarchive.ietf.org/arch/msg/snac/0wzbsMx_1uHFHEdw-cftEufoi-k>
Subject: [Snac] Router using Ipv6 prefix length = 67
X-BeenThere: snac@ietf.org
X-Mailman-Version: 2.1.39
List-Id: "Mailing list for discussing problems relating to the automatic connection of stub networks to existing infrastructure networks. " <snac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/snac>, <mailto:snac-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/snac/>
List-Post: <mailto:snac@ietf.org>
List-Help: <mailto:snac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/snac>, <mailto:snac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jun 2023 17:33:29 -0000

Hello Ted, Jonathan.

                We have multiple test setups testing Matter over Thread back-to-back pairing while connected to infrastructure using different (hundreds) of Wifi AP with default settings. The setup:

[cid:image001.png@01D996CF.FD30C9D0]
Recently, while using Netgear WNP3000 , the Matter pairing failed. The non-thread matter controller is not getting an IPv6 global address, so even that the routing table contains the prefix to reach into the Thread BR, the IP stack does not allow it without a global IP of its own.

Thread BR is only sending icmpv6 RA with RIO. The PIO is not included because there is another router in the network already sending PIO.
However, since that PIO has length = 67, the non-Thread matter controller won’t use it to create a global IP. It’s not even sending NS for DAD.

[cid:image002.png@01D996CF.FD30C9D0]

We think the abnormal ipv6 PIO prefix RA is from the backend Cisco OUI MAC address. We are investigating.

However, this opens an opportunity to create a more robust behavior from Thread BR, to add more logic into processing the existing PIO before deciding not to send a PIO of its own.

Thank you in advance for looking into this.

Cheers,
Alan Collins

v2.23.0 | Report a Bug | By Email