- tor-relays - lists.torproject.org

KVM based virtual machine showing 4 MB/s in atlas, others showing 8-9MB/s ?
by s7r＠sky-ip.org 23 Jun '14

23 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, The same virtualization technique at different providers gives me different advertised bandwidth for relays in atlas: one provider 8-9MB/s other 3-4 MB/s The relays are all exit, having the same RAM and CPU configuration, as well as 100mbit port and unmetered traffic, they use the same Tor version, none of them are capped in any way via torrc or other means, same operating system and same virtualization technique. Why could be this difference in advertised bandwidth? Suggestions? - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 PGP Pubkey: http://www.sky-ip.org/s7r@sky-ip.org.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJTqIMAAAoJEIN/pSyBJlsRTg0IAKGweB8grMmx18rB33/xBrBC 6UAbpnUxj3tDlD+7J9SwK1jkPSvxpKEkKuwblFifJ2J1o4xoUKCvQQWLVfwP4qRI 0R6cn/Zx9pShzZ6MRRIOmuxaZjiavddqeM0/qcnwhsvGVH/6sTw80000VrLV2TMH vExzu7ofEjV1205CZ1CBAj0sOW2s+3nld7iulvttWbBoeHs2+CbRpEfQu1QPoZYu NtJ6f0vBBkenCWD/yv9Xaiwo/Ywej6jH97LIdksr9msRcDmJnbmY3VSmrlnm8n7z YFJSCFlOi3LJIB0y8QmZuowHAQcGe0Q1LmGCWU4uGgB4OHU7QRgC/jM7qffp+eQ= =+FWS -----END PGP SIGNATURE-----

1 0

Shutting down middle relays (off-topic)
by Tora Tora Tora 23 Jun '14

23 Jun '14

Regretfully, I have to shutdown my two middle relays (not too big, you won't even notice it :-D), since I am unable to resolve issues with the latest OpenSSL bug. I was able to find upgraded packages for Centos and Fedora that are supposed to address CVE-2014-0224 vulnerability (the change log claims so). However, the Tripwire )SSL_CCS_InjectTest and Qualys onlien tests both disagree. If someone can suggest a resolution that works, I might be able to keep them running, otherwise I see no point in running vulnerable relays until I figure things out. Thanks ...

7 15

CLI tool like Atlast
by Kali Tor 23 Jun '14

23 Jun '14

Hi all, Is there a CLI client/tool that does what https://atlas.torproject.org/ does? Basically provide an output based on a node's fingerprint? e.g. https://atlas.torproject.org/#details/7EDE11A41D1C7DF4F9103ABAA4F0A31E42CB0… Thanks, KaliTor

5 14

Lost hsdir flag
by kingqueen 21 Jun '14

21 Jun '14

hello, I don't know why, my relay nicknamed kingqueenbtnftw used to have the hsdir flag but now doesn't. I think from what I can gather, hsdir is based purely on the time since last boot / restart Tor service, rather than how long the relay has been up in total? That would explain it. Thanks kingqueen --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

2 2

Traffic limitation
by johhher 20 Jun '14

20 Jun '14

Hi, I'm running a Tor relay on a cheap Linux vserver with high bandwidth. I have a traffic limitation of 500Gb per month and was just wondering what would be the best configuration for the network. Currently I've limited the traffic to a daily maximum to prevent it from hibernating a long time at the end of the month. Is this the right way to do it? Or would be better to limit it on a monthly basis. Thanks for an answer! Johhher

6 5

Yahoo and AOL emails removed from tor-relays due to bounces
by Andrew Lewman 20 Jun '14

20 Jun '14

It seems Yahoo and AOL email servers have decided to refuse all messages from this tor-relays list. Other lists aren't affected, yet. We're seeing this message from Yahoo and AOL servers: "Status: 5.2.1 Remote-MTA: dns; mailin-04.mx.aol.com Diagnostic-Code: smtp; 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being refused due to provided DMARC Policy" There is no fix for this yet as it breaks mailing list software globally. This bug explains the situation, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752084 If you use yahoo or aol for email, unfortunately you can't join nor receive email from our lists. I suspect this will become true for all of our email lists soon. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982

3 2

CentOS of the air
by I 19 Jun '14

19 Jun '14

"At about 02:00 UTC June 18th 2014, changes at the domain registrar caused the CentOS.org domain to get marked as Inactive. This caused widespread outages, with all services in centos.org including: - - Mirror Network ( internal centos.org as well as external ) - - All mirrorlist - - All isolist - - Website ( including bugs.centos.org and wiki.centos.org - - All internal support infrastructure Services were restored at the registrar just before 9:00 AM UTC June 18th, however depending on dns path some users might still see issues for upto 6 to 8 hrs from that point.

1 0

tor-arm question
by Adam Griffin 19 Jun '14

19 Jun '14

Hi, Just started a new tor relay on my raspberry pi yesterday and I'm monitoring with tor-arm over ssh. I'm currently listed on atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' with > 17hrs uptime. However, tor-arm is showing a blank for uptime and about once a minute, the CLI goes blank and then flickers back. (the flickering happens at the same rate for local and remote SSH) Also, about once every couple hours I get a 'Relay unresponsive' and then 10 seconds later 'Relay resumed'. Anything to do to remedy these issues?

3 5

Help keeping Tor relay up
by Evelyne Fong 19 Jun '14

19 Jun '14

I've managed to get my relay running long enough to run the bandwidth check and have it succeed. I'll check Atlus and it'll say my relay's up and running. However when I check again about an hour later, it's saying that "Running: false". I've set up the relay recently, so I'm not expecting a lot of traffic. However, I'm confused as to if my relay is suddenly failing for no reason or is Atlus saying my relay is no longer running because there's no traffic on it. Any help would be appreciated. Thanks.

3 3

Debian relay Puppet module
by Alexander Fortin 19 Jun '14

19 Jun '14

Hi folks, I’ve recently joined the Tor Project and I have been running a non exit relay for a few days. I’m also a Puppet user and, more in general, I try to make deploying applications on the servers I administer as easy as possibile, Tor included. I think Tor documentation to install on a Debian server is quite good, but I still prefer to have Puppet doing that for me, and I’m quite sure every Puppet user out there would think the same. This is the work-in-progress version of the module I’m currently using to manage my relay: https://github.com/shaftoe/puppet-tor/tree/fixes I’m open to any feedback on how to improve it and eventually publish it to the Puppet forge (make it easier for other Puppet users to use it); maybe adding some decent disclaimer on top of the README? I can also drop the whole idea if someone convince me is a bad one... -- Alexander Fortin http://about.me/alexanderfortin

9 22

Tor-relay - IP
by Rui Branco 18 Jun '14

18 Jun '14

hello, I'm a new user of the Tor-relay and I have many doubts. Sorry about that. In the atlas project why the tor-relays ip are discovered? isn't it dangerous? -- Best Regards, Rui Branco

4 3

normal for a new relay node to be under-utilized?
by Kali Tor 18 Jun '14

18 Jun '14

Is it normal for a new relay node to carry almost no traffic even after 24 hrs? From Atlast Uptime: 1 day 8 hours 30 minutes and 28 seconds Advertised Bandwidth: 59.71 KB/s From arm Bandwidth (limit: 16 Mb/s, burst: 32 Mb/s, measured: 160.0 b/s) Upload (0.0 b/sec - avg: 738.8 b/sec, total: 10.8 MB) Download (0.0 b/sec - avg: 3.6 Kb/sec, total: 52.2 MB) torrcRelayBandwidthRate 2048 KB RelayBandwidthBurst 4096 KB AccountingMax 100 GB AccountingStart month 1 03:00 DirPort 9030

3 2

Advertised Bandwidth increasing
by kingqueen 18 Jun '14

18 Jun '14

Hi I'm running the new, imaginatively-nicknamed kingqueenbtnftw relay. I have read around a lot but something I don't get. I thought advertised bandwidth was what I'd put in torrc whereas consensus weight was what some uber-machines tested my relay at, with the idea that this can foil disruption attacks by false relays pretending to give high bandwidth. SO I expected consensus weight to gradually increase. What I didn't expect was for the advertised bandwidth to increase by step changes (as shown on atlas and globe). Evidently I've got something wrong. Could somebody please enlighten this poor nub? By the way, I appreciate that consensus weight is a dimensions number but I understand that it originated as being based on kibibytes per second? If this is still the case, it's currently significantly more than my advertised bandwidth (which is less than that set in TORRC) but appears below it in the graphs? Thanks to anyone who educates me. I have full intent on both the T-shirts on offer - the standard Tor one for uptime and bandwidth, and the EFF one for still being online in a year with over 1MBps transfer :-) Hi to all who know me Kingqueen

2 2

Operating system diversity?
by Jonathan D. Proulx 18 Jun '14

18 Jun '14

Hi All, In the recent thread relating to Debian relay Puppet modules it was suggested that a greater diversity of operating systems in tor nodes wooudl be preferable. I'm not sure if this was meant as a technical or aesthetic preference, but I am curious. Is there any technical benefit to rounning a more diverse set of opensource oprating systems for tor nodes? I discount closed source as we don't know what's going on in there. Would that present significantly different attack surfaces? I can imagine a vulnerability in the TCP stack or other kernel functionality in Linux would not be the saem in FreeBSD or vice versa... My nodes are currently Ubuntu but if there's a reason to do so I coould possibly switch OS to FreeBSD (or hurd does tor run on hurd :)) -Jon

4 3

Advertised Bandwidth increasing
by kingqueen 17 Jun '14

17 Jun '14

Hi I'm running the new, imaginatively-nicknamed kingqueenbtnftw relay. I have read around a lot but something I don't get. I thought advertised bandwidth was what I'd put in torrc whereas consensus weight was what some uber-machines tested my relay at, with the idea that this can foil disruption attacks by false relays pretending to give high bandwidth. SO I expected consensus weight to gradually increase. What I didn't expect was for the advertised bandwidth to increase by step changes (as shown on atlas and globe). Evidently I've got something wrong. Could somebody please enlighten this poor nub? By the way, I appreciate that consensus weight is a dimensions number but I understand that it originated as being based on kibibytes per second? If this is still the case, it's currently significantly more than my advertised bandwidth (which is less than that set in TORRC) but appears below it in the graphs? Thanks to anyone who educates me. I have full intent on both the T-shirts on offer - the standard Tor one for uptime and bandwidth, and the EFF one for still being online in a year with over 1MBps transfer :-) Hi to all who know me Kingqueen -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

Ops request: Deploy OpenVPN terminators
by grarpamp 17 Jun '14

17 Jun '14

Ops request: Deploy OpenVPN terminators We are ops because we want to allow people to avoid censorship and speak freely. But are we doing all we can? It is well known that all relays, exit or non-exit are added to a variety of blocklists. Primarily through scraping the consensus. And those blocklists are then used to indiscriminately deny legitimate users/people access to sites, regardless of their 'behaviour', which more often than not has simply not been determined yet. So we need to augment what we're doing in order to be effective in our mission. Here's how... We already run Tor on an IP, that IP is blackballed as noted above, so using another port on it as a vpn terminator is pointless. Yet our hosting packages often offer other IP's in the same range, or we already have them to use as part of the deal (or, failing that, we can forward the openvpn TCP port on our bad relay IP to another clean non-bulk-blocked IP we control). We obviously cannot publish this new openvpn 'exit/termination' IP anywhere, such as in the comment field of the consensus as it will be banned. *But we can bind to it and let users find it with their own openvpn scans close to (one up or down from) our OR IP.* Just use the standard openvpn TCP port on it. There is no bandwidth cost to us to do this because all the traffic is moved between the exit IP and the openvpn termination IP over localhost. (Well, unless you are forwarding openvpn port on OR IP to another termination real IP off your box.) At minimum we should allow TCP transport out from the vpn to the world, aka the usual nat, so as to make websurfing work for our users. Bonus for allowing nattable outbound UDP, ICMP, etc. Further bonus for allowing inbound binds on whatever port on the IP that is available to be bound to. Obviously sine the IP is scarce to us, we can't allow full unnatted use of the IP. The point is, we already own these extra IP's, and legitimate people are being blocked from services for no reason other than kneejerk or blind reactions to Tor via blocking services. Ahem, cloudflare, et al and other blocking 'services' well known to us. So to the extent we have other IP's available to us, we should set them up to be unpublished openvpn nodes and let users find us by trying to terminate their vpn connections on us at that IP and openvpn port. Yes, blocklists could try the 'one IP up/down' scan method and list this project of ours too, but it's more work for them and they're unlikely to do it in any sort of global fashion. Especially since they can't prove it's part of Tor (because we don't publish the IP's as such). If we wish to make an announcement that we are running such terminators, obviously it should not be made from addresses related to our OR IP's. [FWIW, there is another openvpn terminator project out there. Unlike ours would be, its nodes are public, and even with that detriment (though possibly only because it is lesser known) it obtains more freedom from blocklisting than Tor. However its termination points perform poorly/unreliably whereas ours would be both nonpublished and better managed.]

10 18

New SSL keys for new OpenSSL version?
by no.thing_to-hide＠cryptopathie.eu 16 Jun '14

16 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Tor! I run an internal Tor relay on Debian Wheezy. Today the OpenSSL version was updated to 1.0.1e-2+deb7u11 . Do I need to delete the old SSL keys like after the Heartbleed bug? Thanks and best regards Anton - -- no.thing_to-hide at cryptopathie dot eu 0x30C3CDF0, RSA 2048, 24 Mar 2014 0FF8 A811 8857 1B7E 195B 649E CC26 E1A5 30C3 CDF0 Bitmessage (no metadata): BM-2cXixKZaqzJmTfz6ojiyLzmKg2JbzDnApC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBAgAGBQJTn1hxAAoJEMwm4aUww83weJAH/jYHtjrhrFrGnVdjrKPlN/TR w9NZcvRd0GrNDbZGGwemVam+OmFdHTDEeWZ73fgb/DvrGT8Iej8hD09/vD37xn9p GYhLabsKW06j8oRz7fiVDlWVOWND8QHW+UImnwKcIlvgp9a2EaSyBGVshIGppqMW wGgc8ZhoXvo5fAe/M630PHi6e/oGDJZIilSTIDmttV8M9cTEmsxah64oHZiJqVqc ierCAlAlsbkYH7fs7/QgJw0QolnhtcIZ5ALgijT+Z4EGH5oJBFnA20lvni1qLp1T O/RUTuF8qLAUWFBLgrF1Ng5zDlyPEaVUK5SO1pM6dzvDwvSWOlrapmfCd3b07DI= =OslV -----END PGP SIGNATURE-----

2 1

Ansible repo for setting up relays
by Sam Kottler 15 Jun '14

15 Jun '14

Alexander's email about the Puppet module he's putting together has reminded me to send a mail about an ansible repository I use to manage my relays. https://github.com/skottler/tor-ansible is where it lives. Unlike the puppet module, I'm working on getting a whole environment deployment put together. Ultimately (when I get some time) I'll have it stand up all the necessary pieces to securely run (i.e. ssh configuration, user setup, etc) a relay. For now it just installs Tor. Let me know if you've got any questions. Pull requests are all welcome, of course! -s

2 1

Hash of session info was not as expected
by Logforme 14 Jun '14

14 Jun '14

My tor log file is usually quite boring but today it looks like this: Jun 14 13:42:46.000 [warn] Hash of session info was not as expected. Jun 14 13:57:56.000 [warn] Hash of session info was not as expected. Jun 14 14:11:58.000 [warn] Hash of session info was not as expected. A new line about every 10 minutes since 04:14:53 (CET) Is it a user with problems, an attack on my relay or a sign that my relay have some kind of hardware/software issues?

1 0

Torservers herngaard issues
by grarpamp 12 Jun '14

12 Jun '14

Seems to be consistently delivering random length web pages (if they are artificially slowed such as https://berlin.craigslist.org/) and its bandwidth is tanking on globe.tpo. 3B486DEC5A22694C0960B4A97A3665C617C89B1C

2 1

Sinkhole IPs to block for Cryptolocker and Gameover Zeus
by Adam Brenner 11 Jun '14

11 Jun '14

As you know, the Tor network can be used for mischievous and in some countries illegal activity hurting the reputation of Tor. Two of these activities include Cryptolocker[1] and Gameover Zeus[2]. Recently my exit node was inserted into a few block lists due to this two issues mentioned above and I would guess this hinders 'good' traffic within the Tor network using an exit node. I have complied a list of Sinkholes from CBL for both Cryptolocker and Gameover Zeus. Consider adding these IPs to your ExitPolicy reject list. ExitPolicy reject 85.159.211.119 # Cryptolocker ExitPolicy reject 212.71.250.4 # Cryptolocker ExitPolicy reject 54.83.43.69 # Cryptolocker ExitPolicy reject 192.42.116.41 # Cryptolocker ExitPolicy reject 192.42.119.41 # Cryptolocker ExitPolicy reject 198.98.103.253 # Cryptolocker ExitPolicy reject 208.64.121.161 # Cryptolocker ExitPolicy reject 142.0.36.234 # Cryptolocker ExitPolicy reject 173.193.197.194 # Cryptolocker [1]: http://www.us-cert.gov/ncas/alerts/TA13-309A [2]: https://www.us-cert.gov/ncas/alerts/TA14-150A -- Adam Brenner <adam(a)aeb.io>

2 1

Exit policies pointing to IP blocks not appearing on Globe
by Mendelson Gusmão 10 Jun '14

10 Jun '14

Hi! I just setup a tor relay, encouraged by EFF's Tor Challenge. All I have is a domestic connection. I've read my TOS and my ISP seems to be very friendly to this case. Although I have a little suspicion about traffic shaping, my exit node seems to be running very well! I'm worried about one thing, though. I remember that a while ago, when I tried to access Facebook using a tor client, I saw a message telling that I was blocked for using the network. To avoid the other users of my network to be blocked due to the traffic in my exit node, I managed to add exit policies rejecting every IP block that belongs to Facebook. However, these exit policies don't appear in neither globe.torproject.com nor any site that provides information about nodes. Are these addresses being scrubbed? How do I make sure that these policies being applied? Thanks!

4 4

Running relays at consortia networks [was: JANET/edu]
by grarpamp 09 Jun '14

09 Jun '14

On Thu, Jun 5, 2014 at 3:50 PM, Iain R. Learmonth <irl(a)fsfe.org> wrote: > I'm wondering if anyone knows anything about JANET's (the UK academic ISP) > views on running a Tor relay? > > It's probably not worth putting together a proposal for running one in a UK > University if the ISP is going to have problems with it. Has anyone tried approaching these networks themselves to see about running relays there? Their bandwidth for sponsored things is often free. In the US you might try internet2.edu and all its various connecting regional networks. On a second further approach, once all the risks and pro-reasons have been discussed and accepted, the consortia backing of many Uni's within would be bulletproof.

3 3

suspicious exit?
by JB 08 Jun '14

08 Jun '14

Hi All, FP! :) I just setup my relay node today, and am keeping a hawkish(ish) eye on traffic.... And noticed a flurry of activity from SSH port (22) at 5.104.224.5 - which is listed as an exit. But it's also listed on http://cbl.abuseat.org/lookup.cgi?ip=5.104.224.5 as infected (or NATting for a computer that is infected) with the Conficker botnet. I've black-holed it in the meantime, but am wondering if I'm being overly cautious... Any advice/response/input appreciated. TIA Jeff.

2 2

Unblocking blacklisted exits [was: suspicious]
by grarpamp 07 Jun '14

07 Jun '14

> But it's also listed on http://cbl.abuseat.org/lookup.cgi?ip=5.104.224.5 as If you find exits on blacklists, you could try to contact the operator via their descriptor contact, exit http banner, etc so that they can try to have it removed. Usually a few clicks on an assertion of ownership/cleanliness and an email ack is all that's needed for removal. Since ownership of IP's is always in flux from perspective of BL's such that any 'real' owner could always do it too, absent exit contact info, many users could probably submit removal for them without issues. There's a project covering this on the wiki: https://trac.torproject.org/projects/tor/wiki/org/projects/DontBlockMe

1 0

Tor bridges with AWS
by CD 06 Jun '14

06 Jun '14

I've signed up to AWS with Tor's instructions for bridges. I've intalled Tor on my PC. Wondering how to proceed. Am obviously an illiterate newbie, so any links for a basic knowledge-base would be greatly appreciated. Thanks in advance.

3 3

Re: [tor-relays] Update your OpenSSL, several high-risk CVEs
by Jesse Victors 06 Jun '14

06 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thanks. I saw the OpenSSL update, but thanks for explaining what it was about. Is it necessary to restart Tor to apply the update? Jesse V. On 06/06/2014 04:00 AM, tor-relays-request(a)lists.torproject.org wrote: > Message: 1 > Date: Thu, 05 Jun 2014 16:36:06 +0200 > From: Jeroen Massar <jeroen(a)massar.ch> > To: tor-relays(a)lists.torproject.org > Subject: [tor-relays] Update your OpenSSL, several high-risk CVEs > Message-ID: <53908056.50209(a)massar.ch> > Content-Type: text/plain; charset=ISO-8859-1 > > See for the details: > > https://www.openssl.org/news/secadv_20140605.txt > > Debian etc all have packages available. > > Greets, > Jeroen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQF8BAEBCgBmBQJTkdiSXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMjgyMjhENjEyODQ1OTU1NzBCMjgwRkFB RDk3MzY0RkMyMEJFQzgwAAoJEK2XNk/CC+yABpUIAJ9ZSohmGuH3r4UEg//FrYRF 3IJc6UPJx22FU0pdplN09I5L0LRzH7SehJly62niid6XNS/8bKByzjkvrnik0qRP Hjo8Rq4C/2wbRJU0w8MHvpCRLFhTRdCHdGI2+HkUaYbp7abwIZVWbTMdXB0T5lGx KvSgMeQfmlWzkwEb3WqDUqcc2NJG5D3K5WFV4WOsAi+KerBUiNyJKUqwGRd21PgS VV6S4JLQy0PVKdCAIbeEeOy2xclRfwKjBfe8RVD9b8fOmBY6ty7v1k6Org54PceA hLtJXDQXg9XQfe1u2T+peEYxf1bYIZMu+DI/7DJ0xFDr6naxJ4ttQabE2WmN6lE= =FOEn -----END PGP SIGNATURE-----

3 3

Sign up for the Tor Challenge
by Adam Brenner 05 Jun '14

05 Jun '14

If you have not already, you should consider signing up for EFF's tor challenge https://www.eff.org/torchallenge/ Today also marks the Reset the Net event https://www.resetthenet.org/ -- Adam Brenner <adam(a)aeb.io>

1 0

Update your OpenSSL, several high-risk CVEs
by Jeroen Massar 05 Jun '14

05 Jun '14

See for the details: https://www.openssl.org/news/secadv_20140605.txt Debian etc all have packages available. Greets, Jeroen

1 0

Best way for normal OS X users to run a relay?
by Roger Dingledine 05 Jun '14

05 Jun '14

What is the best way to run a relay on OS X currently? Now that the Vidalia bundles are deprecated and hard to find, I believe we have no packages or bundles for OS X other than TBB 3.x? So either "install from source, write your own init script, hope you know what ulimit -n is, good luck with that" or "install tbb3 and edit the torrc, still hope you know what ulimit -n is" are the current options? Compare with https://www.torproject.org/docs/tor-relay-debian for the Debian/Ubuntu users, where our deb takes care of a lot of these things for them. Assuming my summary is accurate, what are some good ways to move forward here? Thanks! --Roger

7 7

VPS for tor exit nodes
by Contra Band 04 Jun '14

04 Jun '14

Dear exit node operators, Could you please recommend vps providers allowing to run tor exit nodes? I checked many vps operators but most of them allow relays but not exit nodes according to AUP or ToS. thanks.

9 13

Re: [tor-relays] "as well as block BitTorrent after repeated offenses..."
by Tor Admin 03 Jun '14

03 Jun '14

Hi, I'll happily block BitTorrent it before any offenses start. Just tell me how. Regards, =-John-= <snip snip> Spencer Neitzke <spencer(a)neitzke.me> spake thusly: > as well as block BitTorrent after repeated offenses -- Using Opera's mail client: http://www.opera.com/mail/

2 1

Re: [tor-relays] VPS for tor exit nodes
by Mike Patton 03 Jun '14

03 Jun '14

I have an exit with exigent here in Australia. They advised by email that they don't have an issue with Tor. M. On 4 Jun 2014 08:56, I <beatthebastards(a)inbox.com> wrote: > > > So can you post some provider names? > > Comsitec.de is one which is ok with exits but I have a lot of trouble getting their attention when it stops. > It is in Germany which is much better than being in USA because the mentality is better. > Two I have which now say exits are not accepted are Lunanode and Bluevm. One which was expensive but good is DrServer/AbusiveCores. The guy set up Tor when I had a problem with Linux!. > > Since some have said yes to exits when I paid but a week later 'introduced a new policy' I wonder if it is worth being open. If you know what can be done with fifteen VPSs for the next nine months which can't have Tor please tell me. > > Lowendbox.com is good for scavenging addresses and sudden bargains but it may be better in the long run to pay a little more and get more cooperation. > > It may be more useful to Tor at the moment to provide bridges and for that, I believe, the very cheapest VPSs would do the job e.g. $AUD15/year. > > Robert > > > So can you post some provider names? > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

Usefulness of very limited exit policy nodes?
by Phil 31 May '14

31 May '14

Hi, Opinions please - is it worthwhile running an exit node on a home DSL connection with limited bandwidth and exit policies? I'm talking 150Mb per day, 20Kb/s, and only allowing ports 80, 443 and 53 out. I'm concerned about potential abuse from exit traffic more so than limited bandwidth. I've only had it up for a few days and the bandwidth is being used. Is such an exit policy useful for the network? Or would I be better off just running as a relay? Are there other ports that I could allow to exit that would make this node more useful, while not greatly increasing the risk of abuse reports coming my way? Phil

4 5

Running exits from home, posting exit-notice
by grarpamp 31 May '14

31 May '14

In some threads people are running exits from home for principle, economy, management, etc. Some threads question risk. Just as you put exit-relay-notice on your IP to obtain advantage of chance of reading it first before interacting with you, you may consider literally posting it on your doors. Also, even paid hosting location could have advantage from this. https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/operator-too… Btw, the link to that at the bottom of here is 404: https://www.torproject.org/docs/tor-doc-relay.html.en

2 1

Confirm IPv6 Setup as Exit Node
by Adam Brenner 30 May '14

30 May '14

Howdy, I have setup a Tor exit node and IPv4 appears to work (will get a real test in the next 48 hours). I would like to confirm my IPv6 setup as I have found the documentation on this subject lacking (or my googling skills suffering!) Added the following to my torrc file: ORPort 9001 ORPort [2606:2e00:0:19::4]:9050 # first line works with IPv4 while second line is supposed to be IPv6 IPv6Exit 1 ExitPolicy accept6 *:* # Allow all IPv6 Requests I did not specify anything for DirPort as I believe this is not working under IPv6? Is this correct? For reference my fingerprint is 6269EC22B7970ACDE4AF09F6ADE67CEB0C7F7964 -- Adam Brenner <adam(a)aeb.io>

7 9

Exit node little traffic after Named flag?
by Mike Patton 29 May '14

29 May '14

Hi all, I started running an exit node as a test, about a month ago. Initially everything was fine and traffic was good up to my throttled limit. However since my relay got given the Named flag, my traffic has been very very low. Any idea why that would be? Relay nick is NetFreedomTest2 Regards, M.

2 1

Please help profile Tor 0.2.5.4
by Moritz Bartl 27 May '14

27 May '14

Nick could use your help identifying potential bottlenecks in the 0.2.5.4-alpha release by profiling your relay. This is especially useful on high bandwidth relays (> ~50 Mbit/s). https://trac.torproject.org/projects/tor/ticket/11332 Ideally, attach your report(s) to the ticket (you can use cypherpunks/writecode as login if you don't want to create a user). Thanks! -- Moritz Bartl https://www.torservers.net/

1 0

hardening a tor relay
by Contra Band 27 May '14

27 May '14

Hi all, I'm impressed by Tor and its contribution to freedom of speech and started to run some tor relays. The first one is https://atlas.torproject.org/#details/DBE3CE33BA8BF1CB98091EE2A72690DF8218C… and I have applied tight iptables to that as below. Can somebody advise what should be add/remove to make it more efficient to tor network? =========iptables-rules.sh========== # Flushing all rules iptables -F iptables -X # Setting default filter policy iptables -P INPUT DROP iptables -P OUTPUT DROP iptables -P FORWARD DROP #ipv4 udp drop all iptables -A INPUT -p udp -j DROP iptables -A OUTPUT -p udp -j DROP #ipv6 udp drop all ip6tables -A INPUT -p udp -j DROP ip6tables -A OUTPUT -p udp -j DROP # Allow unlimited traffic on loopback iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT ip6tables -A INPUT -i lo -j ACCEPT ip6tables -A OUTPUT -o lo -j ACCEPT # Allow incoming SSH iptables -A INPUT -p tcp --dport xxx -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -p tcp --sport xxx -m state --state ESTABLISHED -j ACCEPT # Allow incoming 443 iptables -A INPUT -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT # Allow outgoing 443 iptables -A OUTPUT -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT # Allow incoming 9050 iptables -A INPUT -p tcp --dport 9050 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -p tcp --sport 9050 -m state --state ESTABLISHED -j ACCEPT # Allow outgoing 9050 iptables -A OUTPUT -p tcp --dport 9050 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -p tcp --sport 9050 -m state --state ESTABLISHED -j ACCEPT # Allow incoming 9051 iptables -A INPUT -p tcp --dport 9051 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -p tcp --sport 9051 -m state --state ESTABLISHED -j ACCEPT # Allow outgoing 9051 iptables -A OUTPUT -p tcp --dport 9051 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -p tcp --sport 9051 -m state --state ESTABLISHED -j ACCEPT # Allow incoming 9001 iptables -A INPUT -p tcp --dport 9001 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A OUTPUT -p tcp --sport 9001 -m state --state ESTABLISHED -j ACCEPT # Allow outgoing 9001 iptables -A OUTPUT -p tcp --dport 9001 -m state --state NEW,ESTABLISHED -j ACCEPT iptables -A INPUT -p tcp --sport 9001 -m state --state ESTABLISHED -j ACCEPT Thanks Simon

8 14

Non-exit abuse reports
by dope457 24 May '14

24 May '14

Hello, I have been running middle relay on my VPS since it was too much trouble to operate an exit. But ever since I have received two abuse reports regarding same issue. 1) Source: 31.31.78.141 Event type: DNSANOMALY Detail: High amount of TCP DNS traffic, whole transfer: 12 503 B Timestamp: 2014-05-14 20:20:35 NetFlow source: localhost Targets: 178.238.223.67 2) Source: 31.31.78.141 Event type: DNSANOMALY Detail: High amount of TCP DNS traffic, whole transfer: 667 644 B Timestamp: 2014-04-28 19:45:00 NetFlow source: localhost Targets: 178.238.223.67 relay - https://atlas.torproject.org/#details/F12AFDB3FEC184E76944579579F762F1142C7… ISP is pushing me to do something about it and that is why I am asking you to help me because I am not sure what to do. Thank you and have a nice weekend! dope457

3 2

Fwd: [rt.torproject.org #26011] Unknown connections
by eva 21 May '14

21 May '14

Hi all, so I'm forwading my message to your mailing list - see below. And yes, I read https://blog.torproject.org/blog/lifecycle-of-a-new-relay though. The consensus weight of my relay was 27 before, and dropped to 15. Now it's getting up again, so it might be ok. But my main question is about unknown connections. Is this a normal behaviour? Apologies, if this is already answered on another page I didn't read, unfortunately. Thank you all for developing Tor. Eva -------- Original-Nachricht -------- Betreff: [rt.torproject.org #26011] Unknown connections Datum: Tue, 20 May 2014 20:36:19 +0000 Von: Matt Pagan via RT <help(a)rt.torproject.org> Antwort an: help(a)rt.torproject.org An: unnamedabc(a)posteo.de Hi: I think you would get a better response to this question by emailing the tor-relays mailing list at tor-relays(a)lists.torproject.org. To subscribe to this mailing list, visit this page: https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays You first may want to have a read over https://blog.torproject.org/blog/lifecycle-of-a-new-relay though. On Mon May 19 18:44:00 2014, unnamedabc(a)posteo.de wrote: > Hi, > > first, thanks for your incredible work on Tor. > > I'm running a middle relay on Linux for about two months and everything > seems to be quite ok. But I'm new to Linux and to configuring a network. > So if you experts have some time to spare to help a newbie, it would be > very nice. > > For the last few days the relay traffic is only a third of it's normal > traffic. And I wonder if I should worry about some inbound and > outbound connections called 'unknown'. Arm shows something like this > > outbound > address: 0.0.0.0 > locale: ?? > No consensus data found > > inbound > address: 166.84.7.148 > locale: ?? > No consensus data found > > Could that be a problem? > > The relay fingerprint is 12AAE898482C1B7CB9ED91A3D7F6EF81D2149178 > > Thanks, > Eva -- - - - - - - - - - - - - - - - - - - - - - - - Help make more Tor-- Support the Tor Project! https://www.torproject.org/donate/donate.html

1 0

Sorry for my molestation
by zwiebel＠quantentunnel.de 19 May '14

19 May '14

I will keep calm next days ... > Gesendet: Montag, 19. Mai 2014 um 18:19 Uhr > Von: "Peter Palfrader" <weasel(a)torproject.org> > An: zwiebel(a)quantentunnel.de > Cc: "Tor Assistants" <tor-assistants(a)lists.torproject.org> > Betreff: Your tor-relays postings (was: [tor-relays] relay not receiving very much traffic) > > Hey, > > you have been posting to tor-relays quite a bit recently. > > zwiebel(a)quantentunnel.de schrieb am Montag, dem 19. Mai 2014: > > > torrc looks good in my eyes. > [..] > > Please don't top-post, and please send text-only mail instead of HTML > mail. > > Thanks, > weasel > -- > | .''`. ** Debian ** > Peter Palfrader | : :' : The universal > http://www.palfrader.org/ | `. `' Operating System > | `- http://www.debian.org/ >

1 0

relay not receiving very much traffic
by Markus Klock 19 May '14

19 May '14

Hello!I deployed a new tor-relay about 2 months ago. It runs on a server with 2 Quad-cores, 8GB RAM and 1Gbit connection.However, I have still not received very much traffic to it, it almost never goes above 10Mbit.This is the server traffic the last 2 months:http://best-practice.se/dump/tor-ralay.PNG Is this normal or may I have configured something wrong?Last time I had a relay running I received 100Mbit+ traffic... Markus

5 11

Advertised Bandwidth
by Spencer Neitzke 19 May '14

19 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, My advertised bandwidth is much slower than what it should actually be. I am running on a network that easily achieves 2gbps, although atlas is reporting 4.15mb/s. Have I misconfigured something? Nickname - ServerX5690 -----BEGIN PGP SIGNATURE----- Version: OpenPGP.js v0.5.1 Comment: http://openpgpjs.org wsBcBAEBCAAQBQJTeZXmCRAgZfyIs5JzlAAABhkH/0GeOwtqo1sE5aT7jQVT taaOKZmJiIgDfBA0KQZdq8WLAkT2V61wiOHcWf6PXIouvY/Tt3n+aWs85v4n cs5Rahj83MYZArKIm9wQ34hEkYu6Fku9HVIVZBWpPcFC6aZgKDk9xgKo4qO1 +OjxsoE8liY0WYVr9BabWKsN3+kiwWDQUk/Et48xPk6YyFJLj0Bjqa951SQf J7lTjitrfxYqPn6GHiz9njhO/szHOP24aLJR5jIagBbGJzlxeQ686C4ptDVM DuZjeTqmN6ZmVWZv5M44FdJknfUigRnUerWVBjfrVuHGU5pnSVf6owSduOX4 U+kK3PlbOrk+0zfQiyJBeuU= =A0nS -----END PGP SIGNATURE-----

3 4

Re: [tor-relays] relay not receiving very much traffic
by Markus Klock 18 May '14

18 May '14

Well, I *am* the network admin :) This server is directly connected to our backbone and is not being throttled in any way. AS1653 is our upstream and they like the Tor-project, no throttles there either :) How often does tor/atlas mesure bandwith? /Markus ________________________________ Från: zwiebel(a)quantentunnel.de<mailto:zwiebel@quantentunnel.de> Skickat: ‎2014-‎05-‎18 23:11 Till: tor-relays(a)lists.torproject.org<mailto:tor-relays@lists.torproject.org> Ämne: Re: [tor-relays] relay not receiving very much traffic _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

3 2

Re: [tor-relays] relay not receiving very much traffic
by Markus Klock 18 May '14

18 May '14

Yeah, I have no problem pushing 850Mbit and more via iperf and wget from speedtest-servers. /Markus ________________________________ Från: zwiebel(a)quantentunnel.de<mailto:zwiebel@quantentunnel.de> Skickat: ‎2014-‎05-‎18 22:11 Till: tor-relays(a)lists.torproject.org<mailto:tor-relays@lists.torproject.org> Ämne: Re: [tor-relays] relay not receiving very much traffic _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

One server, Two open tor connections
by Kurt Besig 18 May '14

18 May '14

Hi all, I'm currently running a Linux relay on one LAN machine. I recently set-up a dual boot win7/Ubuntu 14.04 LTS machine, also on the LAN. For now I'd just like to browse the tor network on the second machine and not run a relay on it for the present. I'm concerned my ISP might give me problems if my bandwidth gets too crazy. So, other than editing my /etc/tor/torrc to open a control port and forwarding the control port, is there anything else required to simply browse tor? When I installed tor on the second machine's Ubuntu install I added the tor repositories to my sources.list and updated, upgraded, and installed tor though apt-get.

3 2

DigitalOcean starting Exit node crackdown
by Shawn Nock 15 May '14

15 May '14

Hello friends, As I recall, there are several exits running on DigitalOcean's infrastructure. This is presented FYI: Background: I've run an exit on DigitalOcean for about a year without issues (lost track of uptime duing heartbleed key regen). It wasn't hidden (the droplet name was 'tor-exit') and it had valid reverse DNS and the standard informational page was hosted there. At the time of droplet creation, tor exits were not prohibited by their ToS. I've mentioned to DigitalOcean staff during support tickets that it was a Tor exit. Today the exit was shutdown, the message received was this: >Hello > >We do see that you are running an exit node for the TOR network. > >Unfortunately we are unable to resume services to this droplet and ask >you that you please not run any other TOR exit nodes. > >Please get back to us as soon as possible so we can resolve this. > >Thanks >Support I sent the following response: >Hello, > >My droplet has been running for months (perhaps a year) with no >significant incidents. It is well managed, allows only a strict subset >of traffic to exit and the very few complaints that have been lodged >have been dealt with quickly and professionally (as said by your >support team). The droplet has been configured to limit the rate of >traffic below the droplet's monthly network transfer quota. > >It's well established that under US law ISPs are excluded from >liability under the safe-harbour provisions of the DCMA for any >copyright infringing traffic. More generally, the probability under US >law that an ISP would be held liable carrying user-generated traffic is >extremely low. Tor exits have been operated by Universities, Churches, >and corporations (large and small) for slightly more that 10 >years. During this time not a single criminal or civil complaint has >been brought against an operator's ISP (to my knowledge). > >While it is surely your right to operate your business in the manner of >your choosing; I politely request an explanation for your apparent >policy against Tor exit nodes. If there is some way I might change the >parameters of the exit to suit a policy against specific traffic (to >certain IP blocks, port ranges); I'd surely comply. > >Finally, in this time where repressive regimes are cracking down on >Internet traffic and persecuting their countrymen and where free access >to the internet is nearing the stature of 'human right': if your policy >is indeed a general one against all Tor exits, I urge you to reconsider >your policy. It would be a great service to tens-of-thousands of Tor >users (refugees, political activists, religious minority, abused >spouses, law enforcement, &c) to revise your policy to allow >well-maintained exits to remain on your network. > >I appreciate any attention you could give to this serious matter. -- nock(a)aphr.asia (OpenPGP: 0x6FDA11EE 3BC412E3)

5 7

Malicious or crappily configured exit node
by u 15 May '14

15 May '14

Hello! referring to https://trac.torproject.org/projects/tor/wiki/doc/badRelays, i sent this also to tor-assistances@tpo. Never got an answer though :( Now and then, I use Icedove with TorBirdy under Debian. While connecting to port 465 on my usual mailserver, using SSL, I sometimes get an SSL certificate alert. The certificate presented is not my usual certificate at all (which works without adding an exception), but one for cab.cabinethardwareparts.com, pretending to be my mailserver. [1] I've searched a bit for information on that exit node and found: http://torstatus.rueckgr.at/router_detail.php?FP=0cc9b8aa649881c39e948e70b6… This node has flags: fast, stable, guard... I tried it several times and the behaviour was repeatedly the same. Last time it happened was 10 days ago. Then again today. I'm not quite sure where to report this (that is how this e-mail ends up on tor-relays :) ), nor how to avoid this exit node. Is there a way to do that? Thanks, u. [1] http://pix.toile-libre.org/upload/original/1399232278.png screenshot of the certificate

5 6

Re: [tor-relays] How to handle an abuse report
by tor＠t-3.net 15 May '14

15 May '14

Does the user appear to be bypassing attempts to block/ban him from the site/chat in question? If not, depending upon what you are looking at, one possible response is along the lines of: This is 2-way participation in an internet chat forum by 2 users who are at odds with one another. The quoted content may be ugly, but it does not appear to qualify as site or network abuse. Ch'Gans wrote: >Everything went well so far, until today. Someone, let's call this >person/group "A", reported an abuse to Hetzner. A TOR User, "B", is >spamming chat/forums with vociferous insults and disrespectful messages, >I got a copy of few of them and the insults from B are as bad as the >ideas defended by A, but I'm not here to judge anyone...

1 0