IETF Logo Mail Archive

Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and GUA

<holger.metschulat@telekom.de> Fri, 14 July 2017 10:33 UTC

Return-Path: <prvs=361b95baf=holger.metschulat@telekom.de>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1906131B21 for <v6ops@ietfa.amsl.com>; Fri, 14 Jul 2017 03:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.101
X-Spam-Level:
X-Spam-Status: No, score=-7.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 dhEJMzW2jJOH for <v6ops@ietfa.amsl.com>; Fri, 14 Jul 2017 03:33:43 -0700 (PDT)
Received: from mailout23.telekom.de (MAILOUT23.telekom.de [80.149.113.253]) (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 7117A131B24 for <v6ops@ietf.org>; Fri, 14 Jul 2017 03:33:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1500028422; x=1531564422; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=C2g59kX2r4AXePlOHTA+dye5oxWEU5NYvdegwKb65aA=; b=0t0db79OJtyFbTBAgk5V/C9OB8kSgTbZhNlJ69qiCJfDxwrrftgWPkrZ LxbBy4rS3koilV6l9tx4AWayQt0nLl28w7+wKbZsqlbquFkHiBtH6wKI/ q69rkvrcu0z5fTzFYs0leBud57al7kwqKknpPztytBsGQokuTaVfcsfZC 6NJ9tJE34ky+MqVy4GRYzT1Jjjj7PuJeiQIwbjvWouAewwv36NC/7xtZU u9xXGyJH/TIbJ+wO0nkqKBIfNKgop/onG3lWFBFQnsCg9cW9fOD1Dgx4p Fkv9KpbGZoxrJgmmAMLmWEwFQ//0+O6pBELJ5+BdMPv+dKbbSVr/ICHc9 A==;
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jul 2017 12:33:40 +0200
X-IronPort-AV: E=Sophos;i="5.40,358,1496095200"; d="scan'208";a="1354541446"
Received: from he199743.emea1.cds.t-internal.com ([10.169.119.51]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES256-SHA; 14 Jul 2017 12:33:23 +0200
Received: from HE199744.EMEA1.cds.t-internal.com (10.169.119.52) by HE199743.emea1.cds.t-internal.com (10.169.119.51) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 14 Jul 2017 12:33:04 +0200
Received: from HE199744.EMEA1.cds.t-internal.com ([fe80::3435:eb51:d048:836d]) by HE199744.emea1.cds.t-internal.com ([fe80::3435:eb51:d048:836d%26]) with mapi id 15.00.1263.000; Fri, 14 Jul 2017 12:33:04 +0200
From: holger.metschulat@telekom.de
To: v6ops@ietf.org
Thread-Topic: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and GUA
Thread-Index: AQHS+wPtmFRdIBFLB06xmR8ahfsFoKJP8KaAgAAFnYCAAyt2oA==
Date: Fri, 14 Jul 2017 10:33:04 +0000
Message-ID: <2ff7a4128d1d424f84c35ddcd3eec0fe@HE199744.emea1.cds.t-internal.com>
References: <937f22f6-e4b7-b398-9df9-79c36ea2d7ee@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002E21@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <a67eb7d0-be6a-f158-b05c-fda0f38e09d6@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002EF9@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <1be23f5b-f449-9924-8322-f21c4ccbd09e@gmail.com> <787AE7BB302AE849A7480A190F8B93300A002F95@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <2c325097-651e-501c-747a-e7a322c3d844@gmail.com> <787AE7BB302AE849A7480A190F8B93300A0032B6@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <6c43cf08-0bd6-daf4-ea9d-d52c34db2a8c@gmail.com> <CAKD1Yr1QLmjUqiEY92vFu9ZDEsVKqJwoZNhyEu+D0hQLEKkopQ@mail.gmail.com> <6727013e-b5c8-4bee-6127-9e0317b41c9f@gmail.com>
In-Reply-To: <6727013e-b5c8-4bee-6127-9e0317b41c9f@gmail.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.157.171.228]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/yIjIFHuYyPAVnb9q4TepOTxtB-Y>
Subject: Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and GUA
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 14 Jul 2017 10:33:45 -0000

See below with [HM]
-----Ursprüngliche Nachricht-----
Von: v6ops [mailto:v6ops-bounces@ietf.org] Im Auftrag von Alexandre Petrescu
Gesendet: Mittwoch, 12. Juli 2017 14:04
An: Lorenzo Colitti
Cc: v6ops@ietf.org
Betreff: Re: [v6ops] RFC6459 "IPv6 in 3GPP" - the IID in the LL address and GUA


I see it with tcpdump on a Sierra IoT module running a form of embedded
linux, gnueabi is the target of the cross compiler.  It uses /dev/ttyAT
device.
[HM] WWAN Modem Chipsets perform some kind of translation of packets, especially ICMPv6 packets, between the interface to the computer and the interface towards the provider network. The reason is that the computer wants to see an Ethernet broadcast interface, but the provider interface is point-to-point. For example, the computer needs Neighbor Discovery but this is not available on the provider interface. The provider's network device doesn't have a MAC address either, so the modem chipset emulates this missing MAC to the computer.

So what you capture on WWAN0 (or however your computer interface is named) is not what actually goes over the air.

Holger

v2.23.0 | Report a Bug | By Email