From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Bohac Subject: Re: IPv6: autoconfiguration and suspend/resume or link down/up Date: Wed, 20 Jul 2011 18:36:56 +0200 Message-ID: <20110720163656.GD11692@midget.suse.cz> References: <20110719180222.GA7509@midget.suse.cz> <1311178905.21004.9.camel@dcbw.foobar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jiri Bohac , netdev@vger.kernel.org, Herbert Xu , "David S. Miller" , stephen hemminger To: Dan Williams Return-path: Received: from cantor2.suse.de ([195.135.220.15]:36614 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751740Ab1GTQg6 (ORCPT ); Wed, 20 Jul 2011 12:36:58 -0400 Content-Disposition: inline In-Reply-To: <1311178905.21004.9.camel@dcbw.foobar.com> Sender: netdev-owner@vger.kernel.org List-ID: On Wed, Jul 20, 2011 at 11:21:43AM -0500, Dan Williams wrote: > ... and in the resume handler use that value to age anything > that needs to know about time spent in suspend, and then do what needs > to be done with that. So something like that may work for IPv6 > addrconf; on suspend save current time, and on resume check the current > time, subtract the time you saved on suspend, and magically add that to > the lifetime counts and then run any expiry stuff. IPv6 (by specification) does not send any RS when an IP address or route expires. So only subtracting the supend time from the lifetimes and possibly expiring the routes/IP addresses won't fix the problem. When I move to a new network, I need to restart the autoconfiguration. This does not currently happen - neither for an alive system where the ethernet link goes down/up, nor for a system that gets suspended, moved and then resumed. -- Jiri Bohac SUSE Labs, SUSE CZ