tor-relays June 2014

tor-relays@lists.torproject.org

89 participants
50 discussions

Trying Trusted Tor Traceroutes
by Sebastian Urbach 06 Jul '14

06 Jul '14

Dear list members, Just a quick update regarding the TTTT project. There are multiple GB's of data to analyse and it is still being worked on. We are also working on the public script(s) as well. Thanks for your ongoing support ! -- 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

2 1

Obfs + Non-obfs bridges
by Daniel Thill 03 Jul '14

03 Jul '14

Can a single tor daemon instance provide both non-obfuscated and various other obfuscated transports? Right now, I have one instance that provides both obfs3 and scramblesuit. E.g., ServerTransportPlugin obfs3,scramblesuit exec /usr/local/bin/obfsproxy managed ServerTransportListenAddr obfs3 MYIP:PORT ServerTransportListenAddr scramblesuit MYIP:PORT2 I currently have another tor instance that runs a vanilla bridge configuration (no transports) on a different port. Is this really necessary? I couldn't find any documentation that address this. Can non-transport clients use any bridge by simply not negotiating a transport? There is a "none" pluggable transport type, but I figured that was for debugging purposes. Thanks, Dan

2 1

Why is UFW bllocking allowed TOR traffic?
by Jeff Odell 02 Jul '14

02 Jul '14

I was monitoring UFW today and noticed that it was periodically blocking allowed TOR traffic. any ideas why from those with more experience than I? toradmin@IrvineTorExit:~$ sudo ufw status Status: active To Action From -- ------ ---- 22 ALLOW Anywhere 9001/tcp ALLOW Anywhere 9030/tcp ALLOW Anywhere 80 ALLOW Anywhere 22 (v6) ALLOW Anywhere (v6) 9001/tcp (v6) ALLOW Anywhere (v6) 9030/tcp (v6) ALLOW Anywhere (v6) 80 (v6) ALLOW Anywhere (v6) toradmin@IrvineTorExit:~$ sudo tail -f /var/log/syslog | grep DPT=9001 Jun 22 15:38:12 IrvineTorExit kernel: [ 2159.246977] [UFW BLOCK] IN=eth0 OUT= MAC=04:01:1b:5e:9a:01:28:8a:1c:64:cf:f0:08:00 SRC=92.108.200.200 DST=188.226.199.250 LEN=52 TOS=0x00 PREC=0x00 TTL=120 ID=10392 DF PROTO=TCP SPT=52000 DPT=9001 WINDOW=16652 RES=0x00 ACK URGP=0 Jun 22 15:38:12 IrvineTorExit kernel: [ 2159.246988] [UFW BLOCK] IN=eth0 OUT= MAC=04:01:1b:5e:9a:01:28:8a:1c:64:cf:f0:08:00 SRC=92.108.200.200 DST=188.226.199.250 LEN=52 TOS=0x00 PREC=0x00 TTL=120 ID=10396 DF PROTO=TCP SPT=52000 DPT=9001 WINDOW=16652 RES=0x00 ACK URGP=0 Regards, Jeff

3 2

Hits against GFC hex-string fingerprint in IPTables yesterday
by tor＠t-3.net 30 Jun '14

30 Jun '14

Wanted to point out to the list that we got 3 hits to our "Libero2" relay on port 9001 from chinese IP address 210.72.9.44 to a "GFC" reject line in the relay's iptables. I think this is the first time we've seen hits to this type of rule. The packets were dropped via this iptables detection: -A INPUT -p tcp -m string --hex-string "|00002800390038008800870035008400160013000a00330032009a009900450044002f00960041000500ff020100000400230000|" --algo kmp The packets came through at approximately these times EST: Jun 29 15:36:10 Jun 29 15:36:38 Jun 29 15:37:15

1 0

One IPv4 address, 1Gbit connection
by Tom van der Woerdt 30 Jun '14

30 Jun '14

Hi, I'm running a Tor exit node on a 1gbit connection. Currently it's maxing at about 180Mbit/s (both ways, so 360Mbit/s) per instance, and I'm running two instances. That's not really using the connection well. The box has 4 cores (no AES-NI) and I'm looking for ways to utilize the other 640Mbit/s. Sadly it's not possible to get more IPv4 addresses on this box. I do however have access to a big range of IPv6 addresses. Can I somehow run more Tor instances on this box by utilizing those IPv6 addresses? Or are there other ways to optimize the throughput and get closer to that 1Gbit? Tom

2 1

Spam
by kingqueen 29 Jun '14

29 Jun '14

hi, well having run a relay for just under 2 weeks, I've got my first spam on this email address. As you will no doubt have guessed, this is not my usual email address, it is only used for the Tor relay contact details, this email list and a very few other projects that will not have published my email address anywhere. So I guess that this spam is as a result of my email address appearing on Atlas or Globe or similar as a result of it being the contact address for my Tor relay. I know this possibility is mentioned in the Tor documentation; I read it somewhere. I guess there's not much to be done about it; I wouldn't want to remove contact details - the address is already in the public domain anyway, and I want to be contactable with any problems. I guess I just have to use the standard spam filtering and combating measures. Could those with experience of running a relay for longer, please advise if this will become a major problem? Will spam increase substantially? Also, any suggestions very gratefully received. Thank you! KQ --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

8 13

Circuit purposes
by Joel Cretan 29 Jun '14

29 Jun '14

I'm running a relay that I do not intend to use for anything else, so I set SocksPort to 0. I usually have two or three circuits established anyway, though, so I guess I haven't managed to disable creating those. I'm not sure what they are for. They are always labeled "Purpose: Ags=is_internal,need_capacity,". Several of them seem to get created around the same time, stay open for a while, and then get closed around the same time. I see some other circuit purposes documented here: https://stem.torproject.org/api/control.html But that documentation indicates that "Tor may provide purposes not in this enum", which is the case here. What are these circuits for, and do I need them? Here's my torrc: http://pastebin.com/fuQv8B2m Here's my ifconfig output: http://pastebin.com/mxMkhbMj I'm running tor 0.2.4.22 compiled from source (did not specify any options on make) on raspbian wheezy June 2014 with kernel version 3.12.20+. Thanks, Joel

2 3

Directory Server and bandwidth accounting
by Kali Tor 28 Jun '14

28 Jun '14

Hi, Is my understanding correct that if I set AccountingMax, the relay will never be used as a DR? It kind of feels odd because in my situation I can donate 500GB (and maybe even more) but I do want to keep a max limit and at the same time let the relay be a DR as well. Any way to achieve this? -kali-

4 5

BBC iPlayer blocked for UK middle relay operators?
by Chris Whittleston 28 Jun '14

28 Jun '14

Is anyone else running a relay in the UK having issues accessing BBC iPlayer from the same connection? For the last 6 weeks or so now I've been getting messages telling me I'm 'outside the UK' when I'm in London, and my IP address clearly resolves to show that. Just wondering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris

3 6

Bridge still advertising removed pluggable transport?
by Rick Huebner 28 Jun '14

28 Jun '14

Hi. I removed the recently-deprecated obfs2 transport from my (0.2.4.22) bridge's torrc, but after restarting, it seems to still be advertising support for it. It correctly doesn't appear as a "Registered server transport obfs2" line in the tor log file, and it's not listed in the TOR_PT_SERVER_TRANSPORTS or TOR_PT_SERVER_BINDADDR env vars fed to obfsproxy, nor is obfsproxy listening at the port that was formerly used for obfs2 any more. But... it's still listed in a "TransportProxy obfs2" line in the tor state file after several hours, and is still showing up as a supported transport in my bridge's details page on globe.torproject.org. It seems like that would mean it's still being handed out as a working bridge by BridgeDB for those requesting obfs2 bridges, though that port and transport will never be up again. And it might trigger mistaken "bridge is down" or "destination is censored" signals from those attempting to monitor such things. Is there something else I need to do besides dropping obfs2 from the torrc ServerTransportPlugin line, or is this just a bug? If so, it'll be showing up a lot more as obfs2 is phased out. Thanks.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays June 2014