From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: David Miller <davem@davemloft.net>
Cc: jbohac@suse.cz, netdev@vger.kernel.org
Subject: Re: ipv6: why disable ipv6 on last address removal?
Date: Wed, 09 Dec 2009 16:39:15 +0900 [thread overview]
Message-ID: <4B1F5423.4070109@linux-ipv6.org> (raw)
In-Reply-To: <20091208.125611.135547597.davem@davemloft.net>
Hello.
Well, AFAIK, it is basically ancient thing.
Some (rather new) paramters are exactly related bringing
up each interface.
Such parameters should be set _before_ it is brought up.
For now, people can do this using the "default" value.
We might have rtnetlink interface for up/down interface,
allowing userspace to send related parameters as well.
Regards,
--yoshfuji
David Miller wrote:
> From: Jiri Bohac <jbohac@suse.cz>
> Date: Tue, 8 Dec 2009 20:20:46 +0100
>
>> Is there any reason why inet6_addr_del needs to sets how=1 and
>> disable IPv6 even more than "ifconfig down" does?
>
> All I can say is that this behavior is definitely on purpose, although
> I don't exactly remember why.
>
> And although it helps you, it could also break things for other people
> who expect the current behavior.
>
> Some people definitely expect no IPV6 at all in any way shape or
> form if they have not assigned IPV6 addresses to an interface.
next prev parent reply other threads:[~2009-12-09 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 19:20 ipv6: why disable ipv6 on last address removal? Jiri Bohac
2009-12-08 20:56 ` David Miller
2009-12-09 7:18 ` Jiri Bohac
2009-12-09 7:39 ` YOSHIFUJI Hideaki [this message]
2010-01-05 6:44 ` David Miller
2010-02-16 15:28 ` Jiri Bohac
2011-01-23 9:47 ` Stephen Hemminger
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=4B1F5423.4070109@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=jbohac@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).