netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas DICHTEL <nicolas.dichtel@6wind.com>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 and rt6_lookup()
Date: Thu, 02 Nov 2006 18:19:06 +0100	[thread overview]
Message-ID: <454A288A.7050107@6wind.com> (raw)
In-Reply-To: <454A24B7.1010109@hp.com>

Le 02.11.2006 18:02, Vlad Yasevich a écrit :
> Nicolas DICHTEL wrote:
>> Hello,
>>
>> Suppose that a host has autoconfiguration enabled. It will take RA to
>> autoconfigure an IPv6 address. For example,
>> 2001:0db8:3008:c1ca:2d0:b7ff:febb:4aee/64.
>> This host will create a route entry for this onlink prefix (dst:
>> 2001:0db8:3008:c1ca::/64)
>> in the MAIN table with the lifetime present in prefix option in RA.
>> Each time this host will receive a RA, it will update this lifetime. To
>> do this,
>> it will call rt6_lookup() (in addrconf_prefix_rcv()) to find the entry.
>>
>> Now, suppose that our host joins this anycast group:
>> "2001:0db8:3008:c1ca::0". A route
>
> Hmm... you are configuring a subnet router anycast address on host and 
> the implementation lets you do it?  That's not good.  I don't think
> you sould be permitted to configure a subnet router anycast address
> on a host that autoconfigures it's interface.
The current implementation allow this and I don't know if we must 
prohibit this.
For example, in case of NEMO (RFC3963), router may autoconfigured its 
address.

Nicolas

      reply	other threads:[~2006-11-02 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 16:25 IPv6 and rt6_lookup() Nicolas DICHTEL
2006-11-02 17:02 ` Vlad Yasevich
2006-11-02 17:19   ` Nicolas DICHTEL [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=454A288A.7050107@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladislav.yasevich@hp.com \
    /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).