From: "YOSHIFUJI Hideaki/吉藤英明" <hideaki.yoshifuji@miraclelinux•com>
To: Alexander Aring <alex.aring@gmail•com>, davem@davemloft•net
Cc: hideaki.yoshifuji@miraclelinux•com, kuznet@ms2•inr.ac.ru,
jmorris@namei•org, yoshfuji@linux-ipv6•org, kaber@trash•net,
netdev@vger•kernel.org, linux-wpan@vger•kernel.org
Subject: Re: IPv6 over IEEE 802.15.4 aka 6LoWPAN - Neighbor discovery issue
Date: Wed, 06 Aug 2014 09:40:28 +0900 [thread overview]
Message-ID: <53E1797C.8000207@miraclelinux.com> (raw)
In-Reply-To: <20140805121516.GB14196@omega>
Hi,
Alexander Aring wrote:
> There exist no mapping between extended and short addresses. The global problem
> that the neighbor discovery cache handle the address length with a static addr_len
> value from net_device, this value should not be changed during runtime.
>
>
> To handle 6LoWPAN over IEEE 802.15.4 correctly we need to indicate that the neighbor
> discovery stores an extended or short address.
:
> My idea:
>
> Let addr_len to extended_address_length + 1. In the last byte we have a bit which
> indicate that is it a short address. If this bit isn't set we have an extended
> address.
>
> If we do that, we need some conversions about generating the ICMPv6 messages according
> to [1]. We can solve that with some hooks in net/ipv6/ndisc.c like the ndisc_mc_map
> function for mapping mac multicast addresses.
>
> Another idea to avoid hooks in net/ipv6/ndisc.c is to parse and rebuild the ICMPv6
> header while replacing IPv6 with the 6LoWPAN header.
Please avoid magling icmpv6/ipv6 bits as much as possible.
> Please I need help and I need a solution which is also acceptable for mainline.
We can have L2-specific private data per NCE, and 6lowpan uses ARPHRD_IEEE802154.
Please consider using it for L2 private data, if you need L2-speicic extra
information per NCE.
Regards,
--yoshfuji
next prev parent reply other threads:[~2014-08-06 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 12:15 IPv6 over IEEE 802.15.4 aka 6LoWPAN - Neighbor discovery issue Alexander Aring
2014-08-06 0:40 ` YOSHIFUJI Hideaki/吉藤英明 [this message]
2014-08-06 10:36 ` Alexander Aring
2014-08-06 21:26 ` David Miller
[not found] ` <53E1B912.5000508@gmail.com>
2014-08-06 7:10 ` Alexander Aring
2014-08-06 7:15 ` Varka Bhadram
2014-08-06 7:47 ` Alexander Aring
2014-08-06 8:32 ` Varka Bhadram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53E1797C.8000207@miraclelinux.com \
--to=hideaki.yoshifuji@miraclelinux$(echo .)com \
--cc=alex.aring@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jmorris@namei$(echo .)org \
--cc=kaber@trash$(echo .)net \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=linux-wpan@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox