netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varka Bhadram <varkabhadram@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: davem@davemloft.net, 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 14:02:40 +0530	[thread overview]
Message-ID: <53E1E828.2050706@gmail.com> (raw)
In-Reply-To: <20140806074715.GA31022@omega>

On 08/06/2014 01:17 PM, Alexander Aring wrote:
>>>> Handing of RS (Router Solicitation) and RA (Router Advertisement) will take care
>>>> by radvd (Router Advertisement Daemon) in Linux. We added the ABRO and 6CO option
>>>> support in radvd. You can find the implementation in [1].
>>>>
>>>>
>>>> [1]: https://github.com/reubenhwk/radvd/blob/master/send.c#L536
>>>>
>>> I see you use the ContextID there, then you need the CID value from
>>> 6LoWPAN header there. I am very interest for patches which introduce
>>> context based address compression and make it also available in
>>> userspace to handle the ContextID with radvd.
>> Right now we providing the contextID from user space through radvd.conf.
>>
>> Context based implementation is not supported so we are only using the
>> context identifier from user space.
>>
> A static CID value in radvd.conf? Sorry, I don't know how this can be
> working without very limitations of use.

Actually we have to get the CID from the 6LoWPAN packet and we have to
update or store the CID based information into a separate table.

For each and every CID we are going to have the its own info.

If CID is changed we have to increment the *version* field in ABRO option
and sends RA message. This support is future work if we have the CID based
compression.


-- 
Regards,
Varka Bhadram.

      reply	other threads:[~2014-08-06  8:34 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/吉藤英明
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 [this message]

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=53E1E828.2050706@gmail.com \
    --to=varkabhadram@gmail.com \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).