Hibernating disables local socks proxy
Aug 10 17:18:34.175 [notice] consider_hibernation(): Bandwidth soft limit reached; commencing hibernation. Aug 10 17:21:43.194 [notice] hibernate_go_dormant(): Going dormant. Blowing away remaining connections.
Once the bandwidth limit is hit all sockets are closed - including the Socks port. Bandwidth limits allow the user to contribute whatever bandwidth they have available; however it is likely the enduser won't be able to use Tor at all if bandwidth limits are configured. The network may have already used all the allocated bandwidth causing Tor to hibernate. Currently the user is better off disabling "ORPort" and not contributing to the network, this way they can be sure Tor will be available when/if they choose to use it.
- The bandwidth limits should exclude and not account for any connections/data via the local Socks port.
- Hibernate should just temporarily disable "ORPort" once foreign nodes have used the data allocation.
Hope this report helps.
[Automatically added by flyspray2trac: Operating System: BSD]