- tor-relays - lists.torproject.org

VPS/dedi paid with bitcoin for exit node anyone?
by Monoko Satou 08 Nov '15

08 Nov '15

Hi thar, I'm looking for relatively cheap dedicated/VPS servers offers for hosting more tor exit nodes that can be paid for using Bitcoin. Minimal connection speed I'm interested in is 100mbit. I've seen some offers here and there but maybe I'm missing something. I'd like fellow node operators to share some insight on the topic. I find the infos currently available on TOR project wiki etc little bit rusty. It'd be ideal to compile an article on the topic, if people can share their experiences I'd like to donate my time for this purpose that methinks other will find helpful if one wants to host a tor relay pretty much anonymously. I for one can share a positive opinion on hosting with "Baltic Servers", an LT based company. I'm running 2 exits and 2 relays there for 31 days at the moment without many hassle (you can find 'em by looking for 'netdive' on torstatus.blutmagie.de or on Atlas). Current average net troughoutput is rx/tx 274.56 Mbit/s / 265.90 Mbit/s and the abuse e-mails are being forwarded. Cheers, -- Netdiver

4 3

(no subject)
by 海洋 08 Nov '15

08 Nov '15

2015/11/8 10:51:15.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:51:15.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:51:15.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:51:43.300 [WARN] Error parsing Bridge address 'cert=MIST1psNVCb8KwXFb7UK7qO+HgnDF7C72lXxDeVOPEJVYDl2c6OuWgW26uZ8b2qeOOFaTg' 2015/11/8 10:51:43.300 [WARN] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details. 2015/11/8 10:52:54.300 [WARN] Error parsing Bridge address 'cert=MIST1psNVCb8KwXFb7UK7qO+HgnDF7C72lXxDeVOPEJVYDl2c6OuWgW26uZ8b2qeOOFaTg' 2015/11/8 10:52:54.300 [WARN] Controller gave us config lines that didn't validate: Bridge line did not parse. See logs for details. 2015/11/8 10:53:21.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:53:21.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:53:21.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:53:21.300 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:53:28.000 [NOTICE] Bootstrapped 5%: Connecting to directory server 2015/11/8 10:53:28.000 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 2015/11/8 10:53:28.000 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 10:53:28.000 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:53:28.000 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:55:47.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:55:47.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:55:47.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:56:12.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:12.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:12.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:12.500 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:56:18.900 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 10:56:18.900 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:56:18.900 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:56:38.400 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:56:38.400 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:38.400 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:56:38.400 [NOTICE] Ignoring directory request, since no bridge nodes are available yet. 2015/11/8 10:56:38.900 [NOTICE] Delaying directory fetches: DisableNetwork is set. 2015/11/8 10:56:52.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:52.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:52.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:56:52.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:56:58.900 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:56:58.900 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 10:56:59.000 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:57:57.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 10:57:57.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 10:57:57.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 2015/11/8 10:58:05.000 [NOTICE] Opening Socks listener on 127.0.0.1:9150 2015/11/8 10:58:11.900 [WARN] Proxy Client: unable to connect to 192.210.207.126:48475 ("general SOCKS server failure") 2015/11/8 10:58:11.900 [WARN] Proxy Client: unable to connect to 194.132.209.91:38675 ("general SOCKS server failure") 2015/11/8 10:58:11.900 [WARN] Proxy Client: unable to connect to 194.132.209.161:58799 ("general SOCKS server failure") 2015/11/8 11:02:48.800 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 2015/11/8 11:02:48.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 2015/11/8 11:02:48.800 [NOTICE] Closing old Socks listener on 127.0.0.1:9150

1 0

(no subject)
by 海洋 08 Nov '15

08 Nov '15

obfs3 192.36.27.98:46121 0DEFB4F0212B8926D2F9B50E1A4149DC3F00CDC6 obfs3 194.68.32.238:44551 3C58A260CB4C5259B0214E63F384CD958934816C obfs3 54.201.127.175:40872 3DB93D8D4E1C02BA1FB6C881C18433091712A544

1 0

Tor non-exit relay - 0 circuits open
by Gergo 06 Nov '15

06 Nov '15

Hello A few days ago I started to run a Tor non-exit relay. Fingerprint: F6D5B2319748E8524478766310FD0E65F612E06A My internet connection speed 100Mbps down, 100Mbps up. (My relay runs from 16 to 18 hours a day.) But my advertised bandwidth just 66.56KB/s, and consensus weight 23 (Atlas). My relay data traffic per day just 20-30MByte. In the log heartbeat messages says 0 circuits open. What do I do wrong? Sorry for my bad english, I'm using a translator. Oberuaz

2 1

Tor Project slandered?
by Larry Brandt 06 Nov '15

06 Nov '15

Last night my wife and I caught an episode of 'NCSI New Orleans.' The plot involved a brainiac from DARPA with a congenital heart problem. His job, he reported to NCSI, was to decrypt the Tor network. He needed a new heart to finish what was almost done. He stated: "97% of all illegal internet activity occurs on the deep web". He made no distinction between deep web and Tor. This morning I fired off an email to the show producer telling him what a disservice he was doing to people worldwide who needed anonymity. Maybe some of you will join me in communicating to him. LB

3 2

Re: [tor-relays] Failure from drain-fd
by starlight.2015q3＠binnacle.cx 05 Nov '15

05 Nov '15

At 23:58 10/28/2015 -0500, starlight.2015q3(a)binnacle.cx wrote: > Log debug file logfile001 If the volume of messages is too high, you might have luck with "domain" logging, which narrows it to particular functional realms, for example: setconf Log="[edge] debug file logfile001" where the "edge" domain relates to event processing. See Log [domain,...] in https://www.torproject.org/docs/tor-manual.html.en for details and the full list of message domains.

2 1

[tor-consensus-health] Possible Sybil Attack
by starlight.2015q3＠binnacle.cx 04 Nov '15

04 Nov '15

FYI list https://lists.torproject.org/pipermail/tor-consensus-health/2015-October/00… Fri Oct 30 22:25:10 UTC 2015 Over the last hour 58 new relays have appeared. New additions are... https://lists.torproject.org/pipermail/tor-consensus-health/2015-October/00… Fri Oct 30 23:25:07 UTC 2015 Over the last hour 75 new relays have appeared. New additions are...

7 10

Re: [tor-relays] tor relay + bridge
by tinychems＠ruggedinbox.com 02 Nov '15

02 Nov '15

Thank you for your reply. Regards!

1 0

tor relay + bridge
by tinychems＠ruggedinbox.com 02 Nov '15

02 Nov '15

Hi, I have a vps acc with 2 ips. I'd like to keep one free of tor, the other is tor only. Right now I run a relay - http://torstatus.blutmagie.de/router_detail.php?FP=e6277f0036890d4ff334c65e… Is it possible to run a bridge on the same server? I assume the same ip would be a problem, but I can get practically unlimited ipv6. Can I run one on only ipv4 and the other on only ipv6? Which do you suggest for each? Regards!

2 1

DirAuths are blocking my node on Amazon EC2. Why?
by Yousif Al Saif 02 Nov '15

02 Nov '15

Dear all, I have a Tor relay running on Amazon EC2 (IP range: 52.0.0.0/11) and for sometime I am receiving the messages: http status 400 ("Authdir is rejecting routers in this range.") response from dirserver 'X.X.X.X:80'. Please correct. The router disappeared from the Tor Directory and the consensus. Its a non-exit node and there seems to be some traffic going on. Was there a particular reason for the block or was this specific to my router only? Should I consider moving to a different provider or was I specifically targeted by the block and should not attempt moving somewhere else. My details: Nickname: Yankee2 IP: 52.25.145.191 Hash: CA631DB7F8E3E00A148D2D1D0BBD1B5710888D8E Best, Yousif

3 3