From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: sohny thomas <sohny.kernel@gmail.com>,
linux-kernel@vger.kernel.org, yoshfuji@linux-ipv6.org,
davem@davemloft.net, kumuda <kumuda@linux.vnet.ibm.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: ipv6: default route for link local address is not added while assigning a address
Date: Fri, 10 Jan 2014 18:16:13 +0100 [thread overview]
Message-ID: <20140110171613.GA23647@order.stressinduktion.org> (raw)
In-Reply-To: <52D020C4.30105@6wind.com>
On Fri, Jan 10, 2014 at 05:33:08PM +0100, Nicolas Dichtel wrote:
> CC: netdev
>
> Le 10/01/2014 13:20, sohny thomas a écrit :
> >Default route for link local address is configured automatically if
> >NETWORKING_IPV6=yes is in ifcfg-eth*.
> >When the route table for the interface is flushed and a new address is
> >added to
> >the same device with out removing linklocal addr, default route for link
> >local
> >address has to added by default.
> I would say that removing the link local route but not the link local
> address
> is a configuration problem.
> If you remove a connected route but not the associated address, you will
> have
> the same problem.
We have some user accessible routes that are essential for IPv6 stack
to work at all. So I don't know if I can agree with that.
Maybe flush is a bit too aggressive?
next prev parent reply other threads:[~2014-01-10 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 12:20 sohny thomas
2014-01-10 16:33 ` Nicolas Dichtel
2014-01-10 17:16 ` Hannes Frederic Sowa [this message]
[not found] <52D2F201.1090903@gmail.com>
2014-01-13 8:49 ` sohny thomas
2014-01-17 8:34 ` sohny thomas
2014-01-17 12:16 ` Hannes Frederic Sowa
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=20140110171613.GA23647@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--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=sohny.kernel@gmail.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
all inboxes | Powered by JetHome®