Opened 13 years ago

Last modified 4 years ago

#318 closed defect (Duplicate)

Hibernating disables local socks proxy

Reported by: mark Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: mark Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Version: tor-0.1.1.23

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.

Suggestion:

  • 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]

Child Tickets

Change History (4)

comment:1 Changed 13 years ago by nickm

This is the same problem as bug 192: the solution is to count bytes separately
if they're on (or on behalf of!) a socks connection. Closing as duplicate.

comment:2 Changed 13 years ago by nickm

flyspray2trac: bug closed.
Duplicate of bug 192.

comment:3 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:4 Changed 4 years ago by federico3

Reopened as #2129

Note: See TracTickets for help on using tickets.