linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <aring@mojatatu.com>
To: Seung.Jang@data61.csiro.au
Cc: linux-wpan@vger.kernel.org
Subject: Re: Running OpenThread on fakelb
Date: Thu, 21 Feb 2019 10:31:23 -0500	[thread overview]
Message-ID: <20190221153123.jao2k2baqmd4eb45@x220t> (raw)
In-Reply-To: <dec2e8f279a14dc0b29dd92707e83319@exch1-mel.nexus.csiro.au>

Hi,

On Thu, Feb 21, 2019 at 12:31:19AM +0000, Seung.Jang@data61.csiro.au wrote:
> Hi all,
> 
> I'm trying to run OpenThread on fakelb, and I'd like to ask about this topic.
> 
> My test environment is Ubuntu 16.04 (kernel version 4.15).
> 
> I followed the instruction in Alex's announcement [1]. From one of ot-cli, I was able to ping the other ot-cli. At the same time, I tried to sniff packets of lowpan0, ot0, ot1, and monitor0 with wireshark. But wireshark detected nothing. When I compiled the ot-cli, I applied '--enable-af-packet'.
> 

The branch of openthread is somehow outdated, feel free to rebase to
openthread/master and send it upstream to openthread.

Your problem:

As I understand you can talk between openthread nodes but not with an
additional Linux 6lowpan interface. To make it capable with openthread
you need to use protocols which are from the Thread world. They have a
"somehow" closed bootstrapping protocol which is MLE. Also note they
forked the IETF MLE standard, so Thread MLE != IETF MLE.

I can give you more information what MLE exactly is if you want.

> Do you have any idea about this? Could you share any experience regarding this?
> 

How you can get Thread MLE working for you?

Good solution is:

"Use open implementation OpenThread and make a library wrapper around
 which is a MLE Linux userspace implementation. It should work on IPv6
 sockets and not AF_PACKET"

Hack solution is:

"Run openthread on node interfaces and AF_PACKET and keep mac settings
in sync" - not sure how this can work, I think it will only make more
trouble.

Another solution:

Just use af802154 in openthread, but then you only use Linux 802.15.4
drivers and mostly no upper layer protocol. Also on node interfaces you
need to keep address settings in sync which I didn't implemented.
On the other hand monitors has limitations when running in promiscuous
mode.

- Alex

  reply	other threads:[~2019-02-21 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21  0:31 Running OpenThread on fakelb Seung.Jang
2019-02-21 15:31 ` Alexander Aring [this message]
2019-02-22  1:03   ` Seung.Jang

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=20190221153123.jao2k2baqmd4eb45@x220t \
    --to=aring@mojatatu.com \
    --cc=Seung.Jang@data61.csiro.au \
    --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 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).