Hibernation and client use

[Jim Pick]

Roger Dingledine wrote:
> On Wed, May 11, 2005 at 02:14:00PM -0700, Jim Pick wrote:
> 
>>I've got a new node ("jpicktor").  I just installed it a few days ago 
>>and I went to the BayFF talk last night.  Quite fun.
> 
> Woo. Thanks for the new Tor node. :)

:-)

  >>The hibernation did appear to work, as traffic dried up.  However, it
>>seems that I was also unable to use the node as a client via privoxy and 
>>the socks interface.
> 
> 
> Right. This is because we do accountingmax based on the number of bytes
> coming into the Tor, from any connection type (OR, exit node, socks
> connection, ...)
> 
> When the limit is reached, we figure you don't want to spend any more
> bandwidth.

That's what I thought.  I wasn't sure though.  Thanks for clarifying.

>>I'm wondering if it would be possible to allow client access while 
>>hibernating?  Or is there some technical reason that client access must 
>>be shut down?
> 
> 
> You're right, I bet we could do this. We would close the OR port, and
> refuse incoming create requests, but otherwise continue to perform.
> 
> Would people prefer this behavior, or do they like it the way it is now?

It might be useful to people like me who are mostly interested in using 
the node as a client, but also have some extra bandwidth to donate.

At least, it would be nice to mention on the man page that hibernation 
also shuts off client access.  Since there is no UI, I wasn't sure if it 
was supposed to do that, or if I had just misconfigured something.  Less 
surprise is usually good.  :-)

>>I'm going to try limiting the bandwidth next, at least I should be able 
>>to preserve client access that way...
> 
> As Warren says, the workaround is simple: run a Tor client also, and use
> that for your own stuff.

Yep, that should work as well, at the cost of an additional install.

Cheers,

  - Jim