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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20131121161310.GA10513@omega>
Date:	Thu, 21 Nov 2013 17:13:11 +0100
From:	Alexander Aring <alex.aring@...il.com>
To:	Jukka Rissanen <jukka.rissanen@...ux.intel.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: Question about IPv6 neighbor discovery and 6lowpan

Hi Jukka,

On Thu, Nov 21, 2013 at 05:52:15PM +0200, Jukka Rissanen wrote:
> On to, 2013-11-21 at 16:34 +0100, Alexander Aring wrote:
> > Hi Jukka,
> > 
> > On Thu, Nov 21, 2013 at 05:02:58PM +0200, Jukka Rissanen wrote:
> > > Hi,
> > > 
> > > 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.
> 
> > 
> > But I am investigating for rfc6775, too. :-)
> > 
> > 
> > At the moment I see too many unsolved issues in the ieee802154/6lowpan
> > implementation which should be fixed at first. :(
> > 
> > - Alex
> 
> No worries, the rfc6775 is common for both zigbee and bluetooth so
> whoever implements the rfc gets support for both of them at the same
> time.
> 
Yea, I did not begin yet and you are welcome to implement it. :-)

- Alex
--
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