Hi, I will send in the next days a new implementation for the netlink interface. Why? I don't know where I can begin to say what's wrong with the current netlink interface. It has some half implemented features and the userspace header (they are not in uapi) contains "extern ..." things for the policy. Right now the lowpan-tools supports add/del interfaces and setting of hardware filter functionality, pan_id, short_address, nothing more. There are some other userspace application (I know two) which talk with this interface. Please don't be angry that you need to updated the userspace application according the new one. The new interface is like cfg80211, but with 802.15.4 functionality. I begun to make everything like the wirless stack and then we can think about bringing 802.15.4 functionality into this stack. Also I implemented a new userspace tool package "wpan-tools" [0]. This will contain the iwpan tool. This code is mostly based on the iw tool from wireless [1]. It currently support adding new interface and delete exist interfaces. It's very modular and we can easy add new netlink features. The nl802154.h should not updated in the wpan-tools, it should updated on the kernel side. I will send the cfg802154 patches to this mailinglist, when I get basic support for channel and pan id setting. - Alex [0] https://github.com/linux-wpan/wpan-tools [1] http://git.kernel.org/cgit/linux/kernel/git/jberg/iw.git -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
