netdev - Re: Question about IPv6 neighbor discovery and 6lowpan

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 22 Nov 2013 10:29:06 +0700
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Jukka Rissanen <jukka.rissanen@...ux.intel.com>
Cc:	Alexander Aring <alex.aring@...il.com>,
	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: Question about IPv6 neighbor discovery and 6lowpan

Hi Jukka,

>>> I am investigating RFC 6775 (Neighbor Discovery Optimization for IPv6
>>> over Low-Power Wireless Personal Area Networks (6LoWPANs))
>>> http://tools.ietf.org/html/rfc6775
>>> 
>>> The RFC suggests some changes to neighbor discovery procedure for the
>>> 6LoWPAN networks. I was looking net/ipv6/ndisc.c and it seems that
>>> ARPHRD type (from type field in net_device struct) is the only way to
>>> detect and change the discovery procedure in the ndisc.c code. Am I
>>> right with this assumption here?
>>> 
>> I think you are right, there was some patches on linux-zigbee-devel who
>> use exact the same idea to check the ARPHRD type.
> 
> Ok. The reason I was interested in about this is that I proposed new
> ARPHRD_RAWIP earlier that I could use in BT LE 6lowpan code. Now I think
> that type might be too generic and perhaps I should have ARPHRD_6LOWPAN
> or even ARPHRD_BT_6LOWPAN.

if it can be shared between 802.15.4 and Bluetooth, then I would propose to use ARPHRD_6LOWPAN and also convert the 802.15.4 stack to use that one.

Regards

Marcel

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html