Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Michael C Cambria <mcc@fid4.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [ANNOUNCE] wpan-tools 0.3 released
Date: Sun, 7 Dec 2014 22:54:55 +0100	[thread overview]
Message-ID: <20141207215452.GB20260@omega> (raw)
In-Reply-To: <5484C900.2020402@fid4.com>

On Sun, Dec 07, 2014 at 04:39:12PM -0500, Michael C Cambria wrote:
> On 12/07/14 12:19, Alexander Aring wrote:
> >On Sun, Dec 07, 2014 at 06:13:11PM +0100, Alexander Aring wrote:
> >>Hi,
> >>
> >>please use bluetooth-next [0] for the wpan-tools. For experiment things use
> >>wpan_rework_rfc branch. I have still patches there which should be go
> >>into mainline but isn't easy to touch the code without breaking.
> >Now I remember, I changed the netlink interface too much and doesn't
> >change it inside the wpan_rework_rfc branch.
> >
> >So it's only working if you hack the nl802154.h header and copy it into
> >wpan-tools or simple forget this branch. This is my dirty dev branch
> >only for bringing the rework mainline, which is still in progress.
> >
> >- Alex
> 
> Now I'm confused.  Forget using which branch? bluetooth-next?
> wpan_rework_rfc?  linux-wpan-next?
> 

the linux-wpan-next/wpan_rework_rfc and linux-wpan-next/master.

Please use bluetooth-next/master. Also if you want to send patches,
please base it on top of bluetooth-next/master.

> Which is the most current yet stable closest to rfc4944 compliance kernel to
> use? Which user tools should I use with it?
> 

Doesn't matter for your use case. The wpan-tools has a little bit more
features than the lowpan-tools.

> Initially I just want to ping between two of 6LoWPAN linux systems.
> 

ok. Read introductions at [0]. Begin at "Bring up 6LoWPAN" section.

For the at86rf230 you should have default a wpan0 interface. If you use
wpan-tools simple type "iwpan" and read the help for setting address
information. I think for at86rf230 you need to set the panid only, phy
settings should be transceiver defaults and short address isn't supported
for 6LoWPAN (except broadcast address, of course).

The documentation is a little bit outdated currently.

> In time I'll create a 3 node mesh and ping from one node via the second to
> the third as a destination.
> 

ok.

> Eventually I add another 6LoWPAN node that will be a "Full Function Device"
> and routes to traditional IPv6.
> 

FFD with coordinator support? We don't support such functionality at L2
level yet.




If you need help simple ask here or for better fast live supporting you
can contact me via IRC #linux-wpan on irc.freenode.net. Ping between two
nodes should be an easy setup.

- Alex

[0] http://linux-zigbee.sourceforge.net/cgi-bin/trac.cgi/wiki/GettingStarted-0.2

  reply	other threads:[~2014-12-07 21:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07 15:08 [ANNOUNCE] wpan-tools 0.3 released Alexander Aring
2014-12-07 17:01 ` Michael C Cambria
2014-12-07 17:13   ` Alexander Aring
2014-12-07 17:19     ` Alexander Aring
2014-12-07 21:39       ` Michael C Cambria
2014-12-07 21:54         ` Alexander Aring [this message]
2014-12-11 15:02           ` Michael C. Cambria
2014-12-11 16:31             ` Alexander Aring
2015-01-06 19:18               ` Maciej Wasilak
2015-01-06 19:44                 ` Alexander Aring
2014-12-12  8:54             ` Stefan Schmidt
2014-12-13  8:55               ` Alexander Aring
2014-12-15  8:29                 ` Stefan Schmidt
2014-12-15  8:35                   ` 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=20141207215452.GB20260@omega \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=mcc@fid4.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