From: David Miller <davem@davemloft.net>
To: yoshfuji@linux-ipv6.org
Cc: jbohac@suse.cz, netdev@vger.kernel.org
Subject: Re: ipv6: why disable ipv6 on last address removal?
Date: Mon, 04 Jan 2010 22:44:36 -0800 (PST) [thread overview]
Message-ID: <20100104.224436.107234750.davem@davemloft.net> (raw)
In-Reply-To: <4B1F5423.4070109@linux-ipv6.org>
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Date: Wed, 09 Dec 2009 16:39:15 +0900
> 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.
I think we should retain inet6 device private structure after
we allocate it the first time that an ipv6 action occurs for
the device, exactly so that settings made earlier can be
retained.
next prev parent reply other threads:[~2010-01-05 6:44 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
2010-01-05 6:44 ` David Miller [this message]
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=20100104.224436.107234750.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbohac@suse.cz \
--cc=netdev@vger.kernel.org \
--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 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).