[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Fri, 6 Jun 2008 12:27:47 +0300
From: Nadejda Levitsky <maximlevitsky@...il.com>
To: Benny Amorsen <benny+usenet@...rsen.dk>
Cc: netdev@...r.kernel.org
Subject: Re: How I can reset TCP sockets after long suspend/resume cyscle
On Friday, 6 June 2008 11:37:12 Benny Amorsen wrote:
> Maxim Levitsky <maximlevitsky@...il.com> writes:
>
> > This seems the right solution,
> > if this is possible, why not to check for stuck TCP connections
> > on resume?
>
> Imagine a laptop on wireless going into suspend for a few minutes,
> then getting woken up. If you're lucky today, the TCP connections
> survive.
It depends, I for example don't care about TCP connecions survival during suspend
I would even like to close them on suspend. (I usially use web browser, chat client, mail
maybe a download running in background which can be resumed)
Like I said such feature can be user configured.
There are uses like hibernating your server to change power supply, and still save all
TCP connections.
>
> If you check for stuck TCP connections right after resume, you could
> have problems because the wireless hasn't negotiated encryption keys
> at that point. Isn't that a concern?
Good point, I haven't thought about this.
This means that a in-kernel solution is no-go, but userland solution
can check for such connections _after_ negotiation of wireless keys.
Or, just close all remote TCP connections if the suspend was long enough.
>
>
> /Benny
>
Best regards,
Maxim Levitsky
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists