search

linux-wpan / wpan-tools

Userspace tools for Linux IEEE 802.15.4 stack
https://linux-wpan.org/
Other
54 stars 28 forks source link

Implement llsec kernel interface and expose it to the wpan-tools commandline #2

Open Stefan-Schmidt opened 9 years ago

Stefan-Schmidt commented 9 years ago

The netlink interface for llsec configuration has landed inside the mainline kernel. We now need to support this in wpan-tools to allow a sane configuration.

Alex has posted some patches for this: http://www.spinics.net/lists/linux-wpan/msg03126.html http://www.spinics.net/lists/linux-wpan/msg03127.html

The meat ios already there but the commandline interface is not really intuitive and needs more work.

Stefan-Schmidt commented 8 years ago

Compare with bluez key handling and see if we can re-use some of the concepts.

darkfader commented 7 years ago

But still experimental. The command and attributes as in the nl802154.h in the llsec branch is outdated. It's missing the net namespace IDs. If you try with wrong header, you'll end up with invalid argument errors or NULL-pointer errors in the modules and holding some mutexes/hanging processes. I see encrypted data (secmode 5) in Wireshark but it doesn't decrypt yet somehow. I'm able to receive packets on another node, but only after adding the device address. Shouldn't it add it automatically somehow? I see somewhere in the llsec source a variable "default_key_source", but is never used? How am I supposed to know what devices exist without setting a key first? How would the secure-mode of RPL / commissioning be implemented? Two lowpan interfaces? Firewall rules? Did linux-rpl solve any of these? Or am I right and continue working on unstrung?