Hi, On 08/02/2016 04:37 PM, Alexander Aring wrote: > This patch will change the behaviour for 6LoWPAN interface to detect the > linklayer address length via sysfs. The usually way to get the address > length is via a mapping from ARPHRD device type. This doesn't work for > 6LoWPAN interfaces, we need at least some other mechanism. This patch > adds the mechanism to read out the sysfs UAPI to get the addr_len > attribute of net_device. This will not work if there are two 6LoWPAN > link-layer types with the same address length but need different > handling in userspace. For that reason I think a linklayer type would be > better, this requires a 6lowpan netlink API which doesn't exist right > now. So we use this simple way now. > > Signed-off-by: Alexander Aring <aar@xxxxxxxxxxxxxx> I need to remove this signed off. That's not radvd commit style. :-) --- After talking shortly with Marcel, RTNL netlink has already the same stuff what we can get from sysfs entry here. See [0] kernel and [1] userspace. Over RTA_PAYLOAD(tb[IFLA_ADDRESS]) [1], we should be able to get the dev->addr_len which is given by [0]... I make now a new version with netlink as UAPI mechanism. - Alex [0] http://lxr.free-electrons.com/source/net/core/rtnetlink.c#L1247 [1] https://github.com/shemminger/iproute2/blob/master/lib/ll_map.c#L84 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
