From: Alexander Aring <aring@mojatatu.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Sujay G <sujay.g@hcl.com>,
"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: about openthread and 6lowpan
Date: Mon, 10 Sep 2018 11:06:47 -0400 [thread overview]
Message-ID: <20180910150647.dcwoyslxrusvcj7j@x220t> (raw)
In-Reply-To: <3503.1536526189@localhost>
Hi,
On Sun, Sep 09, 2018 at 04:49:49PM -0400, Michael Richardson wrote:
>
> Sujay G <sujay.g@hcl.com> wrote:
> > I have been testing openThread on Docker. I wanted to use 6Lowpan with
> > openthread. I assumed openThread would interact with wpan interfaces
> > and added wpan interfaces in container namespace but it did not work.
>
> > Then I came across change for 6Lowpan. Comparison yielded changes in 7
> > files vs the latest openThread repositiry
> > github.com/openthread/openthread/compare/master...linux-wpan:af802154
>
> Why are you asking the linux-wpan ML about openthread patches? :-)
>
it's okay.
> Alex did some patches to make openthread work better with the virtual
> interfaces... it's up to the openthread people to adopt them or not.
>
What is does is to run openthread as somewhat "user space stack" with
limited functionality on monitor interfaces. It's good for debugging.
"limited functionality" is e.g. not ack handling, every frame get to
userspace... it's a pain to run productive I think.
I worried, here was somebody who said "it just works for him on node
interfaces", but in this case the kernel run filtering... I am worried
that people using it in this way and don't know what they do.
> > I manually merged the files and am trying to resolve the errors.
>
> > Had few queries regarding the openThread and 6Lowpan
>
> > Why was the project (af802154) abandoned ? Was openThread working with
> > the above 6Lowpan changes ? Does the current openThread stack support
> > 6Lowpan ? any configuration needs to be enabled ? or is it the right
> > way to port the af802154 to current implementation of openthread ?
>
> You could rebase it, and maybe you have more influence with the
> openthread people than we do.
agree.
- Alex
next prev parent reply other threads:[~2018-09-10 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SG2PR04MB31586E124C6C9A919150F826EF000@SG2PR04MB3158.apcprd04.prod.outlook.com>
[not found] ` <SG2PR04MB3158366EFF8CBC241C84FFD5EF060@SG2PR04MB3158.apcprd04.prod.outlook.com>
2018-09-09 15:05 ` about openthread and 6lowpan Sujay G
2018-09-09 20:49 ` Michael Richardson
2018-09-10 15:06 ` Alexander Aring [this message]
2018-09-20 6:06 ` Sujay G
2018-09-20 6:57 ` Sujay G
2018-09-24 20:56 ` Alexander Aring
2018-09-26 13:28 ` Sujay G
2018-09-26 19:41 ` Alexander Aring
2018-09-24 20:52 ` Alexander Aring
2018-09-10 15:18 ` Alexander Aring
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=20180910150647.dcwoyslxrusvcj7j@x220t \
--to=aring@mojatatu.com \
--cc=linux-wpan@vger.kernel.org \
--cc=mcr@sandelman.ca \
--cc=sujay.g@hcl.com \
/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).