From: Stephen Hemminger <shemminger@vyatta.com>
To: Jiri Bohac <jbohac@suse.cz>
Cc: David Miller <davem@davemloft.net>,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: ipv6: why disable ipv6 on last address removal?
Date: Sun, 23 Jan 2011 20:47:45 +1100 [thread overview]
Message-ID: <20110123204745.2f4f2de0@s6510> (raw)
In-Reply-To: <20100216152859.GC29736@midget.suse.cz>
What about this? It will remove the address on ipv6 disable.
--- a/net/ipv6/addrconf.c 2011-01-23 20:30:25.897243002 +1100
+++ b/net/ipv6/addrconf.c 2011-01-23 20:30:41.161243002 +1100
@@ -4197,7 +4197,7 @@ static void dev_disable_change(struct in
return;
if (idev->cnf.disable_ipv6)
- addrconf_notify(NULL, NETDEV_DOWN, idev->dev);
+ addrconf_notify(NULL, NETDEV_UNREGISTER, idev->dev);
else
addrconf_notify(NULL, NETDEV_UP, idev->dev);
}
prev parent reply other threads:[~2011-01-23 9:47 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
2010-02-16 15:28 ` Jiri Bohac
2011-01-23 9:47 ` Stephen Hemminger [this message]
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=20110123204745.2f4f2de0@s6510 \
--to=shemminger@vyatta.com \
--cc=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).