[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: active connections when hibernating
On Fri, 13 Jul 2007 14:59:44 -0700 "Michael_google gmail_Gersten"
<keybounce@xxxxxxxxx> wrote:
>Hours? Possibly. They'll stay open until the other side closes them,
>as I understand; that's one hour by default.
But those are client-side connections. When routers connect to other
routers, they tend to keep those connections open. As I understand it,
this not only avoids the unnecessary overhead of tearing down and setting
up new connections to the same places repeatedly, it provides another
obstruction to anyone trying to do traffic analysis.
BTW, please do *not* top-post. It makes it much more difficult to
follow the discussion in a thread. Use an editor, and intersperse your
comments/responsses in the appropriate places.
>
>Days? No, that's not, as I understand, supposed to happen.
Again, that shouldn't be true of router-side connections.
>Heck, if I shut down my or-port (so no new connections arrive), and
>turn it off in my browser (so no new outgoing connections are made),
The client is supposed to continue to maintain some circuits, so
that some will be ready for use anytime the client should come to need
them. Because circuits are old after ten minutes, no new connections
are made through them, and they are torn down when the last connection
through them is closed. In order to keep circuits available, the client
therefore must keep building new circuits from time to time to replace
the ones that get aged and closed.
>then my tor winds up with no sockets open in about 2 hours. (Maybe
>less, I haven't checked that frequently)
Then perhaps there is something wrong with your network connection
that it breaks all circuits from time to time.
>
>On 7/13/07, Jens Kubieziel <maillist@xxxxxxxxxxxx> wrote:
>> * Michael_google gmail_Gersten schrieb am 2007-07-13 um 21:37 Uhr:
>> > What do you mean by "Hibernating"?
>>
>> The AccountingMax bytes were exceeded, so it transports no traffic.
>>
>> > Any process will need to be running in order to close connections;
>> > otherwise, the kernel has to at least track that "This connection has
>> > been closed by the other side, but not yet acknowledged as closed by
>> > this side.".
>>
>> Well, but those timeouts shouldn't last hours or days, IMHO.
>>
>> Besten Gru=DF
>>
>> --
>> Jens Kubieziel http://www.kubieziel.de
>> Wenn zwei Menschen immer die gleiche Meinung haben, ist einer von ihnen
>> =FCberfl=FCssig. Sir Winston Spencer Churchill
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFGl9koVm02LO4Jd+gRAvTUAKCghr0xBfBjgS1FrxfV42EidLvBfACfZcxN
>> zcQE7JvCV5VNYBm1WEXZ1w4=3D
>> =3DrRb4
>> -----END PGP SIGNATURE-----
>>
Scott Bennett, Comm. ASMELG, CFIAG
**********************************************************************
* Internet: bennett at cs.niu.edu *
*--------------------------------------------------------------------*
* "A well regulated and disciplined militia, is at all times a good *
* objection to the introduction of that bane of all free governments *
* -- a standing army." *
* -- Gov. John Hancock, New York Journal, 28 January 1790 *
**********************************************************************