From: Michael Richardson <mcr@sandelman.ca>
To: Baptiste Clenet <bapclenet@gmail.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: RPl on Linux
Date: Wed, 09 Mar 2016 14:16:30 -0500 [thread overview]
Message-ID: <3583.1457550990@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAPpUg6MMTrwOiNC5M-e52zZpNkh58AQ7TC7x2p_fY916CvyHpw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
Baptiste Clenet <bapclenet@gmail.com> wrote:
>> Baptiste Clenet <bapclenet@gmail.com> wrote: > Thanks for your work
>> concerning 6lowpan, 802.15.4 and wpan tools, > that's great! I'm
>> wondering what the status of RPL mesh implementation > on Linux?
>>
>> There are few implementations, see for instance this article:
>> http://www.sixpinetrees.pl/2014/11/linux-rpl-router.html
>>
>> 1) Mine, which is at http://unstrung.sandelman.ca/ Currently storing
>> only; non-storing requires kernel work that is not yet done.
> Thanks for your answer, I see that you suggest to make it work with
> Contiki RPL implementation., a serious competitor to Contiki is RIOT,
> have you ever tried your RPL implementation with RIOT RPL?
We interoperated with RIOT-OS RPL back at the 6lo interop in November.
I haven't yet successfully flashed my own openmote with RIOT-OS (or OpenWSN).
[It's a JTAG/bootloader issue that I haven't had time to resolve...]
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 464 bytes --]
next prev parent reply other threads:[~2016-03-09 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 10:17 RPl on Linux Baptiste Clenet
2016-03-09 13:45 ` Michael Richardson
2016-03-09 13:53 ` Baptiste Clenet
2016-03-09 19:16 ` Michael Richardson [this message]
2016-03-09 20:27 ` Baptiste Clenet
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=3583.1457550990@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bapclenet@gmail.com \
--cc=linux-wpan@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.