I think that's part of the joke
On Sat, Aug 31, 2013 at 12:32 AM, Andrea Shepard wrote:
> On Sat, Aug 31, 2013 at 12:27:22AM -0400, grarpamp wrote:
> > On 8/30/13, Andrea Shepard wrote:
> > > On Tue, Aug 27, 2013 at 11:08:34AM -0500, Jon Gardner wrote:
> > >> Then why have exit policies? Exit n
On 8/30/13, Andrea Shepard wrote:
> On Tue, Aug 27, 2013 at 11:08:34AM -0500, Jon Gardner wrote:
>> Then why have exit policies? Exit nodes regularly block "unwelcome"
>> traffic
>> like bittorrent, and there's only a slight functional difference between
>> that
>> and using a filter in front of t
On Sat, Aug 31, 2013 at 12:27:22AM -0400, grarpamp wrote:
> On 8/30/13, Andrea Shepard wrote:
> > On Tue, Aug 27, 2013 at 11:08:34AM -0500, Jon Gardner wrote:
> >> Then why have exit policies? Exit nodes regularly block "unwelcome"
> >> traffic
> >> like bittorrent, and there's only a slight funct
On 08/31/2013 09:25 AM, Mike Perry wrote:
> People with Munin setups: it would be especially useful if you could
> post links/graph images for connection counts, bandwidth, and CPU load
> since 8/19.
I have Munin data for three servers (each running two Tor instances):
https://v-yu.com/servers/muni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Since I originally started keeping an eye on these on my Raspberry Pi
relay (read: slow, resource-limited), I've got to wonder if the
circuit creation storms I was seeing months ago weren't normal network
phenomena but some kind of test run.
We are
To try to get to the bottom of the recent influx of clients to the Tor
network, it might be useful to compare load characteristics since 8/19
for nodes with different types of flags.
People with Munin setups: it would be especially useful if you could
post links/graph images for connection counts,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 30 Aug 2013 16:27:12 +0100
mick wrote:
> I'm currently seeing more than a doubling of connections (from a mean
> of c. 2000 established connections to just over 5000) on my relay at
> 0xbaddad. The log is full of the (expected) messages:
> "Y
On Tue, Aug 27, 2013 at 11:08:34AM -0500, Jon Gardner wrote:
> Then why have exit policies? Exit nodes regularly block "unwelcome" traffic
> like bittorrent, and there's only a slight functional difference between that
> and using a filter in front of the node to block things like porn
There's a c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This new Guy has absolutely seen a huge increase in connections but
don't have much history to go by but it seems to have doubled several
times in a very short span. interested to sit back & hope to see some
of the guru's weigh in.
-BEGIN PGP SIGNA
On Fri, Aug 30, 2013 at 04:25:27PM -0400, t...@t-3.net wrote:
>
> Also see a repeat of the odd log message with the 154.x net address
> someone else described with the huge hexidecimal string (40 hex
> chars, + sign, 40 more, on and on).
Just FYI, these messages were popping up pretty regularly i
On 8/29/2013 11:09 PM, Andreas Krey wrote:
> On Thu, 29 Aug 2013 19:35:37 +, Gordon Morehouse wrote:
> ...
>> Aug 29 18:19:14.000 [notice] Your network connection speed appears to
>> have changed. Resetting timeout to 60s after 18 timeouts and 172
>> buildtimes.
> Random data point: I had these
On 8/30/2013 1:04 PM, Andy Isaacson wrote:
> On Fri, Aug 30, 2013 at 11:38:26AM -0400, That Guy wrote:
>>> I run an exit node off of a residential Verizon connection and I
>>> haven't seen a single threat, legal or otherwise so far, I dunno
>>> why you're having so much trouble.
>> Thank you for
On 30.08.2013 22:26, David Carlson wrote:
> I have recently seen several e-commerce websites blocking all traffic
> coming from IP addresses that are known to be used by Tor relays,
> including non-exit relays. That means _all_ traffic, including
> legitimate traffic. In my personal experience, A
I added a second core to my server and it's still getting "Your
computer is too slow..." error messages. Top shows cpu for the Tor
process hanging around 60-75%, which is where it was before. Top's
system total is hanging around "Cpu(s) 25.9%". That plus the VM
manager's graph suggest that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/2013 12:28 PM, Stracci wrote:
> I can also confirm that I'm seeing that message on all 4 of my
> exit's too. (as well as nearly double the amount of connections).
I see it on my nodes also, as recently as 0801 GMT on 29 August 2013.
This jus
On Fri, Aug 30, 2013 at 11:38:26AM -0400, That Guy wrote:
> > I run an exit node off of a residential Verizon connection and I
> > haven't seen a single threat, legal or otherwise so far, I dunno
> > why you're having so much trouble.
>
> Thank you for the reply but I have not either. My commen
I am new here. Just started my first Tor exit ("privshield") one day ago, so I
guess it is still "warming up"?! At the last heartbeat it only had 14 circuits
open. For what it's worth: the same 504 gateway time out with a ridiculously
long URL of hexdigits is in my logs:
Aug 29 23:19:59.000 [wa
On Fri, Aug 30, 2013 at 04:27:12PM +0100, mick wrote:
> I'm currently seeing more than a doubling of connections (from a mean of
> c. 2000 established connections to just over 5000) on my relay at
> 0xbaddad. The log is full of the (expected) messages:
> "Your computer is too slow to handle this ma
Our relay is a few weeks old and I think it is still in the process of
ramping up its utilization to its configured max. Because of that,
I find it hard to judge what may be excessive on it.
The last log on our server had it at 13,110 circuits open. Yesterday
it hit 10,000 once but seemed to be
Right after I finished sending my first reply to this thread, messages
about too many circuit requests became visible in the logs. We'll see
if adding cores helps ...
On Friday 30/08/2013 at 12:38 pm, Stracci wrote:
I can also confirm that I'm seeing that message on all 4 of my exit's
I can also confirm that I'm seeing that message on all 4 of my exit's too. (as
well as nearly double the amount of connections).
-Stracci
- Original Message -
From: "mick"
To: tor-relays@lists.torproject.org
Sent: Friday, August 30, 2013 9:27:12 AM
Subject: [tor-relays] huge increase in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I'm currently seeing more than a doubling of connections (from a mean of
> c. 2000 established connections to just over 5000) on my relay at
> 0xbaddad. The log is full of the (expected) messages:
> "Your computer is too slow to handle this many ci
I'm currently seeing more than a doubling of connections (from a mean of
c. 2000 established connections to just over 5000) on my relay at
0xbaddad. The log is full of the (expected) messages:
"Your computer is too slow to handle this many circuit creation
requests!"
I guess this is related to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I run an exit node off of a residential Verizon connection and I
> haven't seen a single threat, legal or otherwise so far, I dunno
> why you're having so much trouble.
Thank you for the reply but I have not either. My comments come from
reading
On 8/29/2013 9:17 PM, Gordon Morehouse wrote:
> Bryan Carey:
> > It's possible. One should always review all configuration files
> > before making their node operational. You can't assume that it will
> > be configured in a particular manner.
>
> > I mean, who would have thought the TBB would ship
25 matches
Mail list logo
