From: Hannes Frederic Sowa <hannes@redhat.com>
To: Harout Hedeshian <harouth@codeaurora.org>
Cc: "'David Ahern'" <dsahern@gmail.com>, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] net: ipv6: Make address flushing on ifdown optional
Date: Mon, 19 Jan 2015 20:11:52 +0100 [thread overview]
Message-ID: <1421694712.13047.5.camel@redhat.com> (raw)
In-Reply-To: <00c901d03402$b5cb6890$216239b0$@codeaurora.org>
On Mo, 2015-01-19 at 09:12 -0700, Harout Hedeshian wrote:
> > I would still prefer that we flush automatically generated addresses and only
> > keep the static and permanent ones.
> >
> > What do you think?
> >
> > Bye,
> > Hannes
>
> If I may offer an opinion, I do feel that there are use cases where flushing the auto-generated addresses in ifdown would not be desirable.
>
> We have one such use case where information regarding the state of the network beyond the interface is managed through sideband signaling. We know that the auto-generated address would still be valid on ifup because the router information is unchanged. In this case, ifup/down is solely being used as a way for user space to enable/disable all traffic on a particular netdevice for temporary periods.
>
> That said, I'm not sure how useful this would be for the average user; I see no harm if it is configurable and the default behavior is unchanged.
Do you think it makes sense to combine the logic with the accept_ra
sysctl?
accept_ra && !flush_addr_on_down -> flush addresses generated by accept_ra logic
!accept_ra && !flush_addr_on_down -> don't flush any addresses
I am not sure about that, feels complicated. Would that suite your usecase?
Bye,
Hannes
next prev parent reply other threads:[~2015-01-19 19:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 19:17 [RFC PATCH] net: ipv6: Make address flushing on ifdown optional David Ahern
2015-01-19 15:02 ` Hannes Frederic Sowa
2015-01-19 16:12 ` Harout Hedeshian
2015-01-19 19:11 ` Hannes Frederic Sowa [this message]
2015-01-20 17:07 ` David Ahern
2015-01-23 6:40 ` Stephen Hemminger
2015-01-23 12:22 ` Hannes Frederic Sowa
2015-01-27 4:56 ` Andy Gospodarek
2015-01-27 9:44 ` Hannes Frederic Sowa
2015-01-27 14:55 ` David Ahern
2015-01-27 15:28 ` Hannes Frederic Sowa
2015-01-28 3:21 ` David Ahern
2015-01-28 8:25 ` Hannes Frederic Sowa
2015-01-27 16:09 ` Andy Gospodarek
2015-01-23 18:47 ` David Ahern
2015-01-23 16:09 ` Brian Haley
2015-01-23 18:23 ` David Ahern
2015-01-23 21:17 ` Brian Haley
2015-01-26 16:49 ` 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=1421694712.13047.5.camel@redhat.com \
--to=hannes@redhat.com \
--cc=dsahern@gmail.com \
--cc=harouth@codeaurora.org \
--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 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.