Re: [v6ops] DHCPv6 PD client on cellular on some IoT platform

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 24 May 2017 21:21 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 AFC53129B21 for <v6ops@ietfa.amsl.com>; Wed, 24 May 2017 14:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 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, 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 WM36WxLvXqNh for <v6ops@ietfa.amsl.com>; Wed, 24 May 2017 14:21:37 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 3C03C127863 for <v6ops@ietf.org>; Wed, 24 May 2017 14:21:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v4OLLaA6050867; Wed, 24 May 2017 14:21:36 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v4OLLWNE050453 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Wed, 24 May 2017 14:21:32 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 24 May 2017 14:21:31 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Wed, 24 May 2017 14:21:31 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] DHCPv6 PD client on cellular on some IoT platform
Thread-Index: AQHS1LAKWsHR+akJJEGy3XAfHLYfKKID+7lQ
Date: Wed, 24 May 2017 21:21:31 +0000
Message-ID: <1e7de6487fef4959b9177993c7581e3e@XCH15-06-08.nw.nos.boeing.com>
References: <7537deef-8f87-5187-1e44-595ac63a16ca@gmail.com>
In-Reply-To: <7537deef-8f87-5187-1e44-595ac63a16ca@gmail.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/v6ops/1oOvwQP2yBg95JMuz8vvXsF-oVA>
Subject: Re: [v6ops] DHCPv6 PD client on cellular on some IoT platform
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: Wed, 24 May 2017 21:21:39 -0000

Hi Alex,

We have been doing DHCPv6 PD on Androids for a long time. DHCPv6 messaging
is via a tunnel over the cellular and WiFi links. The DHCPv6 client app was easy to
implement and requires just a small amount of code and a few DHCPv6 messages.
The DHCPv6 server we are using is from ISC.

Thanks - Fred

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Wednesday, May 24, 2017 10:06 AM
> To: v6ops@ietf.org
> Subject: [v6ops] DHCPv6 PD client on cellular on some IoT platform
> 
> Hello,
> 
> We discussed extensively about the potential use of DHCPv6 Prefix
> Delegation on cellular links.
> 
> The chicken issue is the lack of DHCPv6 PD software on typical User
> Equipment.  For example, there is no DHCPv6-PD app on Android.  The egg
> issue is the lack of operator support of DHCPv6-PD towards the User
> Terminal.  For example, there is no cellular operator answering to
> DHCPv6-PD requests issued by the User Terminal.
> 
> To address the chicken issue, we started with an ISC DHCP open software
> client, which does implement Prefix Delegation.  It can be
> (cross)compiled on various platforms; then type "./dhclient -6 -P"; this
> sends an DHCPv6 Solicit Identity Associtaion for Prefix Delegation
> message on the interface.
> 
> However, whereas this software runs ok on interfaces such as Ethernet,
> USBnet and WiFi interfaces, it breaks if run on the cellular interface
> of some IoT cellular platform.  The error can be corrected by the
> quick-and-dirty solution below.
> 
> Alex
> 
> ------------------------------------------------------------------------
> The error says "//UNSUPPORTED DEVICE TYPE 503 FOR RMNET0."
> dhcp-4.3.5
> ./common/lpf.c
> line number: 551
> 
> //default:
> //      log_fatal("Unsupported device type %ld for \"%s\"",
> //                (long int)sa->sa_family, name);
>    default:
>          hw->hlen = 7;
>          hw->hbuf[0] = HTYPE_ETHER;
>          memcpy(&hw->hbuf[1], sa->sa_data, 6);
>    break;
> 
> (two programmers worked this out).
> 
> Alex
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops