From: Alexander Aring <aring@mojatatu.com>
To: Sujay G <sujay.g@hcl.com>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: about openthread and 6lowpan
Date: Wed, 26 Sep 2018 15:41:09 -0400 [thread overview]
Message-ID: <20180926194109.ovjgvdeb5ktkbcec@x220t> (raw)
In-Reply-To: <SG2PR04MB3158B256663D74477E756933EF150@SG2PR04MB3158.apcprd04.prod.outlook.com>
Hi,
On Wed, Sep 26, 2018 at 01:28:09PM +0000, Sujay G wrote:
> Alex,
>
> I am referring to the presentation you gave on Netdev 2.1 IOT Without Things: Building virtual 6LoWPAN Mesh Networks
> I am trying to connect PHY0 and PHY1 as shown in the presentation but so far Iam unable to do so.
> I could get only following steps from the video
> echo “add 1 2” > /sys/kernel/debug/fakelb/edges
> ip netns exec wpan0 sh ~/host lowpan0 0 &
this is old api. I wanted to replace debugfs with netlink which I did.
The feature what you are looking for is now upstream in a new driver
named "mac802154_hwsim" - you need a recent kernel...
Having two nodes connected to each other fakelb is enough. The new
driver allows you to run a individual mesh network with 1000 nodes
connected RIOT/Contiki/Linux/openthread/etc.... you need just enough
memory to run it. And I think with 1000 nodes it will run terrible slow,
because each userspace stack need to filter it _in_ userspace. But it's
possible...
>
> Can you please provide the sequence of steps you used to connect PHY0 and PHY1 ?
>
With mac802154_hwsim you need to have wpan_hwsim which I think are still
not part of wpan-tools upstream [0]. You need to apply these patches and
then run a recent kernel.
Then load mac802154_hwsim and using the tool which is more self
explained. Sorry I don't have any example currently how to set it up...
but you should try fakelb with 3 nodes, every phy is monitor.
Then on two monitors each running openthread. One monitor runs
wireshark/tshark, Then you should able too see the traffic between the
nodes.
- Alex
[0] https://www.spinics.net/lists/linux-wpan/msg05122.html
next prev parent reply other threads:[~2018-09-27 1:55 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
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 [this message]
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=20180926194109.ovjgvdeb5ktkbcec@x220t \
--to=aring@mojatatu.com \
--cc=linux-wpan@vger.kernel.org \
--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).