-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/3/2012 8:44 AM, Tim Wilde wrote:
> On 12/30/2011 2:26 PM, Sebastian Urbach wrote:
>> Anyway, traffic on my relay dropped dramatically and the network
>> transmission time is already increasing in the same way.
>> Some
lays have not seen the dramatic drop; I'm not yet sure what
the difference between them is though.
Tim
- --
Tim Wilde, Software Engineer, Team Cymru, Inc.
twi...@cymru.com | +1-847-378- | http://www.team-cymru.org/
-BEGIN
his node would have been able to attract
traffic by now (>12 hours after it was started).
Thanks,
Tim
- --
Tim Wilde, Senior Software Engineer, Team Cymru, Inc.
twi...@cymru.com | +1-847-378- | http://www.team-cymru.org/
-BEGIN PGP SIGNATURE-
iEYEARECAAYFAk7rVv0ACgkQluRbRini9tiROQ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/2011 10:34 PM, Mike Perry wrote:
> Thus spake Tim Wilde (twi...@cymru.com):
>
>> We're not seeing source port exhaustion, but we are seeing two
>> warns, one of which I haven't been able to nail down:
>>
&
hy BigBoy isn't
affected though, and I haven't been able to definitively prove
anything yet, so I'm just not sure.
Let me know if any more info would be of use (or if anyone has any
ideas about that first message).
Thanks,
Tim
- --
Tim Wilde, Senior Software Engineer, Team Cymru,
x27;m pushing around
600Mb/sec total in+out on my piece of bit iron so I'm much closer to
the same ballpark than I thought. Thanks, and thanks again for your
documentation!
Regards,
Tim
- --
Tim Wilde, Senior Software Engineer, Team Cymru, Inc.
twi...@cymru.com | +1-847-378- |
I've found on your
pages (awesome resource, by the way, thanks for that!) the best I've
been able to manage is ~250Mbps on a single Tor instance, I've had to
use multiple instances on the same hardware to try to get any closer
to filling Gbit.
Thanks,
Tim
- --
Tim Wilde, Sen
