From: Jiri Bohac <jbohac@suse.cz>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jiri Bohac <jbohac@suse.cz>,
netdev@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: IPv6: autoconfiguration and suspend/resume or link down/up
Date: Wed, 20 Jul 2011 18:29:53 +0200 [thread overview]
Message-ID: <20110720162953.GC11692@midget.suse.cz> (raw)
In-Reply-To: <20110720091556.619a0c14@nehalam.ftrdhcpuser.net>
On Wed, Jul 20, 2011 at 09:15:56AM -0700, Stephen Hemminger wrote:
> > When the cable is unplugged and plugged in again, we already get
> > notified through linkwatch -> netdev_state_change ->
> > -> call_netdevice_notifiers(NETDEV_CHANGE, ...)
> > However, if the device has already been autoconfigured,
> > addrconf_notify() only handles this event by printing a
> > message.
...
> If the driver drops the link during suspend then the necessary link
> events happen to keep bridging, ipv6, bonding and all the other possible
> network protocols happy.
OK, so maybe providing the link event on suspend/resume should be
left to the drivers.
The main problem persists: IPv6 currently does nothing when the link goes
down and returns. Shouldn't the kernel anticipate that the new
network could be different, forget all the autoconfigured
parameters and restart the autoconfiguration?
--
Jiri Bohac <jbohac@suse.cz>
SUSE Labs, SUSE CZ
next prev parent reply other threads:[~2011-07-20 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:02 IPv6: autoconfiguration and suspend/resume or link down/up Jiri Bohac
2011-07-20 16:15 ` Stephen Hemminger
2011-07-20 16:29 ` Jiri Bohac [this message]
2011-07-20 16:21 ` Dan Williams
2011-07-20 16:36 ` Jiri Bohac
2011-07-21 5:30 ` Dan Williams
2011-07-21 16:35 ` Dan Williams
2011-07-21 19:44 ` Stephen Hemminger
2011-07-22 8:06 ` David Miller
2011-07-22 9:21 ` Herbert Xu
2011-07-23 14:31 ` Nicolas de Pesloüan
2011-07-23 15:27 ` Herbert Xu
2011-07-23 16:37 ` Stephen Hemminger
2011-07-24 0:18 ` Herbert Xu
2011-07-24 8:35 ` Nicolas de Pesloüan
2011-07-25 3:26 ` Stephen Hemminger
2011-07-25 3:46 ` Herbert Xu
2011-07-27 19:48 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2011-07-19 19:42 Stephen Hemminger
2011-07-26 5:16 ` Anirban Chakraborty
2011-07-25 16:55 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=20110720162953.GC11692@midget.suse.cz \
--to=jbohac@suse.cz \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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.