From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Fedor Babkin <fedor.babkin@gmx.net>
Cc: Julian Anastasov <ja@ssi.bg>, netdev@vger.kernel.org
Subject: Re: Aw: Re: Routes with unreachable gateways are staying in the routing table and they are functional
Date: Tue, 26 Aug 2014 14:34:57 +0200 [thread overview]
Message-ID: <1409056497.9923.9.camel@localhost> (raw)
In-Reply-To: <trinity-760989cf-0ea4-496a-9992-02ed85a5ffe5-1409039594977@3capp-gmx-bs38>
Hi,
On Di, 2014-08-26 at 09:53 +0200, Fedor Babkin wrote:
> Thanks for your feedback. For IPv4 the situation is clear, you have to configure more that one subnet to the interface in order to start experiencing this issue. However exactly the same issue exists in IPv6, where once you configure a single address, you have to count on effectively having 2 addresses on the interface, due to the presence of a link-local address fe80::xxxx. Moreover with IPv6 stateless address autoconfiguration (RFC 4862), there is more address configuration dynamics in IPv6 comparing to IPv4. I would say this issue has a higher visibility and side-effect potential. Is there anyone looking into this issue from IPv6 perspective?
Actually, it is an error and an implementation problem that we currently
add interface routes when adding ipv6 addresses to an interface. Those
routes should only be allocated when the host receives on-link
information (redirect, router advertisment). So in case of IPv6 routing
information should always be handled separate from routing information.
Also see:
$ git log -G IFA_F_NOPREFIXROUTE net/ipv6/addrconf.c
Greetings,
Hannes
prev parent reply other threads:[~2014-08-26 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 15:11 Routes with unreachable gateways are staying in the routing table and they are functional Fedor Babkin
2014-08-22 16:28 ` Julian Anastasov
2014-08-26 7:53 ` Aw: " Fedor Babkin
2014-08-26 12:34 ` Hannes Frederic Sowa [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=1409056497.9923.9.camel@localhost \
--to=hannes@stressinduktion.org \
--cc=fedor.babkin@gmx.net \
--cc=ja@ssi.bg \
--cc=netdev@vger.kernel.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).