From: sohny thomas <sohny.kernel@gmail.com>
To: nicolas.dichtel@6wind.com,
Sohny Thomas <sthomas@linux.vnet.ibm.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: Wed, 05 Feb 2014 00:07:04 +0530 [thread overview]
Message-ID: <52F13350.2020300@gmail.com> (raw)
In-Reply-To: <52EFC324.1030102@6wind.com>
On Monday 03 February 2014 09:56 PM, Nicolas Dichtel wrote:
>> 4) make flush not remove the fe80::/64 address
>>
>> Least favourable to me. I guess this also woud need iproute change
>> and seems most difficult to do.
> Why using this command 'ip -6 route flush proto static' isn't possible?
Ok I tried this and it works fine ( i.e, leaves out removing Link Local
route), but I think this is a workaround to a problem that occurs if
anyone actually deletes a Link local route
> I think that we know what kind of route is added for these TAHI tests,
> hence
> it's better to remove only routes added manually (or by a routing daemon if
> it's the case).
> Removing kernel routes may hide bugs: imagine the kernel adds a wrong
> route,
> TAHI will not detect it.
next prev parent reply other threads:[~2014-02-04 18:37 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
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 [this message]
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=52F13350.2020300@gmail.com \
--to=sohny.kernel@gmail.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=sthomas@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.