Hi, Hi, On Tue, Jan 06, 2015 at 08:18:25PM +0100, Maciej Wasilak wrote: ... > > 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. > 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 -- 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
