Tor causing network lags?
mdal at gmx.ch
Thu Jan 24 21:41:34 UTC 2008
There was a little time ago i reported a network lag problem to this
mailing List which was showing when i was running Tor in relay mode. The
discussion ended up, that my ISP could be throttling down my connection.
After a little bandwith testing i couldn't find any ISP-throttling,
because i got no bandwith difference between running Tor and not running
it (ca. 10mb/s down / 1mb/s up), and also the lags happened at all my
relays which do not all run at the same place and do not all run at the
At that time i had Tor 0.1.2.17, the network lags remained also in
0.1.2.18 and i have them also now in 0.1.2.19. RMLAnonSrv1 is running on
a dedicated slackware 12.0 machine in a network of 10 pc's, RMLAnonSrv 2
-6 are standalone Windows XP prof pc's at different places.
RMLAnonSrv1 to 4 have the bandwith set to 80KB/s, the relays 5 and 6 to
32KB/s. All have their ORPort to 443 and no Directory Mirror. Thei'r
torrc all have the standard settings which have been made with vidalia,
except RMLAnonSrv1, where SocksListenAddress is set.
The network lags show while i ping google.ch, normally it's between 20
and 60ms. Periodically the ping time is increasing to 950ms during about
1 - 30 seconds, and sometimes i got even packet losses.
I made during 10min a Debug log file of Tor and a simultaneous "ping -t
google.ch > C:\Pingtest.txt" in a Windows XP prof. cmd shell on
RMLAnonSrv2, which i can send if needed.
Here are the torrc settings for RMLAnonSrv2 - 6:
# This file was generated by Tor; if you edit it, comments will not be
# The old torrc file was renamed to torrc.orig.1 or similar, and Tor
will ignore it
# Limit the maximum token buffer size (also known as burst) to the given
# number of bytes.
# A token bucket limits the average incoming bandwidth on this node to the
# specified number of bytes per second.
# Administrative contact information to advertise for this server.
ContactInfo mdal at gmx dot ch
# If set, Tor will accept connections from the same machine (localhost
# on this port, and allow those connections to control the Tor process
# the Tor Control Protocol (described incontrol-spec.txt).
# Address/port ranges for which to accept or reject outgoing connections on
# behalf of Tor users.
ExitPolicy reject *:*
# Where to send logging messages. Format is minSeverity[-maxSeverity]
# (stderr|stdout|syslog|file FILENAME).
Log notice stdout
# Set the server nickname.
# Advertise this port to listen for connections from Tor clients and
# If non-zero, avoid directory servers that don't support tunneled
# Bind to this address to listen to connections from SOCKS-speaking
# If non-zero, when a directory server we contact supports it, we will
# one-hop circuit and make an encrypted connection via its ORPort.
I hope anybody can help me and please excuse me for my bad english and
for the huge post.
greetz Matthieu Dalissier
More information about the tor-talk