- tor-relays - lists.torproject.org

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