- tor-relays - lists.torproject.org

Relay overload
by cmeclax 11 Apr '13

11 Apr '13

I noticed when sshing to my relay box that it is responding much slower than normal - taking a minute or two to respond to a single keypress. I ran netstat -t and saw lots of bytes in the outqueue to various other relays. I telnetted to port 9051 and got the following bandwidth log: 650 BW 63449 10568 650 BW 62510 21671 650 BW 63433 22438 650 BW 40314 19035 650 BW 94448 61126 650 BW 10408 11154 650 BW 123157 58027 650 BW 62837 31070 650 BW 12002 3536 650 BW 159449 65423 650 BW 64487 23865 650 BW 65471 35381 650 BW 68892 21466 650 BW 65378 46215 650 BW 38807 11434 650 BW 90042 43329 650 BW 65909 44768 650 BW 77162 18627 650 BW 107393 56922 650 BW 67305 36924 650 BW 25255 11149 650 BW 79619 37266 650 BW 123230 25956 650 BW 67194 27742 650 BW 70871 49787 650 BW 62114 50882 650 BW 53981 60433 650 BW 42699 21631 650 BW 161246 77324 650 BW 66421 39994 650 BW 68306 51876 650 BW 37977 21411 650 BW 157806 71560 650 BW 67964 35298 650 BW 64643 38299 650 BW 41193 26601 650 BW 156710 106887 650 BW 18786 14135 650 BW 158192 48526 650 BW 62862 39633 650 BW 67273 38448 650 BW 57955 39696 650 BW 34695 28979 650 BW 156069 81872 650 BW 53572 28598 650 BW 159163 43722 650 BW 65412 41567 650 BW 67271 48134 650 BW 65372 46107 650 BW 36323 14414 650 BW 0 0 650 BW 158006 92438 650 BW 64455 56813 650 BW 53169 11364 650 BW 109892 82106 650 BW 65191 34845 650 BW 12916 10803 650 BW 76387 21984 650 BW 0 0 650 BW 91819 54140 650 BW 63323 43265 650 BW 66760 26847 650 BW 12030 5817 650 BW 62995 16102 650 BW 154965 70999 650 BW 68408 38650 650 BW 87724 30290 650 BW 44543 45024 650 BW 60544 35343 650 BW 103227 35954 650 BW 155268 53094 650 BW 64928 37615 650 BW 66599 33239 650 BW 111463 36394 650 BW 76657 67405 650 BW 65448 40502 650 BW 65778 49605 650 BW 23300 7620 650 BW 155335 70596 650 BW 65994 31356 650 BW 66109 27590 650 BW 158464 72332 650 BW 60705 36345 650 BW 102858 25936 650 BW 161401 24083 650 BW 86788 62280 650 BW 66162 54081 My throughput limit is 64K, which has not previously been a problem. I've sometimes seen steady throughput close to 64K; more often it's sporadic with an average around 5K. Any idea what's going on? I checked Blutmagie; I've lost the fast flag, but have not been selected as guard or any other new flag. I thought it might have something to do with the bitcoin crash that's going on, but netstat -t on the bitcoin box doesn't show any similar attempt to push more data than the line can handle. If I were selected as the middleman in one user's file upload, I'd see a steady stream of traffic, not this spikiness. cmeclax

1 0

Re: [tor-relays] How to limit number of sockets used?
by Roman Mamedov 10 Apr '13

10 Apr '13

On Wed, 10 Apr 2013 07:51:57 -0400 Steve Snyder <swsnyder(a)snydernet.net> wrote: > Yes, I have hit the limit, with the expected "Error creating network > socket: No buffer space available" messages seen. Afaik this is a different error, and it comes from the RAM limit for network buffers, not due to hitting the maximum quantity of open sockets. ConstrainedSockets/ConstrainedSockSize may actually help you here. Also next time you hit this error, check "lsof -n | grep tor | wc -l". My guess is it will be much lower than 4096. -- With respect, Roman

1 0

How to limit number of sockets used?
by Steve Snyder 10 Apr '13

10 Apr '13

I am running Tor v0.2.3.25 in a VPS that limits me to a max of 4096 sockets in use. How can I instruct Tor not to attempt to use more than this number? Yes, I know about ConstrainedSockets/ConstrainedSockSize, but the way I read these it limits the amount of memory used, not the socket count. Advice, please? Thanks.

5 5

Can you double check my exit policy for usefulness while minimizing complaints
by Nate Homier 09 Apr '13

09 Apr '13

I was wondering if I have a good compromise between not allowing BitTorrent and allowing enough ports to be useful. Here's mine. ExitPolicy accept *:119 # accept nntp as well as default exit policy ExitPolicy accept *:22 # ssh ExitPolicy accept *:80 # www ExitPolicy accept *:443 # www secure ExitPolicy accept *:110 # pop3 ExitPolicy accept *:143 # imap ExitPolicy accept *:995 # pop3 secure ExitPolicy accept *:6660-6669 # irc ExitPolicy accept *:6697 # irc ssl ExitPolicy accept *:7000-7001 # irc ssl ExitPolicy accept *:706 # silc ExitPolicy accept *:1863 # msn ExitPolicy accept *:5050 # yahoo messenger ExitPolicy accept *:5190 # various im programs ExitPolicy accept *:5222 # various im programs ExitPolicy accept *:5223 # various im programs ExitPolicy accept *:8300 # im ExitPolicy accept *:8888 # www ExitPolicy accept *:465 # smtps (SMTP over SSL) ExitPolicy accept *:993 # imaps (IMAP over SSL) ExitPolicy accept *:994 # ircs (IRC over SSL) ExitPolicy reject *:* # no exits allowed How does this compare with this policy located here: https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy Should I use the official Tor reduced policy or is mine good enough to be useful while minimizing complaints. Nate

2 2

tor cpu usage
by Martin Weinelt 09 Apr '13

09 Apr '13

Hey, I'm running a tor relay with version 0.2.4.11-alpha and there seems to be an issue about cpu usage. Usually when the bandwidth peaks (at about 10 MBit/s) the cpu is at about 25-35% load, however after a few days it gets stuck at 100%. The notices-logfile, to my knowledge, does not indicate any weirdness. I'm attaching the "[warn]" section though: Apr 04 18:19:16.000 [warn] crypto error while checking RSA signature: block type is not 01 (in rsa routines:RSA_padding_check_PKCS1_type_1) Apr 04 18:19:16.000 [warn] crypto error while checking RSA signature: padding check failed (in rsa routines:RSA_EAY_PUBLIC_DECRYPT) Apr 06 20:38:18.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. Apr 06 21:01:05.000 [warn] Tried to establish rendezvous on non-OR or non-edge circuit. Apr 07 04:35:49.000 [warn] eventdns: Unable to add nameserver 2001:4860:4860::8888: error 2 Apr 07 04:35:49.000 [warn] eventdns: Unable to add nameserver 2001:4860:4860::8844: error 2 Unfortunately I don't do any statistics so I can't relate a specific event with the spiking cpu load. Does anybody else experience this? What could cause this? How can I fix it? Martin

1 0

How Can I Do This?
by Barack Obama 08 Apr '13

08 Apr '13

My website, Bypass-Censorship.org, is getting LOTS of spam traffic from Tor (specifically in the wp-cron.php script). I obviously don't want to block Tor as it's extremely beneficial for privacy geeks and people from Iran, China, etc, to access my site; however, I do have an alternative solution that I may need help with. Basically what I want to do is add some PHP code in the beginning of index.php (I use WordPress as my CMS). What the code should do is detect if the client is using Tor, and if the client is, the script redirects to the mobile version of my site (mobile.dudamobile.com/site/bypass-censorship - it is hosted for free on DudaMobile). I believe this would be beneficial for two reasons: 1. Spam attacks and hack attacks are useless since it is not on my primary host (meaning there is no wp-cron.php). 2. And it will take a huge load off my server (I am well-ranked for the term "hidden wiki" in Google and Ixquick). Please tell me what you think of this idea, and how I can implement it. Thanks, -BC

4 3

Advice on configuring Obfsproxy3 transport?
by Steve Snyder 06 Apr '13

06 Apr '13

Attempting to get Obfsproxy3 to work. With Tor v0.2.4.11-alpha and Obfsproxy pulled from https://git.torproject.org/obfsproxy.git yesterday this is what I get at runtime: Apr 05 14:57:23.000 [warn] Server managed proxy encountered a method error. (obfs3 could not setup protocol) Apr 05 14:57:23.000 [warn] Managed proxy at '/usr/bin/obfsproxy' failed the configuration protocol and will be destroyed I have no problems with obfs2, but obfs3 success continues to elude me. These are the relevant lines from my bridge config: ServerTransportListenAddr obfs3 aaa.bb.cc.dd:12647 ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy --managed Any advice on how to get Obfsproxy to work would be greatly appreciated. Thanks.

2 1

Obfsproxy doesn't use specified addresses?
by Steve Snyder 05 Apr '13

05 Apr '13

I've got a server with 2 IP addresses, and a bridge running on each address. I followed the instructions for using Obfsproxy, adding this line to each Tor config file: ServerTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed It seems that Obfsproxy is not running on a per-address basis but instead each instance is bound to all addresses. (See below). Is this really how it is supposed to work? Shouldn't each instance of Obfsproxy be bound to a specific IP address? ----------------- # lsof -ni | grep _tor tor TCP aaa.aa.aa.aa:https (LISTEN) tor TCP aaa.aa.aa.aa:57242->000.00.000.000:https (ESTABLISHED) tor TCP aaa.aa.aa.aa:48851->111.111.111.11:torrouting (ESTABLISHED) tor TCP aaa.aa.aa.aa:34865->222.22.222.222:torrouting (ESTABLISHED) tor TCP bbb.bb.bb.bb:https (LISTEN) tor TCP bbb.bb.bb.bb:42826->333.33.333.33:https (ESTABLISHED) tor TCP bbb.bb.bb.bb:https->444.4.444.444:58519 (ESTABLISHED) tor TCP bbb.bb.bb.bb:33745->55.55.555.55:https (ESTABLISHED) tor TCP bbb.bb.bb.bb:44772->666.666.666.666:https (ESTABLISHED) obfsproxy TCP *:34866 (LISTEN) obfsproxy TCP *:41887 (LISTEN)

1 0

Re: [tor-relays] Too-regular traffic
by eliaz＠riseup.net 01 Apr '13

01 Apr '13

Never mind - I noticed the bookkeeping during a period when my bridge was carrying very low traffic. On 03.29.2013 eliaz wrote: > My bridge relay often shows regular pulses in its bandwidth graph, as > per the attached. Do these represent some housekeeping on the > network? [attachment scrubbed]

1 0

ask
by syrus f 30 Mar '13

30 Mar '13

Hello My tor can not connect to internet in these last week. I am in Iran. and have been change my relay addresses but problem not solve what i must to do?

4 3

Re: [tor-relays] ongoing denial of service attack against Road Runner IP addresses
by Kent Backman 29 Mar '13

29 Mar '13

Quoting Rebecca Kaiser <abuse(a)wholesaleinternet.net>: Thanks, Rebecca I see no further malicious activity from DataShack and Wholesale Internet. Still ongoing attack from Limestone and Ubiquity/Nobistech and a few other US ISP's, and of course malicious traffic from IP addresses from one specific foreign country. Any explanation from your foreign customers as to why they are engaging in what appears to be illegal activity, at least as far as US laws apply? - Kent > We've received confirmation from our client that this has been shut down. > > > > From: Kent Backman [mailto:kent@kentbackman.com] > Sent: Tuesday, March 26, 2013 8:08 PM > To: abuse(a)rr.com > Cc: abuse(a)nobistech.net; security(a)datashack.net; noc(a)psychz.net; > abuse(a)limestonenetworks.com; abuse(a)wholesaleinternet.net; abuse(a)he.net > Subject: ongoing denial of service attack against Road Runner IP address > 98.150.237.177 by botnet operating out of Nobistech, Datashack, Limestone, > HE, Pegtech, WholeSale Interent, and Psychz VPS nodes > Importance: High > >

2 2

Re: [tor-relays] Ongoing denial of service attack against Tor relays by leased botnet in America and PRC (Nobistech, Datashack, Limestone, HE, Pegtech, WholeSale Internet, and Psychz VPS nodes, etc)
by Kent Backman 29 Mar '13

29 Mar '13

The list has been very helpful, and helped me gather more information. Appreciate all the responses. The botnet is certainly there, but the targets seem to be much more constrained than I first thought. It *is* just me. Only nodes that someone could associate with me are being targeted. An exit node I setup last night with a nearly default torrc file on a different ISP was clean. While unfortunately this is not better news for me, it is explainable considering what I have exposed in the past, but a false alarm for the rest of you. Thanks -----Original Message----- From: Kent Backman [mailto:kent@kentbackman.com] Sent: Thursday, March 28, 2013 12:14 AM To: 'tor-relays(a)lists.torproject.org' Subject: Ongoing denial of service attack against Tor relays by leased botnet in America and PRC (Nobistech, Datashack, Limestone, HE, Pegtech, WholeSale Interent, and Psychz VPS nodes, etc) Up front, I am not a conspiracy theorist. New to the list, I run a Tor exit node from my small cable modem connection in Honolulu, as well as for a short time on a few on VPS's to prove to myself that it wasn't "just me." Over the last several weeks, I have collected substantial evidence indicating that a botnet is degrading the Tor anonymity network in its entirety via a sustained denial of service attack. I believe it is made to blend in with all the other crazy packets that an exit node generates, but it is pretty easy to spot if you just look at the RST's or drops coming off your node, all from a static unused destination port. If you change the IP address of your node, it will take about 90 minutes before they identify your IP and you start getting attacked again. I will submit to you the headers of a few hundred packets, and the full list of perps involved in separate emails because of the size thing. Do a whois lookup on a few of those VPS IP addresses and you will see the country involved. Here are the last few hundred packet headers showing the two bigger ISP's. Wasn't able to show perp list since first two messages held for the moderator because of the size. Wondering what other folks are seeing with their relays. UTC DATE UTC TIME IP SRC-ISP SPT DST DST-ISP DPT Flags 2013-03-28 7:33:38 173.208.95.126 Nobis Technology Group, LLC 2571 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 173.208.95.126 Nobis Technology Group, LLC 2571 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 74.63.192.36 Limestone Networks 1274 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 108.177.168.156 Nobis Technology Group, LLC 3471 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 173.208.95.126 Nobis Technology Group, LLC 2571 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 23.19.67.28 Nobis Technology Group, LLC 3866 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 74.63.192.36 Limestone Networks 1274 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 108.177.168.156 Nobis Technology Group, LLC 3471 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 74.63.192.36 Limestone Networks 1598 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 23.19.67.28 Nobis Technology Group, LLC 3866 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 108.177.168.156 Nobis Technology Group, LLC 3471 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 74.63.192.36 Limestone Networks 1274 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:41 74.63.192.36 Limestone Networks 1598 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:41 23.19.67.28 Nobis Technology Group, LLC 3866 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:41 74.63.192.36 Limestone Networks 1598 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:44 173.208.44.42 Nobis Technology Group, LLC 1358 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 173.208.44.42 Nobis Technology Group, LLC 1358 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 64.120.60.121 Nobis Technology Group, LLC 4001 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 69.147.233.52 Nobis Technology Group, LLC 2291 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 173.208.44.42 Nobis Technology Group, LLC 1358 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 64.120.60.121 Nobis Technology Group, LLC 4001 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:46 69.147.233.52 Nobis Technology Group, LLC 2291 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:46 64.120.60.121 Nobis Technology Group, LLC 4001 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:46 69.147.233.52 Nobis Technology Group, LLC 2291 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:47 64.120.60.139 Nobis Technology Group, LLC 2078 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:47 23.19.54.243 Nobis Technology Group, LLC 1281 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 64.120.60.139 Nobis Technology Group, LLC 2078 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 23.19.54.243 Nobis Technology Group, LLC 1281 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 64.120.60.139 Nobis Technology Group, LLC 2078 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 23.19.54.243 Nobis Technology Group, LLC 1281 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 64.120.60.106 Nobis Technology Group, LLC 3004 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:49 64.120.60.106 Nobis Technology Group, LLC 3004 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:49 64.120.60.106 Nobis Technology Group, LLC 3004 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:50 69.162.117.205 Limestone Networks 1273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:50 23.19.63.204 Nobis Technology Group, LLC 2769 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:50 69.162.117.205 Limestone Networks 1273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.63.204 Nobis Technology Group, LLC 2769 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.54.57 Nobis Technology Group, LLC 2633 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 69.162.117.205 Limestone Networks 1273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.63.204 Nobis Technology Group, LLC 2769 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.54.57 Nobis Technology Group, LLC 2633 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:52 23.19.54.57 Nobis Technology Group, LLC 2633 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:53 173.208.95.106 Nobis Technology Group, LLC 2337 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:53 108.62.33.54 Nobis Technology Group, LLC 1322 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 23.19.130.121 Nobis Technology Group, LLC 2389 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 108.62.33.54 Nobis Technology Group, LLC 1322 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 173.208.95.106 Nobis Technology Group, LLC 2337 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 23.19.130.121 Nobis Technology Group, LLC 2389 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 108.62.33.54 Nobis Technology Group, LLC 1322 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 173.234.116.251 Nobis Technology Group, LLC 2873 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 173.208.95.106 Nobis Technology Group, LLC 2337 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:55 23.19.130.121 Nobis Technology Group, LLC 2389 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:55 173.234.116.251 Nobis Technology Group, LLC 2873 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 173.234.116.251 Nobis Technology Group, LLC 2873 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 173.234.145.205 Nobis Technology Group, LLC 2549 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 23.19.131.10 Nobis Technology Group, LLC 2273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 69.147.233.52 Nobis Technology Group, LLC 4112 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 173.234.145.205 Nobis Technology Group, LLC 2549 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 69.147.233.52 Nobis Technology Group, LLC 4112 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 23.19.131.10 Nobis Technology Group, LLC 2273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 23.19.63.204 Nobis Technology Group, LLC 4430 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 173.234.145.205 Nobis Technology Group, LLC 2549 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 23.19.131.10 Nobis Technology Group, LLC 2273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 69.147.233.52 Nobis Technology Group, LLC 4112 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 23.19.63.204 Nobis Technology Group, LLC 4430 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 23.19.63.204 Nobis Technology Group, LLC 4430 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:59 173.208.57.54 Nobis Technology Group, LLC 3250 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:59 173.208.57.54 Nobis Technology Group, LLC 3250 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:00 23.19.130.91 Nobis Technology Group, LLC 2751 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:00 173.208.57.54 Nobis Technology Group, LLC 3250 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:00 23.19.130.91 Nobis Technology Group, LLC 2751 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:01 23.19.131.11 Nobis Technology Group, LLC 1828 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:01 23.19.130.91 Nobis Technology Group, LLC 2751 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:01 23.19.131.11 Nobis Technology Group, LLC 1828 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:02 23.19.131.11 Nobis Technology Group, LLC 1828 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:02 23.19.67.28 Nobis Technology Group, LLC 4607 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:03 23.19.67.28 Nobis Technology Group, LLC 4607 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:03 23.19.130.92 Nobis Technology Group, LLC 1398 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 23.19.67.28 Nobis Technology Group, LLC 4607 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 23.19.130.92 Nobis Technology Group, LLC 1398 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 70.32.43.188 Nobis Technology Group, LLC 3669 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 23.19.130.92 Nobis Technology Group, LLC 1398 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:05 70.32.43.188 Nobis Technology Group, LLC 3669 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:05 64.120.60.122 Nobis Technology Group, LLC 4518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:05 70.32.43.188 Nobis Technology Group, LLC 3669 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 173.234.188.204 Nobis Technology Group, LLC 2505 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 64.120.60.122 Nobis Technology Group, LLC 4518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 173.208.16.248 Nobis Technology Group, LLC 3296 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 173.234.188.204 Nobis Technology Group, LLC 2505 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 23.19.131.10 Nobis Technology Group, LLC 4396 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.67.28 Nobis Technology Group, LLC 1378 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 173.208.16.248 Nobis Technology Group, LLC 3296 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 64.120.60.122 Nobis Technology Group, LLC 4518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 173.234.188.204 Nobis Technology Group, LLC 2505 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.131.10 Nobis Technology Group, LLC 4396 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 173.208.16.248 Nobis Technology Group, LLC 3296 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.67.28 Nobis Technology Group, LLC 1378 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.131.10 Nobis Technology Group, LLC 4396 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:08 23.19.67.28 Nobis Technology Group, LLC 1378 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:09 147.255.224.134 Nobis Technology Group, LLC 2361 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:09 147.255.224.134 Nobis Technology Group, LLC 2361 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 64.120.60.106 Nobis Technology Group, LLC 1518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 70.32.43.190 Nobis Technology Group, LLC 2963 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 147.255.224.134 Nobis Technology Group, LLC 2361 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 64.120.60.106 Nobis Technology Group, LLC 1518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 70.32.43.190 Nobis Technology Group, LLC 2963 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 64.120.60.106 Nobis Technology Group, LLC 1518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 173.234.145.205 Nobis Technology Group, LLC 3493 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 70.32.43.190 Nobis Technology Group, LLC 2963 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 173.234.145.206 Nobis Technology Group, LLC 2492 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 173.234.145.205 Nobis Technology Group, LLC 3493 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 173.234.145.206 Nobis Technology Group, LLC 2492 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 173.234.145.205 Nobis Technology Group, LLC 3493 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 23.19.50.46 Nobis Technology Group, LLC 2827 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 173.234.145.206 Nobis Technology Group, LLC 2492 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:13 23.19.50.46 Nobis Technology Group, LLC 2827 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:13 23.19.50.46 Nobis Technology Group, LLC 2827 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:13 64.120.60.105 Nobis Technology Group, LLC 1194 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:14 64.120.60.105 Nobis Technology Group, LLC 1194 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:14 64.120.60.105 Nobis Technology Group, LLC 1194 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:15 173.234.116.237 Nobis Technology Group, LLC 4363 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:16 173.234.116.237 Nobis Technology Group, LLC 4363 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:16 64.120.60.174 Nobis Technology Group, LLC 2369 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 173.234.116.237 Nobis Technology Group, LLC 4363 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 64.120.60.174 Nobis Technology Group, LLC 2369 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 23.19.131.10 Nobis Technology Group, LLC 2648 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 64.120.60.174 Nobis Technology Group, LLC 2369 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 23.19.131.10 Nobis Technology Group, LLC 2648 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:18 23.19.131.10 Nobis Technology Group, LLC 2648 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:18 173.234.145.206 Nobis Technology Group, LLC 4154 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 23.19.130.121 Nobis Technology Group, LLC 3782 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 173.234.145.206 Nobis Technology Group, LLC 4154 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 23.19.130.121 Nobis Technology Group, LLC 3782 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 64.120.60.122 Nobis Technology Group, LLC 2141 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 173.234.145.206 Nobis Technology Group, LLC 4154 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:20 23.19.130.121 Nobis Technology Group, LLC 3782 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:20 64.120.60.122 Nobis Technology Group, LLC 2141 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 64.120.60.122 Nobis Technology Group, LLC 2141 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 173.208.95.126 Nobis Technology Group, LLC 3208 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 173.208.95.126 Nobis Technology Group, LLC 3208 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 64.120.60.174 Nobis Technology Group, LLC 3193 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 173.208.95.126 Nobis Technology Group, LLC 3208 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 64.120.60.174 Nobis Technology Group, LLC 3193 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 64.120.60.174 Nobis Technology Group, LLC 3193 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 64.120.44.150 Nobis Technology Group, LLC 3211 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 64.120.44.150 Nobis Technology Group, LLC 3211 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 108.62.33.51 Nobis Technology Group, LLC 3383 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 108.62.33.51 Nobis Technology Group, LLC 3383 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 64.120.44.150 Nobis Technology Group, LLC 3211 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:24 23.19.50.46 Nobis Technology Group, LLC 4534 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:24 108.62.33.51 Nobis Technology Group, LLC 3383 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:24 23.19.50.46 Nobis Technology Group, LLC 4534 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.130.86 Nobis Technology Group, LLC 3654 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.50.46 Nobis Technology Group, LLC 4534 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.130.86 Nobis Technology Group, LLC 3654 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.130.93 Nobis Technology Group, LLC 2090 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 23.19.130.86 Nobis Technology Group, LLC 3654 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 23.19.130.93 Nobis Technology Group, LLC 2090 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 69.147.233.52 Nobis Technology Group, LLC 4623 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 23.19.130.93 Nobis Technology Group, LLC 2090 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 64.120.60.121 Nobis Technology Group, LLC 1486 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 69.147.233.52 Nobis Technology Group, LLC 4623 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 64.120.60.121 Nobis Technology Group, LLC 1486 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 69.162.117.206 Limestone Networks 1906 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 173.234.116.232 Nobis Technology Group, LLC 4393 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 173.208.44.46 Nobis Technology Group, LLC 2169 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 69.147.233.52 Nobis Technology Group, LLC 4623 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.208.95.125 Nobis Technology Group, LLC 1316 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 64.120.60.121 Nobis Technology Group, LLC 1486 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 69.162.117.206 Limestone Networks 1906 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.234.116.232 Nobis Technology Group, LLC 4393 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.208.44.46 Nobis Technology Group, LLC 2169 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 108.177.157.70 Nobis Technology Group, LLC 1659 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.208.95.125 Nobis Technology Group, LLC 1316 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 69.162.117.206 Limestone Networks 1906 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.234.116.232 Nobis Technology Group, LLC 4393 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.95.106 Nobis Technology Group, LLC 1650 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 108.177.157.70 Nobis Technology Group, LLC 1659 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.95.125 Nobis Technology Group, LLC 1316 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.44.46 Nobis Technology Group, LLC 2169 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.131.10 Nobis Technology Group, LLC 1104 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.131.10 Nobis Technology Group, LLC 1132 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 108.177.157.70 Nobis Technology Group, LLC 1659 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.95.106 Nobis Technology Group, LLC 1650 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.131.10 Nobis Technology Group, LLC 1104 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.67.211 Nobis Technology Group, LLC 1884 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.131.10 Nobis Technology Group, LLC 1132 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.67.214 Nobis Technology Group, LLC 1295 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 173.208.95.106 Nobis Technology Group, LLC 1650 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.131.10 Nobis Technology Group, LLC 1104 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.131.10 Nobis Technology Group, LLC 1132 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.67.211 Nobis Technology Group, LLC 1884 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.67.214 Nobis Technology Group, LLC 1295 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 64.120.60.118 Nobis Technology Group, LLC 2075 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 23.19.67.211 Nobis Technology Group, LLC 1884 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 23.19.67.214 Nobis Technology Group, LLC 1295 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 64.120.60.120 Nobis Technology Group, LLC 4950 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 69.162.119.4 Limestone Networks 2862 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 64.120.60.118 Nobis Technology Group, LLC 2075 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 64.120.60.120 Nobis Technology Group, LLC 4950 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 69.162.119.4 Limestone Networks 2862 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 64.120.60.118 Nobis Technology Group, LLC 2075 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 147.255.224.134 Nobis Technology Group, LLC 1603 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 64.120.60.120 Nobis Technology Group, LLC 4950 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 69.162.119.4 Limestone Networks 2862 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 147.255.224.134 Nobis Technology Group, LLC 1603 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 173.208.44.36 Nobis Technology Group, LLC 3290 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 147.255.224.134 Nobis Technology Group, LLC 1603 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 64.120.60.118 Nobis Technology Group, LLC 2677 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 173.208.44.36 Nobis Technology Group, LLC 3290 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:34 173.208.44.36 Nobis Technology Group, LLC 3290 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:34 64.120.60.118 Nobis Technology Group, LLC 2677 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:34 173.208.16.250 Nobis Technology Group, LLC 1802 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:35 173.208.16.250 Nobis Technology Group, LLC 1802 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:35 64.120.60.118 Nobis Technology Group, LLC 2677 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:35 173.208.16.250 Nobis Technology Group, LLC 1802 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:38 108.177.168.156 Nobis Technology Group, LLC 2832 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:38 108.177.168.156 Nobis Technology Group, LLC 2832 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:38 23.19.130.93 Nobis Technology Group, LLC 4597 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 108.177.168.156 Nobis Technology Group, LLC 2832 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 23.19.130.93 Nobis Technology Group, LLC 4597 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 69.162.117.206 Limestone Networks 3681 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 23.19.130.93 Nobis Technology Group, LLC 4597 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:40 69.162.117.206 Limestone Networks 3681 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:40 69.162.117.206 Limestone Networks 3681 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:40 64.120.60.121 Nobis Technology Group, LLC 3356 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:41 64.120.60.121 Nobis Technology Group, LLC 3356 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 64.120.60.121 Nobis Technology Group, LLC 3356 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 64.120.79.221 Nobis Technology Group, LLC 1410 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 108.62.237.205 Nobis Technology Group, LLC 2969 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 64.120.79.221 Nobis Technology Group, LLC 1410 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 108.62.237.205 Nobis Technology Group, LLC 2969 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 64.120.79.221 Nobis Technology Group, LLC 1410 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 108.62.42.18 Nobis Technology Group, LLC 2158 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 23.19.130.93 Nobis Technology Group, LLC 1789 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 108.62.237.205 Nobis Technology Group, LLC 2969 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 173.208.44.40 Nobis Technology Group, LLC 1441 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 108.62.42.18 Nobis Technology Group, LLC 2158 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.234.12.178 Nobis Technology Group, LLC 2411 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.208.44.40 Nobis Technology Group, LLC 1441 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 23.19.130.93 Nobis Technology Group, LLC 1789 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 108.62.42.18 Nobis Technology Group, LLC 2158 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 23.19.130.93 Nobis Technology Group, LLC 1789 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.208.44.40 Nobis Technology Group, LLC 1441 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.234.12.178 Nobis Technology Group, LLC 2411 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:45 173.234.12.178 Nobis Technology Group, LLC 2411 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:47 64.120.79.222 Nobis Technology Group, LLC 4601 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:47 69.162.80.59 Limestone Networks 3514 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 69.162.80.59 Limestone Networks 3514 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 64.120.79.222 Nobis Technology Group, LLC 4601 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 173.234.145.205 Nobis Technology Group, LLC 4688 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 64.120.79.222 Nobis Technology Group, LLC 4601 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 69.162.80.59 Limestone Networks 3514 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 173.208.44.46 Nobis Technology Group, LLC 4835 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 173.234.145.205 Nobis Technology Group, LLC 4688 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 173.208.44.46 Nobis Technology Group, LLC 4835 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 74.63.192.36 Limestone Networks 1339 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 173.234.145.205 Nobis Technology Group, LLC 4688 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 64.120.60.146 Nobis Technology Group, LLC 3668 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 173.208.44.46 Nobis Technology Group, LLC 4835 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 74.63.192.36 Limestone Networks 1339 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 23.19.131.11 Nobis Technology Group, LLC 3868 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 64.120.60.146 Nobis Technology Group, LLC 3668 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 74.63.192.36 Limestone Networks 1339 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 70.32.43.189 Nobis Technology Group, LLC 4246 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 23.19.131.11 Nobis Technology Group, LLC 3868 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 64.120.60.146 Nobis Technology Group, LLC 3668 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:51 23.19.131.11 Nobis Technology Group, LLC 3868 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:51 70.32.43.189 Nobis Technology Group, LLC 4246 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:51 64.120.60.139 Nobis Technology Group, LLC 1105 66.8.214.196 Road Runner 8118 [S],

2 1

Ongoing denial of service attack against Tor relays by leased botnet in America and PRC (Nobistech, Datashack, Limestone, HE, Pegtech, WholeSale Interent, and Psychz VPS nodes, etc)
by Kent Backman 29 Mar '13

29 Mar '13

Up front, I am not a conspiracy theorist. New to the list, I run a Tor exit node from my small cable modem connection in Honolulu, as well as for a short time on a few on VPS's to prove to myself that it wasn't "just me." Over the last several weeks, I have collected substantial evidence indicating that a botnet is degrading the Tor anonymity network in its entirety via a sustained denial of service attack. I believe it is made to blend in with all the other crazy packets that an exit node generates, but it is pretty easy to spot if you just look at the RST's or drops coming off your node, all from a static unused destination port. If you change the IP address of your node, it will take about 90 minutes before they identify your IP and you start getting attacked again. I will submit to you the headers of a few hundred packets, and the full list of perps involved in separate emails because of the size thing. Do a whois lookup on a few of those VPS IP addresses and you will see the country involved. Here are the last few hundred packet headers showing the two bigger ISP's. Wasn't able to show perp list since first two messages held for the moderator because of the size. Wondering what other folks are seeing with their relays. UTC DATE UTC TIME IP SRC-ISP SPT DST DST-ISP DPT Flags 2013-03-28 7:33:38 173.208.95.126 Nobis Technology Group, LLC 2571 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 173.208.95.126 Nobis Technology Group, LLC 2571 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 74.63.192.36 Limestone Networks 1274 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 108.177.168.156 Nobis Technology Group, LLC 3471 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 173.208.95.126 Nobis Technology Group, LLC 2571 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:39 23.19.67.28 Nobis Technology Group, LLC 3866 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 74.63.192.36 Limestone Networks 1274 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 108.177.168.156 Nobis Technology Group, LLC 3471 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 74.63.192.36 Limestone Networks 1598 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 23.19.67.28 Nobis Technology Group, LLC 3866 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 108.177.168.156 Nobis Technology Group, LLC 3471 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:40 74.63.192.36 Limestone Networks 1274 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:41 74.63.192.36 Limestone Networks 1598 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:41 23.19.67.28 Nobis Technology Group, LLC 3866 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:41 74.63.192.36 Limestone Networks 1598 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:44 173.208.44.42 Nobis Technology Group, LLC 1358 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 173.208.44.42 Nobis Technology Group, LLC 1358 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 64.120.60.121 Nobis Technology Group, LLC 4001 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 69.147.233.52 Nobis Technology Group, LLC 2291 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 173.208.44.42 Nobis Technology Group, LLC 1358 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:45 64.120.60.121 Nobis Technology Group, LLC 4001 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:46 69.147.233.52 Nobis Technology Group, LLC 2291 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:46 64.120.60.121 Nobis Technology Group, LLC 4001 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:46 69.147.233.52 Nobis Technology Group, LLC 2291 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:47 64.120.60.139 Nobis Technology Group, LLC 2078 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:47 23.19.54.243 Nobis Technology Group, LLC 1281 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 64.120.60.139 Nobis Technology Group, LLC 2078 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 23.19.54.243 Nobis Technology Group, LLC 1281 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 64.120.60.139 Nobis Technology Group, LLC 2078 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 23.19.54.243 Nobis Technology Group, LLC 1281 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:48 64.120.60.106 Nobis Technology Group, LLC 3004 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:49 64.120.60.106 Nobis Technology Group, LLC 3004 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:49 64.120.60.106 Nobis Technology Group, LLC 3004 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:50 69.162.117.205 Limestone Networks 1273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:50 23.19.63.204 Nobis Technology Group, LLC 2769 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:50 69.162.117.205 Limestone Networks 1273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.63.204 Nobis Technology Group, LLC 2769 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.54.57 Nobis Technology Group, LLC 2633 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 69.162.117.205 Limestone Networks 1273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.63.204 Nobis Technology Group, LLC 2769 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:51 23.19.54.57 Nobis Technology Group, LLC 2633 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:52 23.19.54.57 Nobis Technology Group, LLC 2633 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:53 173.208.95.106 Nobis Technology Group, LLC 2337 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:53 108.62.33.54 Nobis Technology Group, LLC 1322 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 23.19.130.121 Nobis Technology Group, LLC 2389 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 108.62.33.54 Nobis Technology Group, LLC 1322 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 173.208.95.106 Nobis Technology Group, LLC 2337 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 23.19.130.121 Nobis Technology Group, LLC 2389 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 108.62.33.54 Nobis Technology Group, LLC 1322 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 173.234.116.251 Nobis Technology Group, LLC 2873 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:54 173.208.95.106 Nobis Technology Group, LLC 2337 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:55 23.19.130.121 Nobis Technology Group, LLC 2389 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:55 173.234.116.251 Nobis Technology Group, LLC 2873 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 173.234.116.251 Nobis Technology Group, LLC 2873 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 173.234.145.205 Nobis Technology Group, LLC 2549 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 23.19.131.10 Nobis Technology Group, LLC 2273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:56 69.147.233.52 Nobis Technology Group, LLC 4112 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 173.234.145.205 Nobis Technology Group, LLC 2549 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 69.147.233.52 Nobis Technology Group, LLC 4112 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 23.19.131.10 Nobis Technology Group, LLC 2273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 23.19.63.204 Nobis Technology Group, LLC 4430 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:57 173.234.145.205 Nobis Technology Group, LLC 2549 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 23.19.131.10 Nobis Technology Group, LLC 2273 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 69.147.233.52 Nobis Technology Group, LLC 4112 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 23.19.63.204 Nobis Technology Group, LLC 4430 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:58 23.19.63.204 Nobis Technology Group, LLC 4430 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:59 173.208.57.54 Nobis Technology Group, LLC 3250 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:33:59 173.208.57.54 Nobis Technology Group, LLC 3250 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:00 23.19.130.91 Nobis Technology Group, LLC 2751 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:00 173.208.57.54 Nobis Technology Group, LLC 3250 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:00 23.19.130.91 Nobis Technology Group, LLC 2751 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:01 23.19.131.11 Nobis Technology Group, LLC 1828 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:01 23.19.130.91 Nobis Technology Group, LLC 2751 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:01 23.19.131.11 Nobis Technology Group, LLC 1828 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:02 23.19.131.11 Nobis Technology Group, LLC 1828 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:02 23.19.67.28 Nobis Technology Group, LLC 4607 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:03 23.19.67.28 Nobis Technology Group, LLC 4607 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:03 23.19.130.92 Nobis Technology Group, LLC 1398 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 23.19.67.28 Nobis Technology Group, LLC 4607 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 23.19.130.92 Nobis Technology Group, LLC 1398 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 70.32.43.188 Nobis Technology Group, LLC 3669 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:04 23.19.130.92 Nobis Technology Group, LLC 1398 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:05 70.32.43.188 Nobis Technology Group, LLC 3669 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:05 64.120.60.122 Nobis Technology Group, LLC 4518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:05 70.32.43.188 Nobis Technology Group, LLC 3669 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 173.234.188.204 Nobis Technology Group, LLC 2505 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 64.120.60.122 Nobis Technology Group, LLC 4518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 173.208.16.248 Nobis Technology Group, LLC 3296 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 173.234.188.204 Nobis Technology Group, LLC 2505 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:06 23.19.131.10 Nobis Technology Group, LLC 4396 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.67.28 Nobis Technology Group, LLC 1378 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 173.208.16.248 Nobis Technology Group, LLC 3296 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 64.120.60.122 Nobis Technology Group, LLC 4518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 173.234.188.204 Nobis Technology Group, LLC 2505 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.131.10 Nobis Technology Group, LLC 4396 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 173.208.16.248 Nobis Technology Group, LLC 3296 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.67.28 Nobis Technology Group, LLC 1378 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:07 23.19.131.10 Nobis Technology Group, LLC 4396 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:08 23.19.67.28 Nobis Technology Group, LLC 1378 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:09 147.255.224.134 Nobis Technology Group, LLC 2361 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:09 147.255.224.134 Nobis Technology Group, LLC 2361 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 64.120.60.106 Nobis Technology Group, LLC 1518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 70.32.43.190 Nobis Technology Group, LLC 2963 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 147.255.224.134 Nobis Technology Group, LLC 2361 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 64.120.60.106 Nobis Technology Group, LLC 1518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:10 70.32.43.190 Nobis Technology Group, LLC 2963 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 64.120.60.106 Nobis Technology Group, LLC 1518 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 173.234.145.205 Nobis Technology Group, LLC 3493 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 70.32.43.190 Nobis Technology Group, LLC 2963 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 173.234.145.206 Nobis Technology Group, LLC 2492 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:11 173.234.145.205 Nobis Technology Group, LLC 3493 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 173.234.145.206 Nobis Technology Group, LLC 2492 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 173.234.145.205 Nobis Technology Group, LLC 3493 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 23.19.50.46 Nobis Technology Group, LLC 2827 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:12 173.234.145.206 Nobis Technology Group, LLC 2492 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:13 23.19.50.46 Nobis Technology Group, LLC 2827 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:13 23.19.50.46 Nobis Technology Group, LLC 2827 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:13 64.120.60.105 Nobis Technology Group, LLC 1194 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:14 64.120.60.105 Nobis Technology Group, LLC 1194 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:14 64.120.60.105 Nobis Technology Group, LLC 1194 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:15 173.234.116.237 Nobis Technology Group, LLC 4363 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:16 173.234.116.237 Nobis Technology Group, LLC 4363 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:16 64.120.60.174 Nobis Technology Group, LLC 2369 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 173.234.116.237 Nobis Technology Group, LLC 4363 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 64.120.60.174 Nobis Technology Group, LLC 2369 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 23.19.131.10 Nobis Technology Group, LLC 2648 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 64.120.60.174 Nobis Technology Group, LLC 2369 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:17 23.19.131.10 Nobis Technology Group, LLC 2648 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:18 23.19.131.10 Nobis Technology Group, LLC 2648 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:18 173.234.145.206 Nobis Technology Group, LLC 4154 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 23.19.130.121 Nobis Technology Group, LLC 3782 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 173.234.145.206 Nobis Technology Group, LLC 4154 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 23.19.130.121 Nobis Technology Group, LLC 3782 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 64.120.60.122 Nobis Technology Group, LLC 2141 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:19 173.234.145.206 Nobis Technology Group, LLC 4154 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:20 23.19.130.121 Nobis Technology Group, LLC 3782 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:20 64.120.60.122 Nobis Technology Group, LLC 2141 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 64.120.60.122 Nobis Technology Group, LLC 2141 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 173.208.95.126 Nobis Technology Group, LLC 3208 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 173.208.95.126 Nobis Technology Group, LLC 3208 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:21 64.120.60.174 Nobis Technology Group, LLC 3193 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 173.208.95.126 Nobis Technology Group, LLC 3208 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 64.120.60.174 Nobis Technology Group, LLC 3193 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 64.120.60.174 Nobis Technology Group, LLC 3193 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:22 64.120.44.150 Nobis Technology Group, LLC 3211 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 64.120.44.150 Nobis Technology Group, LLC 3211 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 108.62.33.51 Nobis Technology Group, LLC 3383 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 108.62.33.51 Nobis Technology Group, LLC 3383 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:23 64.120.44.150 Nobis Technology Group, LLC 3211 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:24 23.19.50.46 Nobis Technology Group, LLC 4534 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:24 108.62.33.51 Nobis Technology Group, LLC 3383 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:24 23.19.50.46 Nobis Technology Group, LLC 4534 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.130.86 Nobis Technology Group, LLC 3654 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.50.46 Nobis Technology Group, LLC 4534 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.130.86 Nobis Technology Group, LLC 3654 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:25 23.19.130.93 Nobis Technology Group, LLC 2090 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 23.19.130.86 Nobis Technology Group, LLC 3654 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 23.19.130.93 Nobis Technology Group, LLC 2090 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 69.147.233.52 Nobis Technology Group, LLC 4623 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 23.19.130.93 Nobis Technology Group, LLC 2090 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:26 64.120.60.121 Nobis Technology Group, LLC 1486 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 69.147.233.52 Nobis Technology Group, LLC 4623 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 64.120.60.121 Nobis Technology Group, LLC 1486 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 69.162.117.206 Limestone Networks 1906 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 173.234.116.232 Nobis Technology Group, LLC 4393 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:27 173.208.44.46 Nobis Technology Group, LLC 2169 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 69.147.233.52 Nobis Technology Group, LLC 4623 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.208.95.125 Nobis Technology Group, LLC 1316 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 64.120.60.121 Nobis Technology Group, LLC 1486 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 69.162.117.206 Limestone Networks 1906 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.234.116.232 Nobis Technology Group, LLC 4393 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.208.44.46 Nobis Technology Group, LLC 2169 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 108.177.157.70 Nobis Technology Group, LLC 1659 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.208.95.125 Nobis Technology Group, LLC 1316 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 69.162.117.206 Limestone Networks 1906 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:28 173.234.116.232 Nobis Technology Group, LLC 4393 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.95.106 Nobis Technology Group, LLC 1650 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 108.177.157.70 Nobis Technology Group, LLC 1659 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.95.125 Nobis Technology Group, LLC 1316 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.44.46 Nobis Technology Group, LLC 2169 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.131.10 Nobis Technology Group, LLC 1104 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.131.10 Nobis Technology Group, LLC 1132 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 108.177.157.70 Nobis Technology Group, LLC 1659 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 173.208.95.106 Nobis Technology Group, LLC 1650 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.131.10 Nobis Technology Group, LLC 1104 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:29 23.19.67.211 Nobis Technology Group, LLC 1884 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.131.10 Nobis Technology Group, LLC 1132 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.67.214 Nobis Technology Group, LLC 1295 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 173.208.95.106 Nobis Technology Group, LLC 1650 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.131.10 Nobis Technology Group, LLC 1104 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.131.10 Nobis Technology Group, LLC 1132 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.67.211 Nobis Technology Group, LLC 1884 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 23.19.67.214 Nobis Technology Group, LLC 1295 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:30 64.120.60.118 Nobis Technology Group, LLC 2075 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 23.19.67.211 Nobis Technology Group, LLC 1884 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 23.19.67.214 Nobis Technology Group, LLC 1295 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 64.120.60.120 Nobis Technology Group, LLC 4950 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 69.162.119.4 Limestone Networks 2862 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 64.120.60.118 Nobis Technology Group, LLC 2075 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 64.120.60.120 Nobis Technology Group, LLC 4950 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:31 69.162.119.4 Limestone Networks 2862 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 64.120.60.118 Nobis Technology Group, LLC 2075 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 147.255.224.134 Nobis Technology Group, LLC 1603 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 64.120.60.120 Nobis Technology Group, LLC 4950 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 69.162.119.4 Limestone Networks 2862 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:32 147.255.224.134 Nobis Technology Group, LLC 1603 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 173.208.44.36 Nobis Technology Group, LLC 3290 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 147.255.224.134 Nobis Technology Group, LLC 1603 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 64.120.60.118 Nobis Technology Group, LLC 2677 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:33 173.208.44.36 Nobis Technology Group, LLC 3290 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:34 173.208.44.36 Nobis Technology Group, LLC 3290 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:34 64.120.60.118 Nobis Technology Group, LLC 2677 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:34 173.208.16.250 Nobis Technology Group, LLC 1802 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:35 173.208.16.250 Nobis Technology Group, LLC 1802 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:35 64.120.60.118 Nobis Technology Group, LLC 2677 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:35 173.208.16.250 Nobis Technology Group, LLC 1802 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:38 108.177.168.156 Nobis Technology Group, LLC 2832 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:38 108.177.168.156 Nobis Technology Group, LLC 2832 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:38 23.19.130.93 Nobis Technology Group, LLC 4597 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 108.177.168.156 Nobis Technology Group, LLC 2832 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 23.19.130.93 Nobis Technology Group, LLC 4597 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 69.162.117.206 Limestone Networks 3681 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:39 23.19.130.93 Nobis Technology Group, LLC 4597 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:40 69.162.117.206 Limestone Networks 3681 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:40 69.162.117.206 Limestone Networks 3681 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:40 64.120.60.121 Nobis Technology Group, LLC 3356 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:41 64.120.60.121 Nobis Technology Group, LLC 3356 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 64.120.60.121 Nobis Technology Group, LLC 3356 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 64.120.79.221 Nobis Technology Group, LLC 1410 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 108.62.237.205 Nobis Technology Group, LLC 2969 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 64.120.79.221 Nobis Technology Group, LLC 1410 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:42 108.62.237.205 Nobis Technology Group, LLC 2969 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 64.120.79.221 Nobis Technology Group, LLC 1410 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 108.62.42.18 Nobis Technology Group, LLC 2158 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 23.19.130.93 Nobis Technology Group, LLC 1789 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 108.62.237.205 Nobis Technology Group, LLC 2969 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 173.208.44.40 Nobis Technology Group, LLC 1441 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:43 108.62.42.18 Nobis Technology Group, LLC 2158 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.234.12.178 Nobis Technology Group, LLC 2411 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.208.44.40 Nobis Technology Group, LLC 1441 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 23.19.130.93 Nobis Technology Group, LLC 1789 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 108.62.42.18 Nobis Technology Group, LLC 2158 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 23.19.130.93 Nobis Technology Group, LLC 1789 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.208.44.40 Nobis Technology Group, LLC 1441 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:44 173.234.12.178 Nobis Technology Group, LLC 2411 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:45 173.234.12.178 Nobis Technology Group, LLC 2411 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:47 64.120.79.222 Nobis Technology Group, LLC 4601 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:47 69.162.80.59 Limestone Networks 3514 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 69.162.80.59 Limestone Networks 3514 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 64.120.79.222 Nobis Technology Group, LLC 4601 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 173.234.145.205 Nobis Technology Group, LLC 4688 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 64.120.79.222 Nobis Technology Group, LLC 4601 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 69.162.80.59 Limestone Networks 3514 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:48 173.208.44.46 Nobis Technology Group, LLC 4835 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 173.234.145.205 Nobis Technology Group, LLC 4688 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 173.208.44.46 Nobis Technology Group, LLC 4835 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 74.63.192.36 Limestone Networks 1339 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 173.234.145.205 Nobis Technology Group, LLC 4688 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:49 64.120.60.146 Nobis Technology Group, LLC 3668 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 173.208.44.46 Nobis Technology Group, LLC 4835 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 74.63.192.36 Limestone Networks 1339 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 23.19.131.11 Nobis Technology Group, LLC 3868 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 64.120.60.146 Nobis Technology Group, LLC 3668 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 74.63.192.36 Limestone Networks 1339 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 70.32.43.189 Nobis Technology Group, LLC 4246 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 23.19.131.11 Nobis Technology Group, LLC 3868 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:50 64.120.60.146 Nobis Technology Group, LLC 3668 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:51 23.19.131.11 Nobis Technology Group, LLC 3868 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:51 70.32.43.189 Nobis Technology Group, LLC 4246 66.8.214.196 Road Runner 8118 [S], 2013-03-28 7:34:51 64.120.60.139 Nobis Technology Group, LLC 1105 66.8.214.196 Road Runner 8118 [S],

5 4

Is my relay fine?
by Brandon Steele 26 Mar '13

26 Mar '13

This is my first time sending in a question in this mailing list about my relay. Here's the link to it: http://torstatus.blutmagie.de/router_detail.php?FP=c6528e10911ec94cc85430e9… I realize some of the router flags are checked. I just want someone to check it quickly to make sure that everything is all right. Thanks!

4 4

port setup
by Art 21 Mar '13

21 Mar '13

I have a Westell A90-750018-07 router and I need to set up port forwarding for port 9001 and 9030. My router won't let me do it however, saying: *Invalid End Port value of NULL Please enter a valid number* when I attempt to do so. I entered 9001 in the *Global PortStart *box and**the other empty boxes on the setup page are *Global PortEnd *and *Base HostPort.* What values do I put in the Global PortEnd and Base HostPort boxes????* * TIA. Art* *

4 5

Does obfsproxy advertise ?
by Exocet Tor Node 19 Mar '13

19 Mar '13

Hello all. Beside my relay, I'm also operating a bridge on another server. I've recently installed obfsproxy, mainly for test purpose. The obfs2 service is successfully registered (per log message) but, as of today, I've never received any connection on it (iptables rule show no packet to the dedicated port). The service is running for more than 2 weeks now. My question is : does obfsproxy advertise like the regular bridge service ? Best regards.

2 1

DMCA letters
by jvoss＠altsci.com 13 Mar '13

13 Mar '13

Hi all, I've been running a Tor exit node on my new server for 16 days. Today I received my second automated DMCA infringement notice from HBO. I sent them the boilerplate you see at the bottom of the message both times. My colo provider Hurricane Electric understands Tor, which is awesome. I don't think it'll be an issue, so I'm happy with this. I'm wondering if anyone receives a large number of DMCA infringement notices and whether there was a resolution. It would certainly make my life a little bit more difficult to send more than one of these per week. When I got my first letter I was pushing 5 Mbps (megabits) and now I'm pushing 9 Mbps. I've set the RelayBandwidthRate to 5120 KB which should give a max rate of 41 Mbps. If infringement notices increases linearly with traffic, this could become an issue. I'm happy to share the infringement notices if anyone is interested. I followed a few of the tips from https://blog.torproject.org/running-exit-node , I got a separate IP address and I reduced the exit policy. I plan to update the reverse dns. I don't feel like reducing the exit policy does anything because BitTorrent was designed to run on any high port. Also, reducing the exit policy blocks researchers who are doing port scans and header grabbing over Tor. That's a point of contention for me because I know legitimate researchers use Tor for that purpose. Does anyone have any data or anecdotes on how exit policy affects malicious use of Tor vs legitimate use of Tor? Btw, my server is 216.218.134.12. I'm running a patched version of tor 0.2.3.25 which fixes a few bugs I found in buffer events. See https://trac.torproject.org/projects/tor/ticket/7788 for more info. Uptime is now 6 days, 13 days without a crash. Thanks, Javantea ------------------- Dear Andrew Martin: The IP address in question is a Tor exit node. https://www.torproject.org/overview.html There is little we can do to trace this matter further. As can be seen from the overview page, the Tor network is designed to make tracing of users impossible. The Tor network is run by some 2500 volunteers who use the free software provided by the Tor Project to run Tor routers. Client connections are routed through multiple relays, and are multiplexed together on the connections between relays. The system does not record logs of client connections or previous hops. This is because the Tor network is a censorship resistance, privacy, and anonymity system used by whistle blowers, journalists, Chinese dissidents skirting the Great Firewall, abuse victims, stalker targets, the US military, and law enforcement, just to name a few. See https://www.torproject.org/about/torusers.html.en for more info. Unfortunately, some people misuse the network. However, compared to the rate of legitimate use (the IP address in question processes approximately 11 megabits of traffic per second), abuse complaints are rare. https://www.torproject.org/docs/faq-abuse.html.en This is the second e-mail from you that I am replying to. The only thing that has changed is that I have increased the bandwidth to 9 megabits per second. If you have further questions, feel free to contact me at ------------ Sincerely, -----------

5 6

Local problem or Authority problem?
by Steve Snyder 12 Mar '13

12 Mar '13

This is the 2nd time I've seen the message below in the last few days. Is this a local problem, or is this Authority server having network problems? --------------------- Mar 12 16:13:57.000 [warn] Received http status code 504 ("Gateway Time-out") from server '154.35.32.5:80' while fetching consensus directory. Mar 12 16:13:57.000 [warn] Received http status code 504 ("Gateway Time-out") from server '154.35.32.5:80' while fetching "/tor/server/d/04074EB96250570D79D54ABF8BCCB5D78DCAF288+04A4D41B424AEDA92907E8FD2D3E62150EDF6C2B+05FD952570E17B917395B0A1B85BE3A9D0B2CDFB+063AD80363C90979C3BF86B7059A418C5FD5FEE3+087D53B75320FCB0CA6C3410F1772A75A1BCCD1C+08BE6F4FDAED1B19ED764696DC1BE56B738228E0+09579C2014F3B0419E98E78F2A25D8DD6C96B2E2+0999BB98E0F66C0B888530E3F2E5212DDDF0C6DE+09B0FA1C28671CB104AFC9EDD65239084E407BA0+09BDCC19AD5AB4C3926F7A68F283746871D4D56F+0AB6B62AE4772EE2965DFDAFB8130ECE9CD36884+0C03BE2409199A5D144FE71C88978393DDD421BB+0C2F936E8C2612AAC08C01A0351CE38879E9BDDC+0C7CC03C29DCA1A5F1B52B960EEC9626D174B58E+0D36F472EBFAE10CB177AACC6A119BE3F9DCE08C+0D43FC4BC3A709B0466C824B66685B735CA0238D+0D92EF510A781FC282D09E4AD59BA0C549C38CB5+0DE1BBE15B66DEDDA4BA26CCB81243CA5D5B4361+0E68E2980775EC1A4DCF243B300CD10B667D727E+0EC893270D60852719EA61437365D4E04B58DFF0+0FCF73CC589E66B0A61F5243E98EE181556E58DA+1383AED682BA066E90AB4A129313F8CB74083009+138AC265F2027B064686E061B9BE95B4375F1EDD+14AD0D65F7B8CAB4D1244A81A94435D72C405ED2+163A20C60F5B3852DC4AE997B1AC684167597DA1+176D2F97C6D94847812BA237E5E8FCBC1C06DE23+1775169594A4FC2E0BFF2DC3A72B1250E48AF967+1925372A11574505E657E5FBA91790F1E199E9A7+1A81CCF4DA2D1083C486502D7A1531E0FDA9A976+1A8FFED1415988D7F150DB934B142D367A91F1D4+1AA4EF44F5A1530A7EBF7FCF58F9B9F73B8C8CBD+1AC92989A40613D367D4FBC938260743F735D006+1B047A3E77D42D6F90AC70AD9087C87273608874+1BD1A901C208924FF723449204C1B739253CFC88+1C88BA75E091BA0AD0586F4496563A8108EF0AFD+1D9BD53B703F5B74D35FEFE90A7AAB877C9811C3+1DDB372BA6ED786C00A0A544FC6111388039E208+2007140616A3236E274F96794033B8100FD483E2+210AA9E1A6A081FD73E2ABFB53B58484CFD86854+215DFFBB03D9B0273E54A5312A8D0CC8790FBEBF+2188A991565919B0A93FC008D7F7CA3B88226CD0+21A3880C02DD2F329975A672A378BCF456900D68+21CF5A07F11BD114FDD83A1A9D84011CDEB4B553+22CDC2869521DAB7B894EAB61C22CBD4F91EBFEA+247120DAD42F112C75EA31B08305AEA1B8030C29+24D23ACAA3B84B6FAE1C8C3C6397C8FA72311960+2569B8E88056D46BD791D3EF828669659A37E0C9+262FA174601FDCDB024BED3040929F21BDC36D48+27FEE7C12A2F2CED4FB4BFD8B453740CC14CBE0A+2AF5996140CB3C40ADD81C1C56734EEAB12EE967+2E94AE3BD0CE4F5DFE7779D5358B0B87825B8637+2E95EC620F01E26C120D8097176C4E2A39873F44+2EC372E877F32770625386C46AA1C0A325B23B2C+2FB82F9DB850312DF102F15C904B9DD6D01273B7+3104BEF38E684D052EB5358B0DB8A0221A1D7E2D+3214DEC5847CB9662F76AD2A73F35AD5EB8ADAC5+327371CEF85B0358A179EDBC6305601F3E1A617F+3282DD9CA468BCD87EF104A947FC087BE8457CD4+32AA787CB8185DBB1B371DC3A055C9D54EE263AF+334C9E6D243E607D7F309F6D49EA617D18CBA4AC+33DF5016BA97AA6B00F30C753A9DC2A6B8046F93+3444C8C526C39133A91F519C07476BF40F422330+34D3650408E276D0204EB8711B083432AB5F2736+3521734E1923619DBB92E43FBA1454995BD9BFA2+35624B39BC583AFD70F21C4E4F16E316D83898C2+366E6CB7854E6FB47411484CCF16316967C8BB68+372B550402CF1CAE0EB53CF03B036619521F5401+37BCE27DA528E4B5ECB639EF38768415981376B8+3990219DEFB3E6991ACE408A1D44CBCD226673D1+3D0E6313BEF11C56B4A1703716EACB2D2BFAF170+3D38952385BD797A7E42AE98889BBA39334CE883+3D480580359358750F66AFE84E187AE789380880+3D9F982ECAEE4FA35D4A963BECFB7F3E7B6659C8+40193F0DF2D4041C421455C079272038F9BC3DAC+40BBB8FB6F665C87D9297D67BB053BE388611A09+40DF0911958AEC11481AFE923D0EEA2B7A8EC7DF+419E7503347EA5CD467BB8383565AEC08722A417+41EF33A6492F7563978A369A23F8753F9AE18DB3+42049023A0ADD501B4426F851AC96CE184DC53BD+42F6AA4DF5B2DF4E0C694E7E8D44F07AE0273983+434CE452D749AB0ECB3328F1173EA5C5D9563F28+43AF557F22152E4868AFCBC637F67E3D28502CE5+44FFB205642C55639AB23C33B342B7B4BA52A40F+4547E5892491161DA48E3A85F387F414453D767F+458D39FAFA9D37E137D810E42FC3E3FCA73D1DD1+45B341C87E3765EC668F3F79FEAA775FFAB0FB72+46146B22376DD4CF48EFE695360D4E04C6B27A5F+4672A76E50B62C6ECB36374904BD2E27D58E0F34+473631BF990138E4F0F9DBC6F92A291346F403C6+49067AB9F33B3A813055D1F06C4196AA01952F1F+496341B3CF1F500BF3544EB4D4B4C65A96A663D0+4B03C837FBE98892ABFBD8F88A87DD253F8CBCE3+4D66AEA3A987CB19F6F1A416369FE52DD90C5B97+4D9705EB0D8539C6DB31FB683ADABEAA8B50237C+4DA6EF73ED368372F0639D030408506B7F1874FE+4E825DC538DA34966EA64712E6B7DD84613FD238.z". I'll try again soon.

3 2

ORPort NoListen
by Sina Eetezadi 11 Mar '13

11 Mar '13

Hi! I want to have port 443 advertised but listen on port 9001. My router then forwards 443->9001 to the machine tor is running on. It works with this: ORport 433 ORListenAddress 0.0.0.0:9001 However I thought this is deprecated and I rather use: ORport 443 NoListen ORPort 0.0.0.0:9001 NoAdvertise The latter however does not seem to work. Arm for example still errors "binding failed" and I see no incoming connections. Is this a bug? Thanks. SE

2 4

relay exposed?
by eliaz 09 Mar '13

09 Mar '13

So, some hours ago I noticed a circuit on the network map consisting of a relay in my own country, another one 11,000 km away, and - surprise - my own bridge relay. Can this be so? I thought that bridges, though published, are anonymous. My TBB configuration seems fine, it's what I've used in previous implementations. The only difference I've written into torrc for this run is SocksPort auto. The bandwidth rates seeming way higher than should be allotted to my bridge (10485760 & 5242880, rather than the 196608 & 98304 of previous runs), I checked my bandwidth-limit setting and found that I had inadvertently chosen > 1.5 Mpbs instead of 1.5 Mpbs (but as I'd noted to myself previously, the higher setting doesn't seem to matter, except maybe to improve performance a bit). The relays_ published output is as usual (not that I'd be likely to recognize anything amiss in that report). One other thing that may be pertinent and which I've wanted to ask about for a long time is this: I occasionally for convenience run my open browser from the same vista machine on which I'm running the TBB at the same time. Is this bad practice, and could it have been the reason that the bridge nickname showed in the network map? - eli gpg: 0xE498E90D

1 0

DynDNS and TOR bridge
by Sina Eetezadi 06 Mar '13

06 Mar '13

Hi, I have a bridge running and since my ISP is changing my IP at least daily, I thought it might be a good idea to set my DynDNS in the torrc file. Is it a good idea? How do I set that? Thank you. Sina

5 8

Recommended specifications for 1Gbps exit
by Matt Joyce 05 Mar '13

05 Mar '13

I am wondering if anyone with experience in this area could advise me some on recommended specifications for a 1Gbps exit I think my latest once needs a package upgrade to handle it, currently seems stuck at around 100Mbps worth of traffic. Currently it has access to 3 v cores @1.33Ghz and 1GB of RAM and I think the latter might be becoming the limit instead now I had thought it was the CPU when it had just the one core but that alone hasn't helped. I am not entirely sure if tor is infact using the other cores though watching with top it is sitting at 100 or a fraction over like 104% or so. MaxCPU's is set in torrc to 4 as the OS sees 4 virtual cores but is capped to 300% by the hypervisor perhaps it should be set to 3 not sure if there is any benefit in setting to 4 I have limited experience with virtual servers but unfortunately a fully dedicated server for tor is financially out of my budget at the moment. Also, just to confirm while I'm aware it's very possible that the limitation could be bandwidth given it shares with the other VPS'es on the host I don't believe that was the case, I pulled a backup from there to another server of mine on a different AS and continent and it transferred at 250Mbps while tor was running at 100Mbps the entire time, so unless the contention is over the download which seems less likely for a server I think we should be able to get a good 300Mbps of exit capacity out of this possibly more. So can anyone can advise on recommended CPU, RAM have to consider budget but will try and meet them, also if there are any settings I should check in torrc?

5 9

[ANNOUNCE] check_tor.py: a Nagios check for Tor relays
by Jérémy Bobbio 26 Feb '13

26 Feb '13

Hi! I hereby announce the first release of check_tor.py. It is meant to be used with Nagios (or a similar tool with a compatible interface) in order to check if a bridge, entry node, middle node or exit node is working as intended. check_tor.py is a Python script that relies on Stem [1] to control a dedicated Tor instance in order to perform its checks. For more documentation, please refer to the README at: <http://anonscm.debian.org/gitweb/?p=users/lunar/check_tor.git;a=blob;f=READ…> Download through Git: $ git clone git://anonscm.debian.org/users/lunar/check_tor.git $ cd check_tor && git tag -v 0.1 Browse using gitweb at: <http://anonscm.debian.org/gitweb/?p=users/lunar/check_tor.git> check_tor.py is licensed under GPLv3+. Contributions are highly welcome. [1] https://stem.readthedocs.org/ -- Jérémy Bobbio .''`. lunar(a)debian.org : :Ⓐ : # apt-get install anarchism `. `'` `-

2 2

Google Groups Exit Policy Reject?
by Jonathan Baker-Bates 25 Feb '13

25 Feb '13

Hi All, I've been forwarded a request to block Google Groups IPs due to some abuse or various usenet groups. Is anyone else rejecting from these IPs, and should I do the same? Thanks, Jonathan

4 5

US Investigators seem to learn
by Moritz Bartl 22 Feb '13

22 Feb '13

Hi, I thought I would let you know: Our US hoster is regularly contacted by law enforcement about our exits there. Some agents ask if the traffic pattern is balanced, ie. if the same amount of traffic enters and leaves the box. I always argue that this is a good indicator for Tor traffic, and that it is bad to mix Tor traffic with other traffic for that exact reason. -- Moritz Bartl https://www.torservers.net/

7 9

Problems with Debian package and low ports
by Chris Baines 14 Feb '13

14 Feb '13

I am having some problems with tor (version 0.2.3.25-1), I get warnings when it resumes form hibernation: Feb 11 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied Feb 11 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:443 Can anyone help?

11 11

Re: [tor-relays] Problems with Debian package and low ports (Chris Baines)
by Christian 14 Feb '13

14 Feb '13

Good night Chris, I hope I don't misunderstand your issue, but if you use hibernation, you use a kind of desktop setup, aren't you? If port forwarding running a firewall and tor on the same machine (that's hibernating) behind a normal router looks tricky by means to verify the config, see my suggestion. If my assumption is correct, you have to set port forwarding in your router, say port 443 to 9090, and then use the torrc file to let tor listen on port 9090, but to advertise port 443. This makes tor bind to a higher port than 1024 and thus not needing root privileges if you run tor as the default user debian-tor, but lets your machine be available on port 443 although hibernating might be a bad idea for a tor node. ;-) If you use a home ISP with small bandwidth, maybe you'd better be a bridge (sufficient uptime also appreciated). I hope this could help. Sincerly, christian Am Mittwoch, den 13.02.2013, 19:35 +0000 schrieb tor-relays-request(a)lists.torproject.org: > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Problems with Debian package and low ports (Chris Baines) > 2. Re: Problems with Debian package and low ports (Wessel Nieboer) > 3. Re: Problems with Debian package and low ports (Nils Vogels) > 4. Re: Problems with Debian package and low ports (theo(a)caber.nl) > 5. Re: Problems with Debian package and low ports (Roman Mamedov) > 6. Re: Problems with Debian package and low ports > (Christopher Baines) > 7. Re: Problems with Debian package and low ports > (Christopher Baines) > 8. Re: Problems with Debian package and low ports (Roger Dingledine) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Feb 2013 16:41:54 +0000 > From: Chris Baines <cbaines8(a)gmail.com> > To: tor-relays <tor-relays(a)lists.torproject.org> > Subject: [tor-relays] Problems with Debian package and low ports > Message-ID: > <CAGGGvRs=FYNeKX9_7Ymyn1k2r1xPL1qv11BDGVABgmyDMqA9ZQ(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I am having some problems with tor (version 0.2.3.25-1), I get > warnings when it resumes form hibernation: > Feb 11 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied > Feb 11 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:443 > > Can anyone help? > > > ------------------------------ > > Message: 2 > Date: Wed, 13 Feb 2013 17:44:02 +0100 > From: Wessel Nieboer <weebl(a)weebl.me> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Problems with Debian package and low ports > Message-ID: <511BC2D2.40507(a)weebl.me> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Op 13-2-2013 17:41, Chris Baines schreef: > > I am having some problems with tor (version 0.2.3.25-1), I get > > warnings when it resumes form hibernation: > > Feb 11 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied > > Feb 11 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:443 > > > > Can anyone help? > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > Does it work when you've just booted your computer? > > -Wessel > > > ------------------------------ > > Message: 3 > Date: Wed, 13 Feb 2013 18:07:53 +0100 > From: Nils Vogels <bacardicoke(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Problems with Debian package and low ports > Message-ID: > <CAEM+PCU-0xVPEA+H2cMBZCeTgJwhAcWqG7N2Ve567t_sbdrGEw(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Tor has already changed to a non-privileged user, but you are trying to > bind on ports that only root is allowed to bind on. > > Two solutions: > > 1) Run tor as root (really, a bad idea) > 2) Bind to other ports than 80 and 443. Since you are resuming, you are > unlikely to be a stable relay/exit/bridge anyway, so you can basically > choose any port you want and just use it for your own traffic only. > > On Wed, Feb 13, 2013 at 5:41 PM, Chris Baines <cbaines8(a)gmail.com> wrote: > > > I am having some problems with tor (version 0.2.3.25-1), I get > > warnings when it resumes form hibernation: > > Feb 11 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied > > Feb 11 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:443 > > > > Can anyone help? > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > > > -- > Simple guidelines to happiness: > Work like you don't need the money, > Love like your heart has never been broken and > Dance like no one can see you. >

1 0

Re: [tor-relays] [tor-talk] Legal problems: TOR relay & Torrents in .de
by grarpamp 11 Feb '13

11 Feb '13

> I've snail-mailed them a letter based on what Moritz had posted. They > replied with a standardized letter without even commenting on my > statements. It's basically saying "Last chance to pay or we'll go to > court." > > So I'm a little unsure whether or not it's now time to actually > consult a lawyer or wait until FOX makes it's next move. I believe what some others were saying is to simply ignore any initial complaints that come in which appear to be automated or are in some way not sufficiently personalized, lacking in real data, or stamped by a court. Just because someone complains from getting emailspam or can scrape peers off a tracker could just be a courtesy or idle probe. If such first notices bother you, sure, have an initial consult with a lawyer for potential future engagement if needed. But now that you have snailmailed them, it is raised on different level. One for which some would surely say a five minute chat with a prospective lawyer is wise. Also, if other people on the list get such first notices and don't know what to do with them, redacting any identifying material and posting the remaining full text [from an anonymous account if prudent to further avoid confirmation] would let others get a sense of what is out there and offer any experience. Just saying 'I got a mail about filesharing from my node and I mailed them back' doesn't help the poster or others. Then again, we're not lawyers, consult a real one as needed.

1 0

EC2 IP vs Region & Does this matter in the Tor network?
by David Gilbert 11 Feb '13

11 Feb '13

Hello, I'm operating 6 relays in the EC2 where 4/6 claim to be located outside the US but only 1/6 show up as outside of the US based on the IP address and report on atlas (https://atlas.torproject.org/#search/relay1org, don't heckle, I'm getting an idea of pricing and boosting speed over the next 5 months). Now, I'm curious if the IP address vs region it's supposedly operating in matters at all. Will people in the middle east be less likely to connect to my Tokyo/Singapore based relays because the IP address shows its in the USA? Or any other issues? Also, if this does in fact affect the effectiveness of my relays in those regions, has anyone had experience being able to acquire an IP from Amazon for other regions? I do not have a support contract, since I'm paying for this out of my own pocket so I'm unable to contact tech support. I would be inclined to pay whatever fees it costs to get it done, if I knew exactly what it is I need to do. - David

3 4

Possible bug on Tor 0.2.4.8-alpha and 0.2.4.9-alpha
by Jon 06 Feb '13

06 Feb '13

I started the Tor alpha yesterday, and now have numerous instances of " " Bug/Attack: unexpected sendme cell from client. Closing circ." Anything to be concened about Jon

1 0

Newbie question
by Chuck Bevitt 05 Feb '13

05 Feb '13

I'm running an exit node using my home ISP (yes, I've read the warnings). My question is: what happens when my ISP changes my IPAddress? Will existing connections to my node be lost and will the node reestablish itself? Thanks, Chuck Bevitt Sent from my iPad

5 5

My Relay has slowed significantly.
by Matthew Harrold 04 Feb '13

04 Feb '13

Hello all. This is my first time using a mailing list, so apologies if Im not doing it right! I have ran a couple of Tor Relays now for a few months, one was steady and reliable, and providing about 2MB/s of bandwidth. Of late, its slowed down dramatically. A reboot resolved it temporarily, but its slowed right down again, below 500KB/s. You can see the graph here- https://atlas.torproject.org/#details/2DAEE4EBA687A517F8B473894341A56820CDD… Does anyone have any suggestions? I have checked with my ISP and they are not throttling or managing the traffic in anyway, and my CPU and RAM isnt under heavy load. Ive uploaded my torrc here- http://pastebin.com/ZCnLQF0w I have read that file discriptors can also be a problem, Im not sure if this is relevant but- $ sysctl fs.file-nr fs.file-nr = 832 0 199036 Thanks in advance for your help, keep up the good work!

4 10

help with bridge
by s 03 Feb '13

03 Feb '13

hello i am not sure this goes here but ill give it a shot i want to be able to configure a nas as a bridge is it posssible and what would i have to do? as well as run one on my desktop if yall can shoot me line it would be helpful

1 0

Moritz in January
by Moritz Bartl 01 Feb '13

01 Feb '13

Hi, - Was invited as a speaker at CryptoParty Luxemburg. Gave two talks about Tor, one basic introduction/overview, and one about operating Tor exits. Afterwards, I helped starting Frënn vun der Ënn, a Luxemburg copy of Torservers.net by local members of the CCC -- some of which I already met at Haxogreen 2012, a Luxemburg hacker camp. They are awaiting official approval by the government, and then I will probably sign over our Luxemburg exit to them ( www.enn.lu ) - Wrote a German article about Tor by request of the CCC for their printed magazine "Datenschleuder". It will also be published on the web. - Wrote a small Python script that stores relay contact info from Onionoo data in a local database, together with "first seen" and "last seen" dates. I am currently limiting it to relays faster than 25 MBit/s. This will help me to welcome new relay operators, as well as contact "missing" operators to ask why they are gone. I am currently not publishing the database itself, but the script is at https://github.com/moba/tor-contacts-tracker - I became more accustomed to editing the Torproject website. Pushed some changes, most importantly a completely revised set of install instructions on Mac OSX using the unsafe Homebrew. https://trac.torproject.org/projects/tor/ticket/7989 - Most of my time again went into Help Desk and IRC. For number of closed tickets, see Runa's report which will come soon. - Was offered 2-3 Gbit/s of spare bandwidth at a friendly CH ISP. Passed the offer to the Swiss Privacy Foundation to avoid running more high bandwidth nodes as Torservers.net. -- Moritz Bartl https://www.torservers.net/

1 0

ESMTP Filtering by Santrex
by Moritz Bartl 31 Jan '13

31 Jan '13

-------- Original Message -------- Subject: ESMTP Filtering by 46.166.163.163 Date: Wed, 30 Jan 2013 18:57:53 +0100 From: Moritz Bartl <moritz(a)torservers.net> To: abuse(a)santrex.net Hi, Your customer at 46.166.163.163 runs a Tor exit relay (hooray! great!). The server should be configured in a way that does NOT tamper with outgoing or incoming traffic, but it looks like Santrex (you guys) are at least actively filtering/redirecting ESMTP Port 587 traffic. Trying 74.125.137.108... Connected to smtp.gmail.com. Escape character is '^]'. 220 spamfilter.santrex.net ESMTP Postfix Trying 192.0.43.10... Connected to example.com. Escape character is '^]'. 220 spamfilter.santrex.net ESMTP Postfix Please turn that off, or at least let your customer know about it so they can block the affected ports. Thanks! -- Moritz Bartl https://www.torservers.net/

1 0

Public Munin Graphs: Security Risk?
by Moritz Bartl 31 Jan '13

31 Jan '13

Hi! I finally deployed Munin across our exit nodes. The graphs are currently public, and I don't see an obvious reason for not doing that. Any objections? https://www.torservers.net/munin/ -- Moritz Bartl https://www.torservers.net/

3 2

iptables for relays not behind a nat
by Chris Baines 31 Jan '13

31 Jan '13

Can anyone help with equivalents of the iptables rules given here https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#HowcanImakemyrelay… but for a relay on a vps with a static ip? Thanks, Chris

3 2

University Exit Node Success Stories
by Patrick R McDonald 27 Jan '13

27 Jan '13

All, I am working with various PoC for US universities in an attempt to get them to run fast exit relays. While I am making progress on the universities running a Tor node, most are very hesitant to run an exit node. From several, I received the impression that this was the result of not wanting to be first. To counteract this fear, I am hoping this list can provide some success stories for the above scenario to provide the universities. Looking forward to receiving your feedback, Patrick

1 0

Re: [tor-relays] Contents of tor-relays digest...
by syrus f 27 Jan '13

27 Jan '13

my country block all websites and let see few sites. I use tor . I add some additional bridge but It stop in level:"load relay information" what I must to do?

1 0

[warn] Tried to establish rendezvous on non-OR or non-edge circuit.
by Samuel Walker 26 Jan '13

26 Jan '13

Hi, I've started receiving this message on my relay (non-exit, non-hidden-serivce) > [warn] Tried to establish rendezvous on non-OR or non-edge circuit. I've had a look in the bug tracker, and it looks like it was previously noted under 4171, with the cause being 4641. Both now fixed. Should I be concerned over this? Many Thanks

2 1

Can I enable IPv6?
by cmeclax 26 Jan '13

26 Jan '13

I just upgraded to version 0.2.3.25 from the latest pkgsrc quarterly, and I have an IPv6 address. Can I tell other relays that they can connect to me on IPv6? The port number will be different, as I'm forwarding one port on the router to a different port on the Tor box. cmeclax

2 1

mouseHouse - Why not used more?
by Sina Eetezadi 23 Jan '13

23 Jan '13

Hi all, I am wondering why my TOR server "mouseHouse" is not used more? I configured 40k and 60k burst, buts its only barely used. Any hints? Thank you.

2 1

running relay severely degrades network performance eventually
by Nicolas Bock 22 Jan '13

22 Jan '13

Hello list, every time I run a relay on a Comcast cable connection, after a while (a few hours to days) other network operations such as DNS lookups slow down to such an extent that the network becomes unusable. Unfortunately I don't know how to exactly pinpoint what the problem is, but found that the only reliable solution at such a point seems to be to reset the cable modem. Is that a known issue? Could you suggest how I can diagnose this more accurately? Thanks, nick

4 3

Exit relaying: What regulations exist in your country?
by Moritz Bartl 20 Jan '13

20 Jan '13

Hi, I have revised https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines some more, adding the most relevant legal paragraphs for Germany and USA. What are the exact regulations in your country? If you know which sections, paragraphs etc, add it to the wiki or let me know. -- Moritz Bartl https://www.torservers.net/

2 1

DigitalOcean, cheap VPS that's ok with middle relays
by Micah Lee 13 Jan '13

13 Jan '13

FYI, I just discovered a VPS provider DigitalOcean, and they seem fine with people running non-exit nodes: https://www.digitalocean.com/community/questions/tor The cheapest plan is $5/month (256mb ram, 1 core, 20gb drive) with unlimited bandwidth. They give you New York and Amsterdam IP addresses. I haven't tried running a relay on it so I don't know how much bandwidth you can practically use, but it looks promising. -- Micah Lee https://twitter.com/micahflee

12 14

What's wrong with TorStatus?
by Steve Snyder 12 Jan '13

12 Jan '13

The TorStatus pages at rueckgr.at and all.de have stopped reflecting the actual state of the Tor relays. The page at rueckgr.at displays uptime as the length of time between 04 Jan and now, regardless of the actual history of the relays. The page at all.de is even worse, calculating uptime as the days since 06 Dec 2012. The former shows no less than uptime of 6 days and the latter shows every relay as having 35+ days of uptime. The page at blutmagie.de has an accurate representation of relay uptimes, but their bandwidth stats are always inaccurate, so there really is no single TorStatus page that one can look at to get an accurate view of Tor relays. What's going on with TorStatus?

4 3

Hello guys. Is is possible to choose one's Entry Guards?
by Coyo 11 Jan '13

11 Jan '13

I didn't realize the TOR Project had their own mailing list server, though it makes sense. I'm studying tor relays, especially obfsproxy, and I thought I'd go ahead and ask a question. If you have a hidden service, and hide that on Server A, then have it connect via obfsproxy to Relay B, can you configure a manually-chosen list of entry guard relays to enter the wider Tor Network from Relay B? [Hidden Server] -- obfsproxy --> [Bridge Relay] -- tor --> [Specific Trusted Entry Guard Relays] -- tor --> [TOR Network] Is this currently possible?

2 5

Registration of a Tor node at the German Bundesnetzagentur
by tor-admin 11 Jan '13

11 Jan '13

Hi, this is a question more specific for the German jurisdiction. At the 29C3 in Hamburg I attended a interesting talk about open WIFI (http://is.gd/9G8AVA unfortunately in German) who was given by Reto Mantz (http://www.offenenetze.de/) He gave the advice to register open WIFIs which are operated by non-profits at the German Bundesnetzagentur, because this is required under German law for companies (http://is.gd/vcz2pZ) I am wondering if there are Tor nodes operated by Germans who have been registered at the Bundesnetzagentur. >From my layman’s understanding of the law this should at least be required for nodes operated by German non-profits like CCC and Torservers. I am specially interested in the case of a node which runs in a data center outside of Germany but is operated by a German non-profit. As I operate my nodes privately I am unsure if registration of my tor nodes is required. I will check with my lawyer if a registration should be done and could help to run the nodes more securely concerning law enforcement. Having information from others would help to clarify this. Thanks & regards, torland

5 12

Call for discussion: turning funding into more exit relays
by Roger Dingledine 09 Jan '13

09 Jan '13

For a few years now, funders have been asking if they can pay Tor to run more relays. I kept telling them their money was better spent on code and design improvements: https://blog.torproject.org/blog/why-tor-is-slow https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/Performance since a) network load would just grow to fill whatever new capacity we have, especially if we don't deal with the tiny fraction of users who do bulk downloads, and b) reducing diversity of relay operator control can harm anonymity. But lately the Tor network has become noticeably faster, and I think it has a lot to do with the growing amount of excess relay capacity relative to network load: https://metrics.torproject.org/network.html?graph=bandwidth&start=2010-06-0… At the same time, much of our performance improvement comes from better load balancing -- that is, concentrating traffic on the relays that can handle it better. The result though is a direct tradeoff with relay diversity: on today's network, clients choose one of the fastest 5 exit relays around 25-30% of the time, and 80% of their choices come from a pool of 40-50 relays. https://trac.torproject.org/projects/tor/ticket/6443 Since extra capacity is clearly good for performance, and since we're not doing particularly well at diversity with the current approach, we're going to try an experiment: we'll connect funding to exit relay operators so they can run bigger and/or better exit relays. If we do it right (make more faster exit relays that aren't the current biggest ones, so there are more to choose from), we will improve the network's diversity as well as being able to handle more users. We've lined up our first funder (BBG, aka http://www.voanews.com/) and they're excited to have us start as soon as we can. They want to sponsor 125+ fast exits. ---------------------------------------------------------------------- Open questions we need to decide about: 1) What exactly would we pay for? I think the right way to do it is to offer to reimburse bandwidth/hosting costs -- I don't want to get into the business of paying people to run relays, and I don't want people to be trying to figure out how to "profit". That leads to all sorts of horrible incentive structures. More broadly, we should keep in mind that the primary cost of running an exit relay is effort, not dollars: it takes dedication to find an ISP who will host it, and to hold that ISP's hand when an abuse complaint arrives. Or said another way, hosting costs are in many cases not the biggest barrier to running an exit relay. I think we should aim to constrain ourselves to talking about >=100mbit exits, assuming that turns out to give us enough choices. That said, we don't want to concentrate bandwidth too much in any given relay, so we should limit the amount we'll reimburse per relay. 2) Should we fund existing relays or new ones? The worst failure mode here would be that we screw up the current community of relay operators. That's why it's extra important to keep them involved at each step of this discussion. I think the right answer is probably a balance of reimbursing costs from current exits and encouraging new exits to appear. Before we can get more precise though, we need to get a handle on how many current fast exits there are, and what their constraints are (whether their hosting situation could give them more bandwidth, whether they're paying now or getting a deal through a friend/employer, etc). Even then, there are interesting further questions like: - Should we prefer big collectives like torservers, noisetor, CCC, dfri.se, and riseup (which can get great bulk rates on bandwidth and are big enough to have relationships with local lawyers and ISPs), or should we prefer individuals since they maximize our operator diversity? I think "explore both approaches" is a fine first plan. - For existing relays who pay for hosting, should we prefer that our money go to covering their existing costs (and then we encourage them to save their money for use, say, after this experiment finishes), or should we aim to add additional funding so the relay can use more bandwidth? I'd say it comes down to the preferences of the relay operator. That said, if we have plenty to choose from, we should pick the relays that will make the network grow -- but we should take extra care to avoid situations where operators in the first category say "well, fine" and shut down their relay. More generally, we need to consider sustainability. Our current exit relay funding is for a period of 12 months, and while there's reason to think we will find continued support, the Tor network must not end up addicted to external funding. So long as everybody is running an exit relay because they want to save the world, I think we should be fine. 4) What exactly do we mean by diversity? There's network diversity (AS / upstream network topology), organization and operator diversity, jurisdictional (country) diversity, funding diversity, data-center diversity, and more. We've started to answer some of these questions at https://trac.torproject.org/projects/tor/ticket/6232 https://blog.torproject.org/blog/research-problem-measuring-safety-tor-netw… but this research topic will need ongoing attention. I'd love to get to the point where our diversity metrics can recommend network locations that best improve the various diversity scores. 5) How much "should" an exit relay cost? Since we're aiming for diversity, we can't send all our volunteers to the same cut-rate German VPS provider. After all, much of the work in setting up an exit relay is finding a good provider that doesn't already host a bunch of Tor relays. But if we declare that we'll reimburse $50/month for 100mbit, we're going to attract a different set of volunteers -- and a different set of network locations -- than if we reimburse $100/month for 100mbit. We need to learn about current bandwidth pricing: I know there are 10 cheap hosting places that will tolerate exit relays, but are there 200? And do all of those 200 turn out to overlap diversity-wise? Initial guesses appreciated. I'm inclined toward the $100 number to give our volunteers more flexibility. If we want to reimburse on a monthly basis, how do we handle situations where the ISP wants a longer-term contract? I think the answer will come down to how many choices we have. 6) How exactly should we choose which exit relay operators to reimburse? It might be premature to speculate until we better understand what choices are available to us. But I think the answer must include doing it in a way that encourages continued growth of the relay operator _community_. People who are active in the Tor community, and well-known to many other people, should be part of the answer. At the same time, we should be willing to put some of the money into trying out new places and people, especially if they're in good locations diversity-wise. The broader answer is that we as a community need to figure out a good answer here. I definitely don't want it to be "Roger picks people in an opaque way". But I also don't want the answer to be "anybody on the Internet who offers to take our money". Maybe we should put together a consortium of current Tor activists who run fast exits? 7) How do we audit / track the sponsored relays? How should we check that your 100mbit relay is really working? What do we measure to confirm its capacity? To a first approximation I'm fine assuming that nobody is going to try to cheat (say, by colluding with an ISP to write legit-looking invoices but then just split the money). But as the plan scales, we need good ways to track statistics on how many relays are being sponsored and how much bandwidth they're providing (so funders can see how effective their money is), and what fraction of the overall network these sponsored relays are (to keep an eye on the diversity questions). 8) Legal questions? Tor exit relays raise plenty of legal questions already, especially when you consider jurisdiction variety. But reimbursing relays introduces even more excitement, such as: - Does such a relay operator end up in a different situation legally? - Does the overall Tor network change legal categories in some country, e.g. becoming a telecommunications service when it wasn't before? - Does The Tor Project Inc incur new liabilities for offering this money? Tor has a history of creating fascinating new challenges for legal scholars, and this exit relay funding experiment will be no exception. I believe if we position it correctly, we won't really change the legal context. But I encourage people to investigate these questions for their jurisdiction. ---------------------------------------------------------------------- Next steps: I'm going to do a short blog post pointing to this thread, since many interested parties aren't on tor-relays yet. Then I'll send individual emails to exit relay operators pointing them to it and asking for their feedback (on the list or private, whichever they prefer). I'll also try to get some sense of how much their hosting costs, whether they'd want to participate in our experiment, whether they're in a position to ramp up to a faster connection, etc. Once we have some concrete facts about how many current exit relays want to participate, how many new volunteers want to help, and how many ISPs could handle more exit relays and at what prices, we'll be in a better position to decide how to proceed. --Roger

25 59

Re: [tor-relays] [tor-talk] On the Theory of Remailers
by grarpamp 08 Jan '13

08 Jan '13

> It is an interesting questions, if with a modern user interface, can they > get to new life? I see no reason the state of the art from the legacy remailer types can't be combined and updated into a new service running on some of the same relay machines we have for Tor today. Even if only 10% ran them it would probably be more hosts than were ever behind the old remailer nets. And relay operators already have the abuse experience in place.

1 0