Linux-Bluetooth Archive on
 help / color / Atom feed
From: Stefan Schmidt <>
To: Alexander Aring <>,
	"open list:NETWORKING [GENERAL]" <>
Cc: Michael Richardson <>,
	Jamal Hadi Salim <>,
	Robert Kaiser <>,
	Martin Gergeleit <>,
	Kai Beckmann <>,, linux-wpan - ML <>,,
	BlueZ development <>,,
	Marcel Holtmann <>,
	Werner Almesberger <>,
	Jukka Rissanen <>
Subject: Re: ANNOUNCE: rpld an another RPL implementation for Linux
Date: Thu, 12 Sep 2019 13:14:55 +0200
Message-ID: <> (raw)
In-Reply-To: <>

Hello Alex.

On 29.08.19 23:57, Alexander Aring wrote:
> 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:

I finally had a first look at it and played around a little bit.

How do you want to review patches for this? Pull requests on the github
repo or patches send on the linux-wpan list?

So far just some basic stuff I stumbled over when playing with it. Build
fixes (SCOPE_ID and different lua pkgconfig namings), leak fixes to
config.c as well as a travis setup to get building on CI as well as
submitting to Coverity scan service (the later two are already tested in
practice with some dev branches I pushed to the github repo, hope you
don't mind).

Stefan Schmidt

      parent reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 21:57 Alexander Aring
2019-08-30  0:40 ` Reuben Hawkins
2019-09-12 11:14 ` Stefan Schmidt [this message]

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on

Archives are clonable:
	git clone --mirror linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ \
	public-inbox-index linux-bluetooth

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox