- tor-relays - lists.torproject.org

Relay bandwidth
by Tora Tora Tora 09 Feb '14

09 Feb '14

I have configured Tor with the following (with daily accounting): RelayBandwidthRate 384 KB RelayBandwidthBurst 512 KB I always assumed that the burst bandwidth will set the maximum relay bandwidth. However, by using iftop, I can see individual connections with speeds as high as 2+ Mbps. Even when individual connections are not exceeding burst speeds, adding up bandwidth of all connections would probably exceed allowed relay burst bandwidth. Is this because Tor is using up the bandwidth allowance, since it is well below its long-time average or is this something unexpected that should not be happening?

4 5

using Arm to manage nodes
by jason＠icetor.is 08 Feb '14

08 Feb '14

Hello all, This is something that's bothered me for quite some time. I often use arm (https://www.torproject.org/projects/arm.html.en) for monitoring my relays and to keep a quick eye on things like overall bandwidth consumed, traffic stats and my favorite client locale statistics. I run it in a screen session and often when I re-attach the session often the keymapping is all messed up and the arrow keys will offer to close arm. Usually it will correct after I shift-m to get to the menu and switch around a few times. Has anyone else experienced this and how did you solve it? -Jason

6 8

Re: [tor-relays] Trying Trusted Tor Traceroutes
by Sebastian Urbach 08 Feb '14

08 Feb '14

Hi, That's odd, please send us your ip address and we will look into this and get back to you asap. Feel free to send me your ip by private mail if you feel more comfortable. I would suggest that you keep running the script, we will check your submitted data and then we go from there. -- Mit freundlichen Grüssen / Sincerely yours Sebastian Urbach ---------------------------------------------- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. ---------------------------------------------- Benjamin Franklin (1706 - 1790), Inventor, journalist, printer, diplomat and statesman Hi, I've seen this error message twice now within about 12 hours: ssh_exchange_identification: Connection closed by remote host If I read the script correctly, it tries to upload the data and then deletes it without checking for successful upload. Since the data is probably lost, should I start over? Best regards, Alexander --- PGP Key: 0xC55A356B | https://dietrich.cx/pgp On 2014-02-07 22:05, Sebastian Urbach wrote: > Dear list members, > The Trying Trusted Tor Traceroutes project is coming closer to the > next data review (03/2014). > Basically every relay (except Bridges) can help to evaluate the Tor > Routes. Please consider that one complete run takes about 4 days with > the default settings. > It's really easy to participate, just download and run the script ! We > are currently at 82 completed runs and i think 100 is a great > milestone :-) > The project website: > http://web.engr.illinois.edu/~das17/tor-traceroute_v1.html > The scoreboard with the results: > http://datarepo.cs.illinois.edu/relay_scoreboard.html > Thank you for your help ! > -- > Mit freundlichen Grüssen / Sincerely yours > Sebastian Urbach > ---------------------------------------------- > Those who would give up essential Liberty, > to purchase a little temporary Safety, deserve > neither Liberty nor Safety. > ---------------------------------------------- > Benjamin Franklin (1706 - 1790), Inventor, > journalist, printer, diplomat and statesman > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

Checking a bridge
by Martin Kepplinger 08 Feb '14

08 Feb '14

When my bridge uses only the same few MBs each day, i guess it isn't used at all right? Is there a simple way to ensure it is in bridgeDB and functioning as it should? thanks, martin

8 8

Trying Trusted Tor Traceroutes
by Sebastian Urbach 08 Feb '14

08 Feb '14

Dear list members, The Trying Trusted Tor Traceroutes project is coming closer to the next data review (03/2014). Basically every relay (except Bridges) can help to evaluate the Tor Routes. Please consider that one complete run takes about 4 days with the default settings. It's really easy to participate, just download and run the script ! We are currently at 82 completed runs and i think 100 is a great milestone :-) The project website: http://web.engr.illinois.edu/~das17/tor-traceroute_v1.html The scoreboard with the results: http://datarepo.cs.illinois.edu/relay_scoreboard.html Thank you for your help ! -- Mit freundlichen Grüssen / Sincerely yours Sebastian Urbach ---------------------------------------------- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. ---------------------------------------------- Benjamin Franklin (1706 - 1790), Inventor, journalist, printer, diplomat and statesman

6 6

Onion address or clearnet address
by Hang 07 Feb '14

07 Feb '14

Some sites such as RiseUp and DuckDuckGo could be accessed via onion addresses. I would like to know which address (onion address vs clearnet address) should I use when using TBB. I believe both ways are more or less the same in terms of identity protection and communication security (provided that the clearnet addresses are using HTTPS). Perhaps the main difference is using the clearnet addresses adds burden to the exit relays, while using onion addresses only consumes bandwidth of middle relays which is relatives more in supply. Am I right? Do I overlook anything? Or it doesn't matter at all for either way? Best Hang

4 5

duplicated log output after SIGHUP
by Scott Bennett 07 Feb '14

07 Feb '14

I made a minor change to my torrc file and sent tor a SIGHUP. The only logging I'm doing is "notice" level to a file. Here's what has been going on since the SIGHUP. Feb 06 22:32:01.201 [notice] Heartbeat: Tor's uptime is 10 days 3:00 hours, with 206 circuits open. I've sent 8.22 GB and received 7.72 GB. Feb 06 22:32:01.201 [notice] Average packaged cell fullness: 77.286% Feb 06 22:32:01.201 [notice] TLS write overhead: 12% Feb 06 23:10:33.967 [notice] Received reload signal (hup). Reloading config and resetting internal state. Feb 06 23:10:33.967 [notice] Read configuration file "/usr/local/etc/tor/torrc". Feb 06 23:10:33.976 [warn] Skipping obsolete configuration option 'MaxOnionsPending' Feb 06 23:10:33.978 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening log file. Feb 06 23:10:33.978 [notice] Tor 0.2.4.20 (git-3cb5c70beec5bf46) opening log file. Feb 06 23:10:34.293 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 023220505A550D6FDF0C20FF7C48E66BA06A49A6' Feb 06 23:10:34.293 [notice] Your Tor server's identity key fingerprint is 'MYCROFTsOtherChild 023220505A550D6FDF0C20FF7C48E66BA06A49A6' Feb 06 23:31:59.200 [notice] Circuit handshake stats since last time: 2129/2129 TAP, 364/364 NTor. Feb 06 23:31:59.200 [notice] Circuit handshake stats since last time: 2129/2129 TAP, 364/364 NTor. Feb 06 23:32:01.222 [notice] Heartbeat: Tor's uptime is 10 days 4:00 hours, with 296 circuits open. I've sent 8.55 GB and received 8.05 GB. Feb 06 23:32:01.222 [notice] Heartbeat: Tor's uptime is 10 days 4:00 hours, with 296 circuits open. I've sent 8.55 GB and received 8.05 GB. Feb 06 23:32:01.222 [notice] Average packaged cell fullness: 77.276% Feb 06 23:32:01.222 [notice] Average packaged cell fullness: 77.276% Feb 06 23:32:01.222 [notice] TLS write overhead: 11% Feb 06 23:32:01.222 [notice] TLS write overhead: 11% Feb 07 00:31:59.201 [notice] Circuit handshake stats since last time: 2781/2781 TAP, 348/348 NTor. Feb 07 00:31:59.201 [notice] Circuit handshake stats since last time: 2781/2781 TAP, 348/348 NTor. Feb 07 00:32:01.201 [notice] Heartbeat: Tor's uptime is 10 days 5:00 hours, with 384 circuits open. I've sent 8.62 GB and received 8.11 GB. Feb 07 00:32:01.201 [notice] Heartbeat: Tor's uptime is 10 days 5:00 hours, with 384 circuits open. I've sent 8.62 GB and received 8.11 GB. Feb 07 00:32:01.201 [notice] Average packaged cell fullness: 77.264% Feb 07 00:32:01.201 [notice] Average packaged cell fullness: 77.264% Feb 07 00:32:01.201 [notice] TLS write overhead: 11% Feb 07 00:32:01.201 [notice] TLS write overhead: 11% Feb 07 01:31:59.219 [notice] Circuit handshake stats since last time: 3469/3469 TAP, 278/278 NTor. Feb 07 01:31:59.219 [notice] Circuit handshake stats since last time: 3469/3469 TAP, 278/278 NTor. Feb 07 01:32:01.202 [notice] Heartbeat: Tor's uptime is 10 days 6:00 hours, with 559 circuits open. I've sent 8.63 GB and received 8.13 GB. Feb 07 01:32:01.202 [notice] Heartbeat: Tor's uptime is 10 days 6:00 hours, with 559 circuits open. I've sent 8.63 GB and received 8.13 GB. Feb 07 01:32:01.202 [notice] Average packaged cell fullness: 77.151% Feb 07 01:32:01.202 [notice] Average packaged cell fullness: 77.151% Feb 07 01:32:01.202 [notice] TLS write overhead: 11% Feb 07 01:32:01.202 [notice] TLS write overhead: 11% Feb 07 02:31:59.200 [notice] Circuit handshake stats since last time: 4090/4090 TAP, 345/345 NTor. Feb 07 02:31:59.200 [notice] Circuit handshake stats since last time: 4090/4090 TAP, 345/345 NTor. Feb 07 02:32:01.201 [notice] Heartbeat: Tor's uptime is 10 days 7:00 hours, with 540 circuits open. I've sent 8.82 GB and received 8.31 GB. Feb 07 02:32:01.201 [notice] Heartbeat: Tor's uptime is 10 days 7:00 hours, with 540 circuits open. I've sent 8.82 GB and received 8.31 GB. Feb 07 02:32:01.201 [notice] Average packaged cell fullness: 77.116% Feb 07 02:32:01.201 [notice] Average packaged cell fullness: 77.116% Feb 07 02:32:01.201 [notice] TLS write overhead: 11% Feb 07 02:32:01.201 [notice] TLS write overhead: 11% And so on. Is the duplication of messages after a reload a known bug? Please note that the double logging I reported earlier has been corrected by commenting out the --Log stuff in /usr/local/etc/rc.d/tor, so the new double logging appears to be a different problem. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *or* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

1 1

What is more necessary: Bridge or Relay?
by an.to_n-73＠riseup.net 05 Feb '14

05 Feb '14

Hello List! Since 7/2013 I operate a small Tor Server as internal relay or as obfuscated bridge. What is more necessary: An internal relay to speed up the network, or an obfuscated bridge to help censored users? My ISP gives me dynamic IPs, which change daily. I guess this is good for bridges, because my IP is valid only for one day. Otherwise I've got an upload > 500 kbps and could contribute to the network speed. Actually I've got not clue about the need for anonymous bridges. In addition: I could combine both, because my VPN provider iVPN offers port forwarding. So I could run the RaspberryPi as bridge on my own IP and the 2nd server as internal relay over the VPN. So the public relay runs on another IP. But actually the VPN connection terminates by itself, the relay goes offline and I can fix it the evening. => Has anyone experience with servers listening over VPN? Does anyone know more? Best regards Anton -- an.to_n-73(a)riseup.net Public PGP key fingerprint 5FD2 DE00 1B1A 1970 8D32 A59E 4A25 3CE1 A82F F4C4

2 1

http://torstatus.blutmagie.de/
by K. Besig 05 Feb '14

05 Feb '14

Why shouldn't I be concerned when, by simply accessing this page, all my actual ip/dns information is readily available to all?

4 4

Middle relay
by Tora Tora Tora 05 Feb '14

05 Feb '14

I am trying to run a middle relay with no-exit policy. It was my assumption that a middle relay would only communicate with other relays on 9001 port. Yet I see my relay IP address attempting connections to other IP address on ports that are non-9001 (or 9030).

3 5