From: David Ahern <dsa@cumulusnetworks.com>
To: Sowmini Varadhan <sowmini05@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
hannes@redhat.com, Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH net-next v4] net: ipv6: Make address flushing on ifdown optional
Date: Wed, 7 Oct 2015 11:01:53 -0600 [thread overview]
Message-ID: <56155001.3070207@cumulusnetworks.com> (raw)
In-Reply-To: <CACP96tQtGecigUUHdF32w91qj=abqJLo+evzOL-9JakSJZ064A@mail.gmail.com>
On 10/7/15 9:43 AM, Sowmini Varadhan wrote:
> On Wed, Oct 7, 2015 at 11:17 AM, David Ahern <dsa@cumulusnetworks.com> wrote:
>> Currently, all ipv6 addresses are flushed when the interface is configured
>> down, including global, static addresses:
> :
>>
>> Add a new sysctl to make this behavior optional. The new setting defaults to
>> flush all addresses to maintain backwards compatibility. When the setting is
>> reset global addresses with no expire times are not flushed:
>
> does src addr selection also need to be modified to know if/when it can/cannot
> use this static address as a source addr? Or does the TENTATIVE flag
> make it Do The Right Thing per rfc 3484?
>
When the device is set 'down' (admin state) all routes (including cached
ones) for the device are cleared so there should not be any way to
select the source address that is saved. i.e, ipv6_dev_get_saddr()
should not get invoked for the device.
next prev parent reply other threads:[~2015-10-07 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 15:17 [PATCH net-next v4] net: ipv6: Make address flushing on ifdown optional David Ahern
2015-10-07 15:43 ` Sowmini Varadhan
2015-10-07 17:01 ` David Ahern [this message]
2015-10-08 19:25 ` Hannes Frederic Sowa
2015-10-08 19:36 ` David Ahern
2015-10-08 19:47 ` Hannes Frederic Sowa
2015-10-11 11:44 ` David Miller
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=56155001.3070207@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=hannes@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=sowmini05@gmail.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 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.