From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f182.google.com ([209.85.215.182]:39682 "EHLO mail-pg1-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725826AbfH3Akf (ORCPT ); Thu, 29 Aug 2019 20:40:35 -0400 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: ANNOUNCE: rpld an another RPL implementation for Linux From: Reuben Hawkins In-Reply-To: Date: Thu, 29 Aug 2019 17:40:30 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: Sender: linux-wpan-owner@vger.kernel.org List-ID: To: Alexander Aring Cc: "open list:NETWORKING [GENERAL]" , Michael Richardson , Jamal Hadi Salim , Robert Kaiser , Martin Gergeleit , Kai Beckmann , koen@bergzand.net, linux-wpan - ML , BlueZ development , Stefan Schmidt , sebastian.meiling@haw-hamburg.de, Marcel Holtmann , Werner Almesberger , Jukka Rissanen There is a COPYRIGHT file in radvd which I just read for the first time toda= y. It=E2=80=99s been there for 19+ years. Sounds very BSD to me. I=E2=80=99v= e been maintainer for 9 years. As far as I=E2=80=99m concerned, you can do w= ith the code whatever you like. Good luck. =F0=9F=91=8D=20 Sent from my iPhone > On Aug 29, 2019, at 2:57 PM, Alexander Aring wrote:= >=20 > Hi, >=20 > 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. >=20 > 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. >=20 > I changed a little bit the dependencies from radvd (because fancy new thin= gs): >=20 > - lua for config handling > - libev for event loop handling > - libmnl for netlink handling >=20 > The code is available at: >=20 > https://github.com/linux-wpan/rpld >=20 > 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. >=20 > 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). >=20 > 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. >=20 > 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). >=20 > 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. >=20 > 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. >=20 > 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. >=20 > - Alex >=20 > [0] https://tools.ietf.org/html/rfc6550 > [1] https://github.com/reubenhwk/radvd > [2] https://github.com/AnimaGUS-minerva/unstrung