I've been trying to set up a 6LoWPAN network similar to what's
described on the "Getting Started" page [1], only that this is a
mix of Linux and Contiki. It works after solving the uncompression
issues I mentioned in my last post, but there are still a few
things I wonder about:

- why configure all nodes to have an additional link-local address
  (besides the fe80::a200:0:0:{1,2,3} they derive from the EUI-64) ?

  I.e., this:
  # ip addr add fe80::a000:0:0:8/64 dev lowpan0

  And why make it the same on all the nodes ?

- the pings seem to try to use the automatically set link-local
  address but without flipping the universal/local bit. I.e.,
  "Getting Started" says

  # ping6 fe80::a000:0:0:3%lowpan1

  But it would seem that what is meant is

  # ping6 fe80::a200:0:0:3%lowpan1

  (Or the additional address that's being set manually would have
  to be fe80::a000:0:0:{1,2,3})

- the example doesn't set the address of the wpan0 interface. This
  address is compared in mac802154_subif_frame and a mismatch causes
  it to classify the frame as PACKET_OTHERHOST while it should be
  PACKET_HOST. As far as I can tell, nobody cares about this, but I
  wonder if that could become an issue in the future.

  To set that address correctly, one would have to
  # ip link set wpan0 address a0:0:0:0:0:0:0:1

[1] http://sourceforge.net/apps/trac/linux-zigbee/wiki/GettingStarted-0.2

My instructions for a mixed Linux-Contiki (*) setup are here:
https://github.com/frtos-wpan/frtos-wpan/blob/master/doc/6lowpan.txt

(*) There's one more quirk: I run Contiki under FreeRTOS. But that
    only affects the build process, not how Contiki's networking
    works.

- Werner

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to