netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: nicolas.dichtel@6wind.com
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 and rt6_lookup()
Date: Thu, 02 Nov 2006 12:02:47 -0500	[thread overview]
Message-ID: <454A24B7.1010109@hp.com> (raw)
In-Reply-To: <454A1BF7.6030500@6wind.com>

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.

-vlad

> entry will be added in the LOCAL table (see addrconf_join_anycast()).
> Problem is that, next time our host will receive a RA and will perform a
> rt6_lookup(),
> this function will return the local entry (LOCAL table), and not the
> "dynamic" entry
> (MAIN table). Consequence is that the lifetime of the dynamic entry will
> never been updated,
> and so will expire, whereas the host will keep the corresponding address.
> 
> Maybe, when strict is set to 1 in rt6_lookup(), kernel must not return
> an anycast route.
> What about this patch ?
> 
> 
> Regards,
> Nicolas
> 
> [IPv6] Don't return anycast route when strict is enable
> 
> Signed-off-by: Nicolas DICHTEL <nicolas.dichtel@6wind.com>
> 
> 
> ------------------------------------------------------------------------
> 
> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
> index c953466..51a8c1d 100644
> --- a/net/ipv6/route.c
> +++ b/net/ipv6/route.c
> @@ -248,6 +248,8 @@ static __inline__ struct rt6_info *rt6_d
>  			if (dev->ifindex == oif)
>  				return sprt;
>  			if (dev->flags & IFF_LOOPBACK) {
> +				if (strict && sprt->rt6i_flags & RTF_ANYCAST)
> +					continue;
>  				if (sprt->rt6i_idev == NULL ||
>  				    sprt->rt6i_idev->dev->ifindex != oif) {
>  					if (strict && oif)


  reply	other threads:[~2006-11-02 17:02 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 [this message]
2006-11-02 17:19   ` Nicolas DICHTEL

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=454A24B7.1010109@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.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).