wpan-tools 0.3 released

Hi,

I'm happy to announce that I've just released wpan-tools 0.3. This is our first "real" release, the new kernel 3.18 will contain the nl802154 interface. The old netlink interface will be removed soon and is deprecated now. At the moment you can still use both userspace tools, but I don't recommend the lowpan-tools.

New release will be found now under:

http://wpan.cakelab.org/releases/

Github has no option to make releases with "make distcheck" that's why I will upload it to this location.

Below you can see the shortlog from 0.2 to 0.3 version. Only some fixes to make a release with "make distcheck" possible.

Thanks to all contributors.

- Alex

Alexander Aring (4):
iwpan: use autoconf version defines
configure: fix CLFAGS definition
configure: change archive generation
configure: version bump

Stefan Schmidt (3):
configure: Fail if libnl3 dependency is not found
build: add header files to SOURCES
configure: do not use check-news for now

Should we using https://github.com/linux-wpan/linux-wpan-next or https://github.com/linux-wpan/linux-wpan-next/tree/wpan_rework_rfc

Thanks,
MikeC

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.

Also for patches please base on bluetooth-next.

mhh, better I update this branch now to bluetooth-next since nl802154 seems to be work.

- Alex

[0] http://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git

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?

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

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

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

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

Thanks,
MikeC

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.

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

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.

ok.

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

[deleted]

I'm using bluetooth-next, and it boots and seems to find the openlabs.co adapter just fine.

GettingStarted-0.2 describes the "iz" command. I don't have "iz". I built/installed on the Pi itself, downloaded from
http://wpan.cakelab.org/releases/. I do see an iwpan command installed (see below).Are there more user tools or do we just substitute iz with iwpan?

Once an IPv6 address is assigned to wpan0, should I be able to ping wpan0 from an IPv6 address on a different box? I ask because I only have one Pi at the moment and can't test radio to radio.

pi@raspberrypi:~$ iwpan list
wpan_phy wpan-phy0
supported channels:
        page 0: 11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26
current_page: 0
current_channel: 13
cca_mode: 0
tx_power: 0
pi@raspberrypi:~$
pi@raspberrypi:~$
pi@raspberrypi:~$
pi@raspberrypi:~$
pi@raspberrypi:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 7a:93:66:29:55:e3
          inet addr:192.168.1.171  Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::7893:66ff:fe29:55e3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500 Metric:1
          RX packets:140 errors:2 dropped:0 overruns:0 frame:0
          TX packets:64 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10011 (9.7 KiB)  TX bytes:6536 (6.3 KiB)

[deleted]

wpan0 Link encap:UNSPEC HWaddr 26-8E-9A-10-24-7B-3A-81-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING NOARP MTU:127 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:300
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

pi@raspberrypi:~$

yes, lowpan-tools will be deprecated soon, which means the netlink interface will be removed... maybe in the next three kernel versions.

No, please forget the complete tutorial with iz.

You need to set a pan_id. "iwpan dev wpan0 set pan_id 0xbeef" or something else Then create a lowpan interface with:

ip link add link wpan0 name lowpan0 type lowpan

lowpan0 is now your ipv6 interface which use 6LoWPAN.

I will try to make some better new documentation in wpan.cakelab.org with some asciidoc generated html pages... when I find some time.

- Alex

Hello,

2014-12-11 17:31 GMT+01:00 Alexander Aring <[email protected]>:

I tried to follow instructions above and I have trouble changing pan_id. When I execute command:

    sudo iwpan --debug dev wpan0 set pan_id 0xabcd

I get following output:

-- Debug: Sent Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets

    .nlmsg_len = 36
    .type = 21 <0x15>
    .flags = 5 <REQUEST,ACK>
    .seq = 1420571541
    .port = -1023407865
  [GENERIC NETLINK HEADER] 4 octets
    .cmd = 10
    .version = 0
    .unused = 0
  [PAYLOAD] 16 octets
    08 00 03 00 02 00 00 00 06 00 09 00 cd ab 00 00 ................

--------------------------- END NETLINK MESSAGE ---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[NETLINK HEADER] 16 octets

    .nlmsg_len = 56
    .type = 2 <ERROR>
    .flags = 0 <>
    .seq = 1420571541
    .port = -1023407865
  [ERRORMSG] 20 octets
    .error = -16 "Device or resource busy"
  [ORIGINAL MESSAGE] 16 octets
    .nlmsg_len = 16
    .type = 21 <0x15>
    .flags = 5 <REQUEST,ACK>
    .seq = 1420571541
    .port = -1023407865

--------------------------- END NETLINK MESSAGE ---------------------------
command failed: Device or resource busy (-16)

I am using Raspberry Pi with Raspbian, and bluetooth-next branch kernel (cloned today). I am using 802.15.4 hardware from openlabs. Physical interface is recognized correctly:

    pi@raspberrypi ~ $ iwpan phy
    wpan_phy wpan-phy0
    supported channels:
        page 0: 11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26
    current_page: 0
    current_channel: 26
    cca_mode: 1
    tx_power: 0
Network wpan0 interface is created automatically on startup:
    pi@raspberrypi ~ $ iwpan dev
    phy#0
        Interface wpan0
            ifindex 2
            wpan_dev 0x1
            extended_addr 0xf9045327f9757da8
            short_addr 0xffff
            pan_id 0xffff
            type node
            max_frame_retries -1
            min_be 3
            max_be 5
            max_csma_backoffs 4
            lbt 0

I can create lowpan interface without problems (sudo ip link add link wpan0 name lowpan0 type lowpan). It sends valid 6LoWPAN packets (I use external sniffer), but pan_id remains 0xffff.

When I use old linux-wpan-next branch and old lowpan-tools, problem doesn't occur.

I tried to bring wpan0 interface down (sudo ifconfig wpan0 down), but it doesn't help.

Does anyone have the same problem?

Best Regards
Maciej Wasilak

Hi,

Hi,

On Tue, Jan 06, 2015 at 08:18:25PM +0100, Maciej Wasilak wrote:
...

Which wpan-tools version do you use? Can you please try the newest version which can be found at [0].

I did some changes according the new nl802154 uapi header, means enum structural changes. Sorry about that, I suppose that's your problem.

Can you please try to update your wpan-tools or simple use the actual one at [1].

If this doesn't help I don't know why you have this issue. The ifdown of your wpan interface should fix the -EBUSY issue.

btw:
We return -EBUSY because the address filter is set on an interface up, while interface up it's not easy to deal address filtering changes, also we can remove some hotpath locks because these values are readonly at tx/rx paths. These locks are still there and will be removed later.

- Alex

[0] http://wpan.cakelab.org/releases/
[1] https://github.com/linux-wpan/wpan-tools

Hello.

Thanks for mentioning this adapter. I was looking for something like this for a while. Just ordered. :)

Anyone has some tips about cheap but easy to use sensor nodes with contiki and maybe TinyOS support? I don't care about senors or such on them at all. My use case would be testing the communication interop between the Linux stack and contiki or other embedded OS's.

All I found so far are 70€ or higher which I find a bit pricey for my use case.

regards
Stefan Schmidt

Stefan,

Maybe again the avr raven are something for you. I don't use the shipped sensors, but you can connect them to some power supply (don't know which voltage, but need to solder some pinouts).

My idea is now, you have these sensor node (don't know if they are good to use) and the USB Stick. The RAVEN USB stick works like atusb but with a bigger mcu (more ram etc...) maybe you get this wireless kit and I think you could easy port the atusb firmware to this raven usb stick, just an idea. With dfu (I know you already an expert in dfu and the ported atusb firmware (maybe with tweaks because it contains a bigger mcu).

Just an idea, I have one of the avr raven usb stick and they are much common as the atusb stick.

For me the idea to have an atusb firmware for the avr raven usb stick sounds great. Maybe you will start the project "Most used open source firmware for 802.15.4 USB dongles". ;-)

- Alex

[0] http://store.atmel.com/PartDetail.aspx?q=p:10500059#tc:description

Hello.

Will check if the avr raven might be interesting for me.

The idea is interesting but for now I would like to focus on the Linux side of things. Firmware hacking is not at the top of my list. :)

regards
Stefan Schmidt

oh, I can help you with firmware hacking. Just we both have atusb and avr raven sticks. But too many things need to be done.

I think with the avr raven sticks we get an huge increment of users for this stack.

Okay here's the deal:

I wait until you finished the atusb firmware hacking, then I will check how possible it is to port the atusb to the raven stick. Maybe I can comibine it with some course at my university so I have _really_ time for it.

I could try it to market it as "master project", but seems that is not science enough. (And I would be fast done with that.)

- Alex