[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Hibernation and client use

Jim,

I don't think the TOR server with parameters you specified can determine whether your traffic should be allowed over other client connections. The server was given a max option and stopped processing once it reached the limit. Why don't you just set up a client only TOR server for your own personal use on your desktop/laptop?

-Warren.

Jim Pick wrote:

[I'm resending this because I believe my first attempt was blocked due to majordomo subscription issues - my apologies if it gets posted twice]

Hi,

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.

Anyways, I'm playing around with the bandwidth limiting features. My server runs Xen and Linux, and is in a colo (simpli.biz, which is at above.net in San Jose, CA).

I'm using tor 0.0.9.9-1 from Debian unstable.

The man page says this about the AccountingMax option:

  If you have  bandwidth  cost issues, using this option is preferable
  to setting a low bandwidth, since it provides users with a collection
  of fast servers that are up some of the time, which is more useful
  than a set of slow servers that are always "available".

So I tried this:

 AccountingMax 2 GB
 AccountingStart day 0:00

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.

Losing client access wasn't exactly the behaviour I was expecting or hoping for during hibernation. I couldn't find any documentation anywhere saying that hibernation would shut down client access.

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?

I'm going to try limiting the bandwidth next, at least I should be able to preserve client access that way...

Cheers,

 - Jim