- tor-relays - lists.torproject.org

Tor relay operators meetup, 25/05/2019 @ RADIX hacklab, Athens
by Vasilis 28 May '19

28 May '19

Dear Tor friends and relay operators, Next Saturday (25.05.2019) a Tor relay operators meetup will take place at RADIX hacklab in Athens. When: Saturday, May 25th, 2019 Time: 19:00 / 7:00 PM Where: Kaniggos 34 & Stournari, Athens 10682, Greece Event link: https://radix.one/en/2019-05-18-tor-meetup/ Hope to see many of you there. Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 1

Tor Relay Operator Meeting at the Gulaschprogrammiernacht
by Christophe Kemp 28 May '19

28 May '19

Hello everyone, there will be a Tor Relay Operator Meeting at the Gulaschprogrammiernacht :) You will find soon more information here: https://entropia.de/GPN See you there! Best regards Chrëscht International Ambassador Frënn vun der Ënn A.S.B.L

1 1

VPNs and Ports
by grarpamp 25 May '19

25 May '19

>> On May 23, 2019, at 4:39 AM, Wallichii <wallichii(a)riseup.net> wrote: >> >> On Thu, 23 May 2019 04:15:36 -0500 >> Conrad Rockenhaus <conrad(a)rockenhaus.com> wrote: >> >>> I’ll be starting a free VPN service soon to allow users that are >>> blocked from using Tor at their location to access Tor. To prevent >>> abuse of the service, I plan on restricting the ability of the VPN to >>> only access 53, 80, 443, 8080, 8443, 9001, and 9030. Are there any >>> other ports I should consider keeping open for the service? >> >> IMO setting up a bridge will help more users because not everyone is >> going to trust someone on the internet giving free proxy, you should >> run a bridge if you want to help more users. That would be an input VPN... perhaps useful if DPI was breaking user's tor access protocols (to bridges or regular entry guards), but not their VPN traffic. Output VPN's could also be useful to allow tor users to bind their stack to it over tor, thus permitting UDP back and forth from clearnet... typical with voice video comms and a bunch of other applications that have been disabled for tor users becase tor only supports TCP. Operators would have to publish their VPN node info somewhere for users to use... or getbridges, getvpns. There are prior exploratory threads on this here before. Operators can also be running and supporting VPNGate.net service as both input and output.

1 0

Tor relay says it is reachable, but is not appearing on the network.
by Keifer Bly 24 May '19

24 May '19

Hi all, something very strange is going on with my relay called torworld. For some reason, the tor software is reporting that the relay is reachable and the relay is sending and receiving data (please see the attached screenshot), but after several days the relay is not appearing on the tor relay list. This seems strange and any ideas as to why this might be happening is appreciated. Thank you. running on Debian via Google Cloud VPS. Thank you. --Keifer

4 13

Scanning relays looking for onions
by Jordan 24 May '19

24 May '19

Looks like someone is making HTTP requests to known relays with a host header of an onion address. I have a webserver that returns 200 OK to all requests for honeypot-related fun and well... I can only imagine what they think my relay hosts as a result. Stay safe out there friends. 2019-05-23T02:43:58Z 5.8.10.[snip] 200 jg4rli4xoagvvmw47fr2bnnf[snip].onion / -- Jordan https://yui.cat/

1 0

new tor middle relay error
by Keifer Bly 24 May '19

24 May '19

Hi all, So I am running a new tor middle relay via a Google Cloud VPS but after the relay running for 1 day I am seeing this error May 16 18:23:50.000 [notice] Heartbeat: It seems like we are not in the cached consensus. Any thoughts on why this is happening is appreciated, thank you. --Keifer

2 2

forward relay connections
by tor-relay＠riseup.net 24 May '19

24 May '19

Hello dear friends I'm running a non exit relay on a debian machine (in the next few months I will switch to *BSD) on a Lime2. I'm running an exit relay too on a remote VM. I would turn my non-exit relay in an exit one, but for obvious reasons, I don't want to run It from my shitty ISP IP. I could give 10-14 mbps from my home connection, so I think that the lime2 would be powerful enough to run It properly. Do you think would be feasible to use SSH to forward all connections, except DNS queries, between my Lime2 and the remote VM in order to use an additional VM's IP? Could you give me some tips please? cheers Gigi

4 5

Tor relay problem
by findmei 22 May '19

22 May '19

Hi guys, I recently set up a tor relay on Centos7.But when I check the node at https://metrics.torproject.org/, i see that the relay is offline.Even though it is online.I looked tor log file. There was two common warning. May 15 14:42:13.000 [warn] Unable to stat resolver configuration in '/etc/resolv.conf': Permission denied May 15 14:49:13.000 [warn] HTTP status 307 ("Temporary Redirect") was unexpected while uploading descriptor to server '86.59.21.38:80'. Possibly the server is misconfigured? I try to chmod 777 /etc/resolv.conf for this warning " /etc/resolv.conf': Permission denied".But it didnt work it.And then i searched it on google for "HTTP status 307 ("Temporary Redirect")" .But i didn't find solution.Any suggestions? /etc/tor/torrc => https://paste.ubuntu.com/p/tD6zg2mwZy/ /var/log/tor/notices.log => https://paste.ubuntu.com/p/JsPGdgFJyT/ systemctl statust tor -l => https://paste.ubuntu.com/p/qpppzVK8qR/ Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 4

Re: [tor-relays] Trouble Running Middle Relay On Google Cloud Debian VBS
by Keifer Bly 19 May '19

19 May '19

--Keifer On Sat, May 18, 2019 at 2:28 PM Keifer Bly <keifer.bly(a)gmail.com> wrote: > I have a specified port (65534). I just tried changing the ip adress to > 35.232.92.24 <https://35.232.92.24/>, and the connection to that port is > allowed by the firewall. I will check again over the next day and see if > anything chages. It is strange the software says traffic is being received > and says " > --May 18 01:20:06.000 [notice] Self-testing indicates your ORPort is > reachable from the outside. Excellent. > May 18 01:20:08.000 [notice] Performing bandwidth self-test...done." > > So according to the software the relay is reachable and sending and > receiving traffic. Seems strange it appears unreachable to me. Wonder why > that might be. Thanks. > > > On Sat, May 18, 2019 at 1:42 PM Roman Mamedov <rm(a)romanrm.net> wrote: > >> On Wed, 15 May 2019 22:26:25 -0700 >> Keifer Bly <keifer.bly(a)gmail.com> wrote: >> >> > Hi all, >> > >> > So I am starting a new middle relay using a VPS hosted on Google Cloud >> > running Debian. though the relay is running, it is not appearing in the >> > consensus after 10 hours. Here is the tor log, any thoughts on what is >> > going on would be greatly appreciated thank you. >> >> > May 15 18:23:53.000 [notice] Now checking whether ORPort >> > 35.238.140.120:65534 is reachable... (this may take up to 20 minutes -- >> > look for log messages indicating success) >> > May 15 18:23:54.000 [notice] Self-testing indicates your ORPort is >> > reachable from the outside. Excellent. >> >> FWIW this 35.238.140.120:65534 is not reachable right now from any of my >> machines. Did you change the port or IP since then? Also, I never used a >> Google >> VPS, but it appears you need to do extra steps to ensure you get a static >> external IP: >> >> https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-… >> Did you do that? >> >> >> -- >> With respect, >> Roman >> >

1 0

Trouble Running Middle Relay On Google Cloud Debian VBS
by Keifer Bly 19 May '19

19 May '19

Hi all, So I am starting a new middle relay using a VPS hosted on Google Cloud running Debian. though the relay is running, it is not appearing in the consensus after 10 hours. Here is the tor log, any thoughts on what is going on would be greatly appreciated thank you. May 15 18:23:47.096 [notice] Opening OR listener on 0.0.0.0:65534 May 15 18:23:47.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. May 15 18:23:47.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6. May 15 18:23:47.000 [notice] Configured to measure statistics. Look for the *-stats files that will first be written to the data directory in 24 hours from now. May 15 18:23:47.000 [warn] You are running Tor as root. You don't need to, and you probably shouldn't. May 15 18:23:47.000 [notice] Your Tor server's identity key fingerprint is 'torworld 3A4E582092E7C6B822EC01F4D76F680F6C65B0A2' May 15 18:23:47.000 [notice] Bootstrapped 0%: Starting May 15 18:23:50.000 [notice] Bootstrapped 80%: Connecting to the Tor network May 15 18:23:51.000 [notice] Guessed our IP address as 35.238.140.120 (source: 193.23.244.244). May 15 18:23:52.000 [notice] Bootstrapped 85%: Finishing handshake with first hop May 15 18:23:52.000 [notice] Bootstrapped 90%: Establishing a Tor circuit May 15 18:23:53.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. May 15 18:23:53.000 [notice] Bootstrapped 100%: Done May 15 18:23:53.000 [notice] Now checking whether ORPort 35.238.140.120:65534 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) May 15 18:23:54.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. May 15 18:23:56.000 [notice] Performing bandwidth self-test...done. May 16 00:23:50.000 [notice] Heartbeat: It seems like we are not in the cached consensus. May 16 00:23:50.000 [notice] Heartbeat: Tor's uptime is 5:59 hours, with 0 circuits open. I've sent 789 kB and received 7.41 MB. May 16 00:23:50.000 [notice] Average packaged cell fullness: 100.000%. TLS write overhead: 27% May 16 00:23:50.000 [notice] Circuit handshake stats since last time: 0/0 TAP, 6/6 NTor. May 16 00:23:50.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 0 v3 connections, and 8 v4 connections; and received 1 v1 connections, 0 v2 connections, 0 v3 connections, and 6 v4 connections. May 16 00:23:50.000 [notice] DoS mitigation since startup: 0 circuits rejected, 0 marked addresses. 0 connections closed. 0 single hop clients refused. May 16 00:58:51.000 [warn] Received http status code 404 ("Not found") from server '45.62.242.212:9030' while fetching consensus directory. I also had another thing I wanted to ask. I am working on a crontab script to automatically update and restart the tor relay once a month automatically, as I am already running a bridge on another network that needs to be updated manually. Does this script look like it would get the job done? I don't have much experience with crontab. # m h dom mon dow command 0 0 1 * * apt-get update apt update && apt install -y --only-upgrade tor killall tor tor root@instance-1:/home/keifer_bly# Thank you very much. --Keifer

4 7