From: Sohny Thomas <sthomas@linux.vnet.ibm.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, yoshfuji@linux-ipv6.org,
davem@davemloft.net, kumuda <kumuda@linux.vnet.ibm.com>
Subject: Re: [PATCH] ipv6: default route for link local address is not added while assigning a address
Date: Mon, 03 Feb 2014 12:49:27 +0530 [thread overview]
Message-ID: <52EF42FF.60907@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140130232909.GH25336@order.stressinduktion.org>
> Actually I am not so sure, there is no defined semantic of flush. I would
> be ok with all three solutions: leave it as is, always add link-local
> address (it does not matter if we don't have a link-local address on
> that interface, as a global scoped one is just fine enough) or make flush not
> remove the link-local address (but this seems a bit too special cased for me).
1) In case if we leave it as it is, there is rfc 6724 rule 2 to be
considered ( previously rfc 3484)
Rule 2: Prefer appropriate scope.
If Scope(SA) < Scope(SB): If Scope(SA) < Scope(D), then prefer SB and
otherwise prefer SA. Similarly, if Scope(SB) < Scope(SA): If
Scope(SB) < Scope(D), then prefer SA and otherwise prefer SB.
Test:
Destination: fe80::2(LS)
Candidate Source Addresses: 3ffe::1(GS) or fec0::1(SS) or LLA(LS)
Result: LLA(LS)
Scope(LLA) < Scope(fec0::1): If Scope(LLA) < Scope(fe80::2), no,
prefer LLA
Scope(LLA) < Scope(3ffe::1): If Scope(LLA) < Scope(fe80::2), no,
prefer LLA
Now the above test fails since the route itself is not present, and the
test assumes that the route gets added since the LLA is not removed
during the test
2) having a LLA always helps in NDP i think
3) making flush not remove link-local address will be chnaging
functionality of ip flush command
Regards,
Sohny
>
> Greetings,
>
> Hannes
>
>
>
next prev parent reply other threads:[~2014-02-03 7:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 6:41 [PATCH] ipv6: default route for link local address is not added while assigning a address Sohny Thomas
2014-01-29 10:38 ` Nicolas Dichtel
2014-01-30 23:29 ` Hannes Frederic Sowa
2014-02-03 7:19 ` Sohny Thomas [this message]
2014-02-03 15:23 ` Nicolas Dichtel
2014-02-03 16:08 ` Hannes Frederic Sowa
2014-02-03 16:26 ` Nicolas Dichtel
2014-02-04 18:37 ` sohny thomas
2014-02-03 7:02 ` Sohny Thomas
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=52EF42FF.60907@linux.vnet.ibm.com \
--to=sthomas@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=kumuda@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--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).