Re: Tor 0.1.2.17 causing high latency after 5 - 6 hours

[Matthieu Dalissier <mdal@xxxxxx>]

phobos@xxxxxxxxxx schrieb:
> On Fri, Sep 28, 2007 at 10:07:50PM +0200, mdal@xxxxxx wrote 20K bytes in 387 lines about:
> : They have all the same configuration, and are bandwith limited with the
> : custom setting to about 75% of the connection.
>
> What do you mean by laggy?  And, is there anything interesting in the
> tor log file during this 'lagginess'?
>
> My guess is if this is on a cable modem, you may be overloading the
> cable modem with tcp connections, or the ISP is considering your traffic
> to be illegal p2p traffic and limiting your bandwidth as a result.
>
>   
By laggy i mean i got a diashow at online gaming(ping  ~500 ms) or in
Teamspeak i got interruptions of the Voice chat. The Tor log File shows
nothing
very exotic to me, there were no warnings at all, but perhaps i am still
too much a noob at it.

that's what is shown, i restarted the server on oct 01:
Okt 01 21:34:19.000 [Hinweis] Tor v0.1.2.17. This is experimental
software. Do not rely on it for strong anonymity.
Okt 01 21:34:19.328 [Hinweis] Initialized libevent version 1.3b using
method win32. Good.
Okt 01 21:34:19.328 [Hinweis] Opening OR listener on 0.0.0.0:443
Okt 01 21:34:19.437 [Hinweis] Opening Socks listener on 127.0.0.1:9050
Okt 01 21:34:19.437 [Hinweis] Opening Control listener on 127.0.0.1:9051
Okt 01 21:34:48.343 [Hinweis] Tor has successfully opened a circuit.
Looks like client functionality is working.
Okt 01 21:34:48.343 [Hinweis] Now checking whether ORPort
80.219.249.125:443 is reachable... (this may take up to 20 minutes --
look for log messages indicating success)
Okt 01 21:34:55.578 [Hinweis] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
Okt 01 21:35:48.109 [Hinweis] Performing bandwidth self-test...done.
Okt 01 21:37:09.000 [Hinweis] Your DNS provider gave an answer for
"zrovrnqdqm.com", which is not supposed to exist.  Apparently they are
hijacking DNS failures. Trying to correct for this.  We've noticed 1
possibly bad addresses so far.
Okt 02 00:07:06.687 [Hinweis] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Okt 02 00:07:06.687 [Hinweis] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'Unnamed'. Retrying on a new circuit.
Okt 02 16:54:30.625 [Hinweis] Your DNS provider has given
"208.69.32.139" as an answer for 7 different invalid addresses.
Apparently they are hijacking DNS failures. I'll try to correct for this
by treating future occurrences of "208.69.32.139" as 'not found'.
Okt 04 01:37:11.953 [Hinweis] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'Anonymity0for0all'. Retrying on a new circuit.
Okt 04 18:27:32.312 [Hinweis] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'canttakethesky'. Retrying on a new circuit.
Okt 04 18:27:32.312 [Hinweis] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'canttakethesky'. Retrying on a new circuit.
Okt 04 18:27:32.312 [Hinweis] We tried for 15 seconds to connect to
'[scrubbed]' using exit 'canttakethesky'. Retrying on a new circuit.

I also thought at my ISP limiting my bandwith, after a few phone calls,
they reassured me that limiting bandwith is not part of their policy.
Besides even if i would do illegal p2p traffic the ISP can't just limit
my bandwith because i pay a price for this bandwith. This would be fraud
If i am overloading the Cablemodem with TCP connections, is there a way
i can see it's limits and how much connections that i have?