- tor-relays - lists.torproject.org

Fast Exit Node Operators - ISP in US
by SiNA Rabbani 30 Nov '14

30 Nov '14

Dear Relay Operators, I noticed there are very few US based exit nodes in the network. And more and more people are jumping on the same set of AS numbers in Europe. I am not if the reason is lack of Tor friendly ISPs or people are just too freaked out about the summer of Snowden. I think it's very wrong to assume that EU countries are not part of the world-wide-wiretap, packets are going through a few internet exchanges anyways. I have been hosting/operating Faravahar (one of the authority directory servers) at Rethem Hosting (rethemhosting.net) for a couple of years now, and never had any issues. I also just brought up 2 exit nodes there: https://atlas.torproject.org/#details/A5B1C342B316C2AE5695B903CED18F619A836… https://atlas.torproject.org/#details/6FFCDF910C32D620FCC6EEF7A8A57F3E9A234… If anyone is interested in running fast Tor Exit nodes at Rethem Hosting. Feel free to contact me directly, so I can make proper referral/introductions. Rethem Hosting is also able to provide hosting In IceLand, but you get the most bang for your buck in the US datacenter. Thank you for contributing to Tor. All the best, SiNA # Consensus Weights Advertised Bandwidth Guard Probability Middle Probability Exit Probability Nickname Fingerprint Exit Guard Country Autonomous System 1.5958% 0.0000% 0.0000% 0.0000% 4.8946% (11 other relay groups) 17.6751% 0.0000% 0.0000% 0.0000% 54.2124% (total in selection) 1 4.1722% 0.0000% 0.0000% 0.0000% 12.7968% * (26 relays) (26) (22) FR (4) 2 3.8256% 0.0000% 0.0000% 0.0000% 11.7338% * (19 relays) (19) (16) DE (6) 3 2.1098% 0.0000% 0.0000% 0.0000% 6.4712% * (10 relays) (10) (8) NL (6) 4 1.4620% 0.0000% 0.0000% 0.0000% 4.4843% * (5 relays) (5) (5) RO (1) 5 0.9090% 0.0000% 0.0000% 0.0000% 2.7881% * (6 relays) (6) (5) SE (4) 6 0.8788% 0.0000% 0.0000% 0.0000% 2.6955% * (4 relays) (4) (4) CH (2) 7 0.8560% 0.0000% 0.0000% 0.0000% 2.6255% * (3 relays) (3) (3) LU (1) 8 0.6510% 0.0000% 0.0000% 0.0000% 1.9967% * (1 relays) (1) (1) LR (1) 9 0.6433% 0.0000% 0.0000% 0.0000% 1.9731% * (10 relays) (10) (8) US (10) 10 0.5715% 0.0000% 0.0000% 0.0000% 1.7528% * (2 relays) (2) (2) GB (1)

17 40

Re: [tor-relays] Fast Exit Node Operators - ISP in US
by teor 23 Nov '14

23 Nov '14

> Date: Sat, 22 Nov 2014 17:58:37 -0800 > From: Seth <list(a)sysfu.com> > ... > > I should have also mentioned in my previous post I put the following in > /etc/tor/torrc > > # Bandwidth and data caps > AccountingStart day 19:45 # calculate once a day at 7:45pm > AccountingMax 33 GBytes # 33GB X 30 days = 10GB shy of 1000GB/mo. > RelayBandwidthRate 3000 KBytes > RelayBandwidthBurst 3750 KBytes # allow higher bursts but maintain average There are 7/12 months that have 31 days, where your 33GB per day will result in a (potential) 23GB overuse. (And that's not including non-tor traffic like OS updates.) Why not use 32GB x 31 days = 992GB, or 31GB x 31 days = 961GB ? teor pgp 0xABFED1AC hkp://pgp.mit.edu/ https://gist.github.com/teor2345/d033b8ce0a99adbc89c5 http://0bin.net/paste/Mu92kPyphK0bqmbA#Zvt3gzMrSCAwDN6GKsUk7Q8G-eG+Y+BLpe7w…

3 2

(no subject)
by Chris Boyd 23 Nov '14

23 Nov '14

http://estudiohalabi.cl/problem.php?4z0oxj4vkg5 wodencafe wodencafe(a)gmail.com +++++++++++++ Penalty for premature evacuation. -- Reality Bites

2 1

wild swings in Advertised Bandwidth
by jchase 23 Nov '14

23 Nov '14

Hi, I'm running a low-volume bridge on a raspberry pi. Globe.torproject says that my fingerprint is 1BCD3EBEFE17EEB86EEDE21D5E2DB8468E2864CF . I'm keeping an eye on myself and traffic via globe.torproject and my advertised bandwidth makes wild swings: one day its 56 kB/s and the next day it's 8 kB/s. When I read that "The minimum BandwidthRate setting is 20 kilobytes per second", I am confronted with the fact that 8 is less than 20 and it doesn't seem worth it keeping my bridge up and working. Why would a bridge make such swings in advertised bandwidth? And is there any good reason to keep the bridge up and working if it sinks to 8 kB/s? Thanks, J Chase

2 1

Decision on Dedicated Server for Exit Node
by Libertas 23 Nov '14

23 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I've been looking for a budget dedicated server to host an exit node on, and the best option I've found is BalticServers. However, they're already listed on the GoodBadISPs wiki page, and because they're in Northeast Europe (Lithuania, to be precise) I'm concerned that their ISP already has more exit nodes than is healthy for network diversity. Is it a good idea to host another exit node there? If you think there's a better option, I'd appreciate it if you could tell me either publicly or privately. Thanks, Libertas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUb8qfAAoJELxHvGCsI27Nx0sP/j5wBhV7EJZZ4EJoPgnoEH8A i6cDB3sL+Q50MgZivZLG47U+wdj95EJeIRl16RsaL0JaShVwyvbpStaIuhpOoujX FN0oumg3Z27fists+CSImLAHHHyr3a526XbWQazKZ7ReBvBZeIOa4PKA/OWsI8wg CWogwEWxbVNMojWaHMID3Y43qEeSH/T0R9ibqyrvqoZrOhnVqH1+1HzVs4FAWoST UMS2m/+b1qL4riL20XyaS0SUO0OkNbL3ecBnCN9LZJwMMuXVB4QNrsBSNFtDTpeu r8ZPJ/DxLJuQOtOvluSqqriKZCCi2lFAHovcXAf2ele0xqPrnJLFXDvhKkuAlv2o wQb+hdpBZ95u073cu/md8vTYVzA8NJ/sRTPmsWtxdRR8PMVpx59+BOAWNYMLWgEu JdTVinsbaWuKKTCtsZY0KAmYRbYC8E0O46z3OnOaeLX2s4MLUK/rPV3FoOAJ0tA3 ixnJ0kjuaFiBN7SRn+N4imBEmt5DP3cbPmai6YX5FzaL0RjlD+1uWk/ZxV66iK3c YrisgQ0bWFbVCGeztblvBGQF3o6cElCJ26Cvy3EaTn7No+1d4f+/1rYwYCmNHjYY mdfUhSfWWFNv+oaF9MU/IHek45l+yrTHHZlhrk3pmFX/bcUWWcfcYX1D/aMhgH58 7p48+5liXZOtSuVK44aS =/fUH -----END PGP SIGNATURE-----

4 4

Website no longer available from Tor
by Marcello Vitagliano 22 Nov '14

22 Nov '14

Hi from a few weeks the site spacemarc.it is no longer accessible via TOR. My hosting does not apply any filter nor I do it from code. I do not get any error from web server (forbidden, timeout and so on...) but the Tor Browser (v4.0.1) simply tries to connect for several seconds but to no avail (try yourself please). I checked the Apache logs and I do not see any request from an IP Tor. In your opinion why is not it more accessible? Thanks

3 3

building Tor against LibreSSL 2.1.1 fails with "undefined reference to `EVP_aes_128_ctr'" error
by Seth 22 Nov '14

22 Nov '14

I'm trying to build tor-0.2.5.10 from source against LibreSSL 2.1.1 on a FreeBSD 9.3x jail system. It fails with this message ----------------------------------- CC src/tools/tor-gencert.o CCLD src/tools/tor-gencert src/common/libor-crypto.a(aes.o): In function `aes_new_cipher': /usr/local/src/tor-0.2.5.10/src/common/aes.c:100: undefined reference to `EVP_aes_128_ctr' *** [src/tools/tor-gencert] Error code 1 Stop in /usr/local/src/tor-0.2.5.10. *** [all] Error code 1 Stop in /usr/local/src/tor-0.2.5.10. -------------------------------------- Has anyone has any luck building Tor against LibreSSL? -- Seth I <3 nicely trimmed email replies

2 2

OrPort self-testing sometimes fails
by Julien ROBIN 22 Nov '14

22 Nov '14

Hi everybody, Second time it happen to me so I would like to know if you have ideas about it. Sometimes after a reboot, I haven't the following message into the log : "Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor." And after a while (fortunately), I receive a warning (Tor Weather) because my server is shown as offline. So I just type /etc/init.d/tor stop and /etc/init.d/tor start, and it works fine. I would like to know how does the test works, in order to check what can fail during the test. If my server's IP (95.130.9.190) is not reachable by a part of the Internet for example, in order to open a support ticket with my ISP (do you know how I can easily check it ?). Also, since few month now, the bandwith usage seems to keeps far below what I had before (even with a good consensus weight, fresh OS install with new keys and name a month ago) so I now realize that may be there is a problem somewhere with this machine. Thank you in advance for your help and ideas ! Best Regards, Julien ROBIN ---- Please find below the logs of the "failed" start, followed by the "working" start Nov 21 11:56:53.000 [notice] Tor 0.2.5.10 (git-43a5f3d91e726291) opening log file. Nov 21 11:56:53.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Nov 21 11:56:53.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Nov 21 11:56:53.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Nov 21 11:56:53.000 [notice] Caching new entry debian-tor for debian-tor Nov 21 11:56:53.000 [notice] Caching new entry debian-tor for debian-tor Nov 21 11:56:53.000 [notice] Your Tor server's identity key fingerprint is 'MagnetronFR1 145AEE9359A8943189500C5451722CAA7EEEC6C3' Nov 21 11:56:53.000 [notice] Bootstrapped 0%: Starting Nov 21 11:56:57.000 [notice] We now have enough directory information to build circuits. Nov 21 11:56:57.000 [notice] Bootstrapped 80%: Connecting to the Tor network Nov 21 11:56:57.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Nov 21 11:56:58.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Nov 21 11:57:00.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Nov 21 11:57:00.000 [notice] Bootstrapped 100%: Done Nov 21 13:56:58.000 [notice] Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Nov 21 13:57:28.000 [notice] Clean shutdown finished. Exiting. Nov 21 13:57:39.000 [notice] Tor 0.2.5.10 (git-43a5f3d91e726291) opening log file. Nov 21 13:57:39.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Nov 21 13:57:39.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. Nov 21 13:57:39.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. Nov 21 13:57:39.000 [notice] Caching new entry debian-tor for debian-tor Nov 21 13:57:39.000 [notice] Caching new entry debian-tor for debian-tor Nov 21 13:57:39.000 [notice] Your Tor server's identity key fingerprint is 'MagnetronFR1 145AEE9359A8943189500C5451722CAA7EEEC6C3' Nov 21 13:57:39.000 [notice] Bootstrapped 0%: Starting Nov 21 13:57:39.000 [notice] Bootstrapped 5%: Connecting to directory server Nov 21 13:57:41.000 [notice] We now have enough directory information to build circuits. Nov 21 13:57:41.000 [notice] Bootstrapped 80%: Connecting to the Tor network Nov 21 13:57:41.000 [notice] Bootstrapped 85%: Finishing handshake with first hop Nov 21 13:57:41.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Nov 21 13:57:43.000 [notice] Bootstrapped 90%: Establishing a Tor circuit Nov 21 13:57:44.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Nov 21 13:57:44.000 [notice] Bootstrapped 100%: Done

2 1

[Tor Weather] Node Down! - AccountingMax and ORPort 80
by Chuck Peters 21 Nov '14

21 Nov '14

I thought it might be nice to run a relay only node with ORPort 80 because it might make tor more available to some users where blocking occurs. And to limit unexpected expenses I calculated 220GB a week would be good. Now I have found out why running ORPort 80 with AccountingMax is a problem... Can I work around this issue of after hibernation the node won't bind to port 80? Or do I need to set it to something above port 1024, for example the default port 9001? Initial setup includes the following: ORPort 80 AccountingMax 220 GB AccountingStart week 7 00:00 After a few weeks running the node, day 7 of the week's AccountingMax Tor Weather reports Node Down! Date: Sat, 15 Nov 2014 15:52:45 -0000 Subject: [Tor Weather] Node Down! Nov 15 14:15:09.000 [notice] Bandwidth soft limit reached; commencing hibernation. No new connections will be accepted Nov 15 15:37:55.000 [notice] Heartbeat: Tor's uptime is 10 days 12:00 hours, with 68 circuits open. I've sent 315.47 GB and received 315.06 GB. We are currently hibernating. ... Nov 16 00:00:00.000 [notice] Hibernation period ended. Resuming normal activity. Nov 16 00:00:00.000 [notice] Opening Socks listener on 127.0.0.1:9050 Nov 16 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:80 Nov 16 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied I restart the server, after a bit of downtime. [1]. Following week on day 5 of the AccountingStart week I am approaching the limit again and decide to try a daily AccountingMax, and then perhaps I could restart the server with cron at 5:01, but that isn't going work well with random hibernation. ORPort 198.211.99.146:80 IPv4Only AccountingMax 32 GB AccountingStart day 05:00 Then Node Down again, this time it happens right after the AccountingStart resets. Date: Fri, 21 Nov 2014 07:13:07 -0000 Subject: [Tor Weather] Node Down! Nov 21 05:00:00.000 [notice] Configured hibernation. This interval began at 2014-11-21 05:00:00; the scheduled wake-up time is 2014-11-21 06:20:24; we expect to exhaust our quota for this interval around 2014-11-22 04:16:24; the next interval begins at 2014-11-22 05:00:00 (all times local) Nov 21 05:00:01.000 [notice] Commencing hibernation. We will wake up at 2014-11-21 06:20:24 local time. Nov 21 05:00:01.000 [notice] Going dormant. Blowing away remaining connections. Nov 21 06:20:24.000 [notice] Hibernation period ended. Resuming normal activity. Nov 21 06:20:24.000 [notice] Opening Socks listener on 127.0.0.1:9050 Nov 21 06:20:24.000 [notice] Opening OR listener on 198.211.99.146:80 Nov 21 06:20:24.000 [warn] Could not bind to 198.211.99.146:80: Permission denied ... after logrotate runs Nov 21 07:46:25.000 [warn] Could not bind to 198.211.99.146:80: Permission denied Nov 21 07:46:25.000 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Nov 21 07:46:25.000 [err] Reading config failed--see warnings above. For usage, try -h. Nov 21 07:46:25.000 [warn] Restart failed (config error?). Exiting. I would like to run an exit node, but the advise seems to be try a relay only node for 6 months to a year first... It seems it might be more of an issue with expenses that might prevent me from running an exit node, or multiple nodes. I'l upgrade the VPS to the 2TB transfer, but that might be after the holidays. However I suspect that it will only be a matter of days or weeks before I run into the AccountingMax limits and that may preclude changing the configuration to be an exit node. 1. Downtime starting the 15th. eth0 08:59 ^ t | rt rt | rt rt rt | rt rt rt | t rt rt rt rt | rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt | rt rt rt rt rt rt rt rt rt rt rt rt -+---------------------------------------------------------------------------> | 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 00 01 02 03 04 05 06 07 08 h rx (KiB) tx (KiB) h rx (KiB) tx (KiB) h rx (KiB) tx (KiB) 09 1,380,268 1,409,649 17 1,244 2,753 01 3,117 6,815 10 1,383,154 1,407,057 18 1,100 1,720 02 161,632 164,035 11 1,143,056 1,163,393 19 706 228 03 1,564,910 1,578,327 12 1,920,541 1,953,502 20 127 201 04 1,036,805 1,054,792 13 2,719,316 2,742,037 21 675 222 05 1,630,340 1,644,128 14 854,474 869,997 22 124 150 06 3,189,069 3,215,147 15 81,036 82,419 23 732 324 07 2,952,173 2,999,409 16 52,548 52,515 00 6,367 2,718 08 2,115,794 2,150,727 ------------------------------------------------------------------------------- And some other stats that seem to follow the expected life cycle. day rx | tx | total | avg. rate ------------------------+-------------+-------------+--------------- 10/06/2014 28.32 MiB | 13.31 MiB | 41.63 MiB | 0.49 KiB/s 10/07/2014 37.10 MiB | 30.33 MiB | 67.43 MiB | 0.80 KiB/s 10/08/2014 200.13 MiB | 170.99 MiB | 371.12 MiB | 4.40 KiB/s 10/09/2014 194.58 MiB | 188.91 MiB | 383.49 MiB | 4.55 KiB/s 10/10/2014 578.48 MiB | 588.95 MiB | 1.14 GiB | 13.84 KiB/s 10/11/2014 1.09 GiB | 1.10 GiB | 2.19 GiB | 26.62 KiB/s 10/12/2014 1.34 GiB | 1.34 GiB | 2.68 GiB | 32.57 KiB/s 10/13/2014 977.57 MiB | 984.14 MiB | 1.92 GiB | 23.25 KiB/s 10/14/2014 1.68 GiB | 1.67 GiB | 3.34 GiB | 40.56 KiB/s 10/15/2014 1.35 GiB | 1.36 GiB | 2.71 GiB | 32.91 KiB/s 10/16/2014 8.49 GiB | 8.58 GiB | 17.07 GiB | 207.20 KiB/s 10/17/2014 11.88 GiB | 12.02 GiB | 23.91 GiB | 290.15 KiB/s 10/18/2014 13.33 GiB | 13.55 GiB | 26.88 GiB | 326.25 KiB/s 10/19/2014 15.95 GiB | 16.19 GiB | 32.15 GiB | 390.12 KiB/s 10/20/2014 12.34 GiB | 12.53 GiB | 24.87 GiB | 301.83 KiB/s 10/21/2014 17.41 GiB | 17.68 GiB | 35.10 GiB | 425.94 KiB/s 10/22/2014 23.84 GiB | 24.21 GiB | 48.04 GiB | 583.08 KiB/s 10/23/2014 26.52 GiB | 26.93 GiB | 53.46 GiB | 648.77 KiB/s 10/24/2014 26.19 GiB | 26.60 GiB | 52.79 GiB | 640.64 KiB/s 10/25/2014 24.77 GiB | 25.13 GiB | 49.89 GiB | 605.53 KiB/s 10/26/2014 32.19 GiB | 32.66 GiB | 64.86 GiB | 787.13 KiB/s 10/27/2014 28.44 GiB | 28.84 GiB | 57.28 GiB | 695.12 KiB/s 10/28/2014 24.39 GiB | 24.80 GiB | 49.19 GiB | 596.97 KiB/s 10/29/2014 23.66 GiB | 24.04 GiB | 47.70 GiB | 578.94 KiB/s 10/30/2014 26.16 GiB | 26.64 GiB | 52.80 GiB | 640.83 KiB/s 10/31/2014 24.48 GiB | 24.94 GiB | 49.42 GiB | 599.75 KiB/s 11/01/2014 26.62 GiB | 27.02 GiB | 53.64 GiB | 650.94 KiB/s 11/02/2014 26.65 GiB | 27.02 GiB | 53.67 GiB | 651.32 KiB/s 11/03/2014 25.09 GiB | 25.51 GiB | 50.60 GiB | 614.08 KiB/s 11/04/2014 25.06 GiB | 25.43 GiB | 50.49 GiB | 612.75 KiB/s 11/05/2014 27.74 GiB | 28.17 GiB | 55.91 GiB | 678.50 KiB/s 11/06/2014 23.62 GiB | 23.98 GiB | 47.61 GiB | 577.79 KiB/s 11/07/2014 26.63 GiB | 27.06 GiB | 53.69 GiB | 651.61 KiB/s 11/08/2014 30.29 GiB | 30.73 GiB | 61.02 GiB | 740.58 KiB/s 11/09/2014 30.93 GiB | 31.38 GiB | 62.32 GiB | 756.31 KiB/s 11/10/2014 37.56 GiB | 38.16 GiB | 75.72 GiB | 918.98 KiB/s 11/11/2014 33.97 GiB | 34.46 GiB | 68.43 GiB | 830.48 KiB/s 11/12/2014 37.92 GiB | 38.52 GiB | 76.45 GiB | 927.78 KiB/s 11/13/2014 32.15 GiB | 32.65 GiB | 64.80 GiB | 786.41 KiB/s 11/14/2014 36.32 GiB | 36.81 GiB | 73.14 GiB | 887.61 KiB/s 11/15/2014 25.40 GiB | 25.75 GiB | 51.15 GiB | 812.74 KiB/s 11/16/2014 44.23 GiB | 44.88 GiB | 89.11 GiB | 1.06 MiB/s 11/17/2014 44.96 GiB | 45.64 GiB | 90.60 GiB | 1.07 MiB/s 11/18/2014 48.38 GiB | 49.16 GiB | 97.53 GiB | 1.16 MiB/s 11/19/2014 51.38 GiB | 52.33 GiB | 103.71 GiB | 1.23 MiB/s 11/20/2014 43.68 GiB | 44.43 GiB | 88.11 GiB | 1.04 MiB/s 11/21/2014 5.52 GiB | 5.62 GiB | 11.14 GiB | 398.39 KiB/s Chuck

3 2

Re-installed Tor relay node as exit node with same name, different OS.
by Seth 20 Nov '14

20 Nov '14

I recently re-installed the operating system for a VPS that was running Parabola GNU/Linux and acting as a Tor relay. The new OS is OpenBSD 5.6 running tor-0.2.5.10. Instead of running as a relay I modified torrc so it runs a ReducedExitPolicy policy. Initially there were several problems with Tor exit node traffic being blocked by the firewall which has since been resolved. The Tor status page however still does not list this router as an exit node. http://jlve2y45zacpbz6s.onion/router_detail.php?FP=e1e1059d8c41fc48b823c6f0… Any ideas why? -- Seth I <3 nicely trimmed email replies

2 2