- tor-relays - lists.torproject.org

Exit relay seized by police
by Kevin Beranek 10 Nov '15

10 Nov '15

Is there a procedure I should follow if a relay has been seized by the police? Do DirAuths typically do something in cases where a relay is seized? I just got a message from NQHost stating that "We have received several police inquires and court order to seize your VPS. ". This affects relay A1E0245862C707F977DF0EC79257C49CD5DA99FE. Thanks, Kevin

10 21

interpreting extra-infos
by eliaz 09 Nov '15

09 Nov '15

Can anyone point me to a tutorial about how to read the extra-info output of CollecTor? I'm particularly interested in what bridge-ip-versions v4=0,v6=0 means and why bridge-ip-transports does not report the the pluggable transport proxies (obfs3, obfs4, etc.) for the bridge I'm running.

2 1

Wrong IP from faravahar again
by Pascal Terjan 09 Nov '15

09 Nov '15

Nov 04 17:06:00.000 [notice] Our IP Address has changed from 149.18.2.82 to 154.35.32.5; rebuilding descriptor (source: 154.35.175.225). Nov 04 17:08:55.000 [notice] Our IP Address has changed from 154.35.32.5 to 149.18.2.82; rebuilding descriptor (source: 154.35.175.225). 5.32.35.154.in-addr.arpa domain name pointer faravahar.rabbani.jp.

2 1

Faravahar messing with my IP address
by Logforme 09 Nov '15

09 Nov '15

I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34) Saw this in yesterday's log file: Oct 22 03:17:55.000 [notice] Our IP Address has changed from 84.219.173.60 to 154.35.32.5; rebuilding descriptor (source: 154.35.175.225). Oct 22 03:17:55.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Oct 22 03:17:56.000 [notice] Performing bandwidth self-test...done. Oct 22 03:26:55.000 [notice] Our IP Address has changed from 154.35.32.5 to 84.219.173.60; rebuilding descriptor (source: 194.109.206.212). 84.219.173.60: <- My real IP address 154.35.32.5: faravahar.rabbani.jp <- No idea 154.35.175.225: faravahar.redteam.net <- Authority server 194.109.206.212: tor.dizum.com <- Better authority server So if I read it right my relay asked the authority server Faravahar what my IP address is and got the wrong answer. 9 minutes later my relay asked another authority server and got the right answer. My relay show an uptime starting from this time and if the relay did a full restart it meant all the circuits got dropped? Inconvenient for users. My relay have "restarted" like this a few times the last weeks (only Tor daemon "restarting", not the machine). Don't know if Faravahar is behind the other "restarts". This time I just caught it in the log file before it got archived. Is this a know issue with Faravahar? If so, should it be fixed?

7 7

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 海洋 07 Nov '15

07 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 海洋 07 Nov '15

07 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 05 Nov '15

05 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 04 Nov '15

04 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