linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Alexander Aring <alex.aring@gmail.com>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Cc: Michael Richardson <mcr@sandelman.ca>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Robert Kaiser <robert.kaiser@hs-rm.de>,
	Martin Gergeleit <martin.gergeleit@hs-rm.de>,
	Kai Beckmann <kai.beckmann@hs-rm.de>,
	koen@bergzand.net, linux-wpan - ML <linux-wpan@vger.kernel.org>,
	reubenhwk@gmail.com,
	BlueZ development <linux-bluetooth@vger.kernel.org>,
	sebastian.meiling@haw-hamburg.de,
	Marcel Holtmann <marcel@holtmann.org>,
	Werner Almesberger <werner@almesberger.net>,
	Jukka Rissanen <jukka.rissanen@linux.intel.com>
Subject: Re: ANNOUNCE: rpld an another RPL implementation for Linux
Date: Thu, 12 Sep 2019 13:14:55 +0200	[thread overview]
Message-ID: <78e83575-4bae-cb8b-be8c-c108ac488a37@datenfreihafen.org> (raw)
In-Reply-To: <CAB_54W7h9ca0UJAZtk=ApPX-2ZCvzu4774BTFTaB5mtkobWCtw@mail.gmail.com>

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:
> 
> https://github.com/linux-wpan/rpld

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).

regards
Stefan Schmidt

      parent reply	other threads:[~2019-09-12 11:15 UTC|newest]

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

Reply instructions:

You may reply publicly 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=78e83575-4bae-cb8b-be8c-c108ac488a37@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --cc=alex.aring@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=jukka.rissanen@linux.intel.com \
    --cc=kai.beckmann@hs-rm.de \
    --cc=koen@bergzand.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=martin.gergeleit@hs-rm.de \
    --cc=mcr@sandelman.ca \
    --cc=netdev@vger.kernel.org \
    --cc=reubenhwk@gmail.com \
    --cc=robert.kaiser@hs-rm.de \
    --cc=sebastian.meiling@haw-hamburg.de \
    --cc=werner@almesberger.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).