Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2911164ybl; Thu, 29 Aug 2019 14:58:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqxYC7YTnpntellKRgY+TxZDIXkOdsyz2fjtT65l3cqIwkRLQP/5lXIWnIQK2QsQ47I4YOrY X-Received: by 2002:a62:86cf:: with SMTP id x198mr14279067pfd.195.1567115916457; Thu, 29 Aug 2019 14:58:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567115916; cv=none; d=google.com; s=arc-20160816; b=ts9j3V5szIKXFCiH7rUr/dhfNcmlZhAHkicp2vY46/ffQ6Q1RMqoRx0QuPBBjvqdoz fmXvC2P0JA8+k2dcBbdacmueFDoMUzbI3SqDz69Yu3TattIKL9zTtvQSlDL5AAA4OXmG Ms5EvYbXQMVz0tMLWexDrgzXaWGi/KIl+UFjItnzt542WIsCdUHS2utCHDzWoz5tNHvh bR8vg/b+A2G5a8fIqq36nL+qMgwgFvLzL4levqYm6pLcbQIkYVNjdYj4AHMKs3+BhRMm imMs8oR2s2TKjbcsZtHbCTSo/H2S8j+q9msPDBzZzCnxnZVEOqHNzW8BXtrup0873ccE Ebrw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :mime-version:dkim-signature; bh=JByFaSedVJm/2cv0gwp6K7M2K2CazvyjJt9MUumRGx4=; b=ddIWjzkqvmOB41BgGiaKWBV4rZFpsontsBGBKvtPLCdW+Dbd9p9OuF9n1bnJETv7dj 2u9ONXbsNV+sI5M0D27gtM7D2dC63hsK1lO7mpJsataSDwRUuqMGhINAFiTNKpzgi0MW PXRP16ReTHfqaW4taOM3zEGIjGe1pFeazXp3X2S3aOMh+r3Co0qDpx41XNGph7z5unGB 00nnP+yiSzcifx4tfOYys74Hn/wXq9p1jcp5lZY3KwN7KNsrEg5c6bGruHGvV/4tF16c /MW1W/kDihLB+42l4Lw1KIP6OU7WTq8tMmuJ3hPu5eMJH+3x/S9f3xDowdlgulnWTc9M Kf4w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="PGZWM/rW"; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u19si3170702pgf.531.2019.08.29.14.58.08; Thu, 29 Aug 2019 14:58:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b="PGZWM/rW"; spf=pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727996AbfH2V6F (ORCPT + 99 others); Thu, 29 Aug 2019 17:58:05 -0400 Received: from mail-oi1-f193.google.com ([209.85.167.193]:34997 "EHLO mail-oi1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727959AbfH2V6F (ORCPT ); Thu, 29 Aug 2019 17:58:05 -0400 Received: by mail-oi1-f193.google.com with SMTP id a127so3820541oii.2; Thu, 29 Aug 2019 14:58:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=JByFaSedVJm/2cv0gwp6K7M2K2CazvyjJt9MUumRGx4=; b=PGZWM/rWRRXrT7I69KY9OtlW0+bpycNW2Lz+I6v/54eGdukUFNGSFxX4amcUykbZ5C yXWfg7gIlzAspW89k5F1UtF2/SGL1jCmtUd2h8K1yW2PZWXrVTijgCjKzGrPHl62ecRz xY+iqnUzV6zlDWJFYn7pojo6jgPm8JlIbKb2NA0l2WSoyAq1owLnDewzvOKlZgvAahvs mD5Wp78Mndf3PgCzZn2sgcoYkPKjd2wM0bD5FIjIQHkAxlHIivDVulUBfstRaZXplW1x JPfs1lg6Le+b7QZc2MIflRAFQw5+4DsWlCMXDMsquy8GIjuY3whpSX4/5awQLDbTRHTN qagw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=JByFaSedVJm/2cv0gwp6K7M2K2CazvyjJt9MUumRGx4=; b=mgOfUjlpDHSmT3WdBHVMtt1bpV06qHiCQplM57pPaR1SHTVMHikoxCtKkZ51M2XPts jc82IqKNryHPwU3BVaaLpQWAT+mOxauMixmesvHE86JMU/AzvuwN7BLO/sYff3+Qt/4y Zlu8MZDWD+3/R5iI89CWscRtCuI46Gsc7DapPjLN30ph8sD3xeSwePPY7gUXdeq1zFfz Tsft8kxg7GADfcrjTj/tTopOKr8SKkbky8KfY4+b6jyJiC1dAf3WjG+nb4+eax31ha0s KO7d/FTle9jx4J4Fi4G+rI4E2ctBgS3F2CN0UOit2f5bGwyvYiywur89sWyDCS+bEQMr kl4g== X-Gm-Message-State: APjAAAXUZapGYtDN9WwZwuCs1nrrJ1x9h52906+aUzH6g6zGkneCsxcA yDpy3Pt324QeEjK+Y+q03q8McvJfk7NJAxVhifXTifWQ X-Received: by 2002:aca:4b88:: with SMTP id y130mr8379252oia.157.1567115883743; Thu, 29 Aug 2019 14:58:03 -0700 (PDT) MIME-Version: 1.0 From: Alexander Aring Date: Thu, 29 Aug 2019 17:57:52 -0400 Message-ID: Subject: ANNOUNCE: rpld an another RPL implementation for Linux To: "open list:NETWORKING [GENERAL]" Cc: Michael Richardson , Jamal Hadi Salim , Robert Kaiser , Martin Gergeleit , Kai Beckmann , koen@bergzand.net, linux-wpan - ML , reubenhwk@gmail.com, BlueZ development , Stefan Schmidt , sebastian.meiling@haw-hamburg.de, Marcel Holtmann , Werner Almesberger , Jukka Rissanen Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi, I had some free time, I wanted to know how RPL [0] works so I did a implementation. It's _very_ basic as it only gives you a "routable" (is that a word?) thing afterwards in a very constrained setup of RPL messages. Took ~1 month to implement it and I reused some great code from radvd [1]. I released it under the same license (BSD?). Anyway, I know there exists a lot of memory leaks and the parameters are just crazy as not practical in a real environment BUT it works. I changed a little bit the dependencies from radvd (because fancy new things): - lua for config handling - libev for event loop handling - libmnl for netlink handling The code is available at: https://github.com/linux-wpan/rpld With a recent kernel (I think 4.19 and above) and necessary user space dependencies, just build it and run the start script. It will create some virtual IEEE 802.15.4 6LoWPAN interfaces and you can run traceroute from namespace ns0 (which is the RPL DODAG root) to any other node e.g. namespace ns5. With more knowledge of the scripts you can change the underlying topology, everybody is welcome to improve them. I will work more on it when I have time... to have at least something running means the real fun can begin (but it was already fun before). The big thing what everybody wants is source routing, which requires some control plane for RPL into the kernel to say how and when to put source routing headers in IPv6. I think somehow I know what's necessary now... but I didn't implemented it, this simple implementation just filling up routing tables as RPL supports storing (routing table) or non-storing (source routing) modes. People tells me to lookup frrouting to look how they do source routing, I will if I get the chance. It doesn't run on Bluetooth yet, I know there exists a lack of UAPI to figure out the linklayer which is used by 6LoWPAN. I need somehow a SLAVE_INFO attribute in netlink to figure this out and tell me some 6LoWPAN specific attributes. I am sorry Bluetooth people, but I think you are also more interested in source routing because I heard somebody saying it's the more common approach outside (but I never saw any other RPL implementation than unstrung running). Also I did something in my masters thesis to make a better parent selection, if this implementation becomes stable I can look to get this migrated. Please, radvd maintainer let me know if everything is okay from your side. As I said I reused some code from radvd. I also operate on ICMPv6 sockets. The same to Michael Richardson unstrung [2]. If there is anything to talk or you have complains, I can change it. Thanks, I really only wanted to get more knowledge about routing protocols and how to implement such. Besides all known issues, I still think it's a good starting point. - Alex [0] https://tools.ietf.org/html/rfc6550 [1] https://github.com/reubenhwk/radvd [2] https://github.com/AnimaGUS-minerva/unstrung