From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
David Ahern <dsahern@gmail.com>
Cc: YOSHIFUJI Hideaki <hideaki.yoshifuji@miraclelinux.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: why are IPv6 addresses removed on link down
Date: Tue, 13 Jan 2015 18:05:19 +0100 [thread overview]
Message-ID: <54B5504F.2020200@6wind.com> (raw)
In-Reply-To: <1421161230.13626.30.camel@stressinduktion.org>
Le 13/01/2015 16:00, Hannes Frederic Sowa a écrit :
[snip]
>
> This was already discussed several times here, e.g. one patch I just
> found:
>
> http://lists.openwall.net/netdev/2011/01/24/8
> and
> http://patchwork.ozlabs.org/patch/17558/
>
> Albeit I hate sysctls for things like this, it might I tend to find it
> acceptable because it solves a problem which happened to lots of people.
> And I don't like the current behavior neither.
>
> I think this can work, but we should follow up all the old discussions
> to not introduce any kind of new undesired behavior this time.
If I remember well, one of the problem was that it was not possible anymore to
unload the IPv6 module after the patches. But since commit 8ce440610357 ("ipv6:
do not allow ipv6 module to be removed"), it's not possible anymore.
next prev parent reply other threads:[~2015-01-13 17:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 5:06 why are IPv6 addresses removed on link down David Ahern
2015-01-13 7:10 ` Stephen Hemminger
2015-01-13 10:35 ` Hannes Frederic Sowa
2015-01-13 11:58 ` YOSHIFUJI Hideaki
2015-01-13 12:15 ` YOSHIFUJI Hideaki
2015-01-13 12:36 ` Hannes Frederic Sowa
2015-01-13 14:53 ` David Ahern
2015-01-13 15:00 ` Hannes Frederic Sowa
2015-01-13 17:05 ` Nicolas Dichtel [this message]
2015-01-13 15:00 ` Sowmini Varadhan
2015-01-13 15:09 ` Hannes Frederic Sowa
2015-01-13 15:13 ` Sowmini Varadhan
2015-01-13 17:25 ` David Miller
2015-01-13 17:34 ` 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=54B5504F.2020200@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=dsahern@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.