On Thu, 5 Sep 2013 06:54:57 -0400
Roger Dingledine wrote:
> Hi folks,
>
> I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
>
> It comes with a new feature:
> - Relays now process the new "NTor" circuit-level handshake requests
> with higher priority than the old "
Definitely a newboy questionI ssh into an Ubuntu 13.04 (from Ubuntu 13.04) and see root@vps09:~#.To get a gui going which I can handle I apt-get updateapt-get install ubuntu-desktopboth worked. Restarted.I can't get the gui to start.What is a better way to control and install an exit relay remo
Martin, setting ControlListenAddress to 10.0.0.3:9051 did the trick.
I've also enabled cookie authentication. Obviously ARM running on
something that's not a Tor server to connect to a server's control port
has its limits, but I can still get some useful info. Thanks.
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.09.2013 06:01, Robert Charlton wrote:
> Hello, Tor community. Quick, possibly noobish question. I'd like to
> use my desktop and connect ARM (running on the desktop) to the
> control port of a server running Tor on the same LAN, but it's
> refusi
Hello, Tor community. Quick, possibly noobish question. I'd like to use
my desktop and connect ARM (running on the desktop) to the control port
of a server running Tor on the same LAN, but it's refusing the
connection. I'm running /sudo -u tor arm -i 10.0.0.3:9051/, and it outputs:
robert@CPC-Arch
On Thu, Sep 05, 2013 at 12:08:05PM -0700, Andy Isaacson wrote:
> After 20 minutes of uptime with 17-rc I'm not seeing the CPU pegged like
> it was within minutes of restart with 0.2.3.25, even though we are
> pushing 220 Mbps already.
Here's stats from the last hourly:
==> /var/log/tor/notices1.l
On Thu, Sep 05, 2013 at 10:54:58PM +0200, tor-admin wrote:
> Just noticed that during bootstrap there are new warnings I never noticed
> before. Is this a known issue or should I file a ticket?
>
> Sep 05 21:56:15.000 [warn] Problem bootstrapping. Stuck at 85%: Finishing
> handshake with first h
On Sep 5, 2013, at 20:13 , Kevin C. Krinke wrote:
>
> Machine's performance and resource usage are all within allowed norms (in
> fact running better than the 2.3.x release).
I concur with Kevin that this built is running smoothly:
Sep 05 21:24:37.000 [notice] Circuit handshake stats since las
On Thursday 05 September 2013 22:27:53 tor-admin wrote:
> Updated torland family. Hope that the new version helps. One of the last
> messages before update to 0.2.4.17-rc:
>
> Sep 05 21:06:29.000 [warn] Your computer is too slow to handle this many
> circuit creation requests! Please consider usin
Updated torland family. Hope that the new version helps. One of the last
messages before update to 0.2.4.17-rc:
Sep 05 21:06:29.000 [warn] Your computer is too slow to handle this many
circuit creation requests! Please consider using the
MaxAdvertisedBandwidth config option or choosing a more r
On Thu, Sep 05, 2013 at 06:54:57AM -0400, Roger Dingledine wrote:
> So the more relays that upgrade to 0.2.4.17-rc, the more stable and fast
> Tor will be for 0.2.4 users, despite the huge circuit overload that the
> network is seeing.
>
> Please consider upgrading. If you do, though, please also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nice, thank you :)
Let's see, how Tor reacts on this :D
Roger Dingledine schrieb:
>Hi folks,
>
>I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
>
>It comes with a new feature:
> - Relays now process the new "NTor" circuit-
On 2013-09-05, at 2:00 PM, Elrippo wrote:
>
> Nice, thank you :)
> Let's see, how Tor reacts on this :D
Just a quick note on my exit node's stats:
17:46:33 [NOTICE] Circuit handshake stats since last time: 25849/25857 TAP,
117/117 NTor.
16:46:33 [NOTICE] Circuit handshake stats since last t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Roger Dingledine:
> Hi folks,
>
> I just released 0.2.4.17-rc. Hopefully there will be debs of it
> soon.
I will get binary debs for Raspbian completed this evening, and this
time sign them with my public key[1] for anyone who chooses to trust
me.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upgraded to 0.2.4.17-rc and almost immediately got the following in my
syslog:
debian kernel: [5000394.949751] TCP: Possible SYN flooding on port 443.
Sending cookies. Check SNMP counters.
No idea what it means. 443 is my or port. Tor is running fin
On Thu, 05 Sep 2013 17:04:15 +0200
virii wrote:
> Don't know if this is update specific or just because of the new users
> in the network:
I had this on 0.2.4.16, so not update-specific.
--
With respect,
Roman
signature.asc
Description: PGP signature
_
Hi all,
After running my relay for a bit on my home connection I found that
Tor would happily consume all the bandwidth available, which
(coupled with the number of connections overwhelming my home router,
I suspect) caused my internet connection to be unusable for other
things.
So I set the Rela
Don't know if this is update specific or just because of the new users
in the network:
17:00:25 [WARN] Your Guard curiosity3
($07AE80AA2F475282E3C08F589826C8FB19E8086B) is failing a very large
amount of circuits. Most likely this means
the Tor network is overloaded, but it could also mean an at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Just to add my experiences to the mix:
I started running a RPi relay back in January. It ran fine for several
months, until I started to get these circuit creation storms
periodically. It would come at random times, maybe once a week, and
would some
On Thu, Sep 5, 2013 at 7:12 PM, Lunar wrote:
>
> For those in a hurry, automatically built packages are available by
> adding the following in your sources.list:
>
I see the following messages, which I was not seeing earlier. It
eventually completes bootstrapping, 100%:
Sep 05 22:04:03.000 [no
Upgraded to the nightlies this morning. Everything running peachy keen so far.
Thanks!
On 2013-09-05, at 7:12 AM, Lunar wrote:
> Roger Dingledine:
>> I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
>
> For those in a hurry, automatically built packages are available by
>
On 09/05/2013 03:20 PM, Roger Dingledine wrote:
> On Thu, Sep 05, 2013 at 06:54:57AM -0400, Roger Dingledine wrote:
>> In my spare time I'm also working on a blog post to explain what's going
>> on and what measures we're taking to keep things afloat.
> https://blog.torproject.org/blog/how-to-handl
On Thu, Sep 05, 2013 at 06:54:57AM -0400, Roger Dingledine wrote:
> In my spare time I'm also working on a blog post to explain what's going
> on and what measures we're taking to keep things afloat.
https://blog.torproject.org/blog/how-to-handle-millions-new-tor-clients
--Roger
Roger Dingledine:
> I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
For those in a hurry, automatically built packages are available by
adding the following in your sources.list:
deb http://deb.torproject.org/torproject.org/ tor-nightly-0.2.4.x-wheezy
main
You can repl
Hi folks,
I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
It comes with a new feature:
- Relays now process the new "NTor" circuit-level handshake requests
with higher priority than the old "TAP" circuit-level handshake
requests. We still process some TAP req
25 matches
Mail list logo
