tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

How to change Tor's source code
by dave` dave 29 May '18

29 May '18

I saw that i have this site https://gitweb.torproject.org/tor-browser.git which have Tor's source code, i don't understand how it works. i want to change the source code in my computer, can/how i do that?

2 1

Re: [tor-relays] Verizon AS701 blocking Tor consensus server tor26 (86.59.21.38)
by starlight.2017q4＠binnacle.cx 28 May '18

28 May '18

>Hi tor-relays mailing list, > >Good news! Verizon unblocked tor26 (86.59.21.38). > >I posted something similar on NANOG (with modifications for network people) here: >https://mailman.nanog.org/pipermail/nanog/2018-May/095386.html > >Someone nice at Verizon must have read NANOG (VZ NOC people probably do >read NANOG) and unblocked tor26. Here is a (successful) traceroute: Thank you Neel! My relay along with all the other Verizon FiOS relays are now visible to 'tor26'. This can be viewed by navigating to https://consensus-health.torproject.org/ and clicking the 'detailed page' link at the bottom (takes time to load and render). https://metrics.torproject.org/rs.html#search/as:701

2 1

Re: [tor-relays] tor-relays Digest, Vol 88, Issue 45
by Yash Kumar 27 May '18

27 May '18

Hi Olaf, Thank you for offering your help. I installed "ufw" and unblocked my ORPort, but still I am getting the same issue. Can you please suggest what else could be the problem ? Thank you, Yash On Thu, 24 May 2018 at 23:31, <tor-relays-request(a)lists.torproject.org> wrote: > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Re: Unable to confirm my ORPort is reachable (Luca Tortiglione) > 2. Re: Unable to confirm my ORPort is reachable (Matt Traudt) > 3. Re: Why adding more Nodes won't help? (teor) > 4. Re: Unable to confirm my ORPort is reachable (Olaf Grimm) > 5. Re: Tor Software Update Question (Keifer Bly) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 24 May 2018 16:56:15 +0200 > From: Luca Tortiglione <luca.tortiglione(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Unable to confirm my ORPort is reachable > Message-ID: > < > CABvHF-vHSQUGQwpp3iu_vat1gv3gRtoi2ra_ASOi6ZchGLYzQw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > what about port forwarding on the router / modem adsl ? > Il giorno gio 24 mag 2018 alle ore 16:54 Yash Kumar <yashkr.99(a)gmail.com> > ha scritto: > > > Hi all, > > I have set up a tor relay on my Ubuntu machine by following the > instructions given in the link. To confirm whether the setup was done > properly, I checked the status using the command: > > > $ sudo service tor status > > > and was getting status as "Active". > > Further, I looked into the log file /var/log/tor/notices.log using the > command: > > > $ tail -f /var/log/tor/notices.log > > > and following was the output: > > > May 24 18:24:54.000 [notice] Starting with guard context "default" > > May 24 18:24:54.000 [notice] Bootstrapped 80%: Connecting to the Tor > network > > May 24 18:24:54.000 [notice] Signaled readiness to systemd > > May 24 18:24:55.000 [notice] Guessed our IP address as x.x.x.x (source: > 204.13.164.118). > > May 24 18:24:55.000 [notice] Bootstrapped 85%: Finishing handshake with > first hop > > May 24 18:24:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit > > May 24 18:24:59.000 [notice] Tor has successfully opened a circuit. Looks > like client functionality is working. > > May 24 18:24:59.000 [notice] Bootstrapped 100%: Done > > May 24 18:24:59.000 [notice] Now checking whether ORPort x.x.x.x:9001 is > reachable... (this may take up to 20 minutes -- look for log messages > indicating success) > > May 24 18:44:55.000 [warn] Your server (x.x.x.x:9001) has not managed to > confirm that its ORPort is reachable. Relays do not publish descriptors > until their ORPort and DirPort are reachable. Please check your firewalls, > ports, address, /etc/hosts file, etc. > > > Can anyone please help me with this issue? > > I am not able to figure out the reason behind this error message "Your > server (x.x.x.x:9001) has not managed to confirm that its ORPort is > reachable". > > Please also let me know if you feel there is any issue with the tor > configuration. > > > Thank you, > > Yash Kumar > > _______________________________________________ > > tor-relays mailing list > > tor-relays(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > > -- > > > > > L. > > > ------------------------------ > > Message: 2 > Date: Thu, 24 May 2018 10:56:42 -0400 > From: Matt Traudt <pastly(a)torproject.org> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Unable to confirm my ORPort is reachable > Message-ID: <00717b22-2471-5dc5-f4d1-352a455f6e73(a)torproject.org> > Content-Type: text/plain; charset=utf-8 > > On 5/24/18 10:53, Yash Kumar wrote: > > Hi all, > > I have set up a tor relay on my Ubuntu machine by following the > > instructions given in the link > > <https://trac.torproject.org/projects/tor/wiki/TorRelayGuide>. To > > > > [...] > > > > Can anyone please help me with this issue? > > I am not able to figure out the reason behind this error message "Your > > server (x.x.x.x:9001) has not managed to confirm that its ORPort is > > reachable". > > Please also let me know if you feel there is any issue with the tor > > configuration. > > > > Based on the information provided, most likely port 9001 is not > forwarded correctly at your router. > > Matt > > > > ------------------------------ > > Message: 3 > Date: Thu, 24 May 2018 08:30:16 -0700 > From: teor <teor2345(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Why adding more Nodes won't help? > Message-ID: <1B7BFAE4-778C-4D57-9E8D-0A9E0ECA8FDE(a)gmail.com> > Content-Type: text/plain; charset="utf-8" > > > > > On 24 May 2018, at 05:00, dave` dave <daved7082(a)gmail.com> wrote: > > > > i saw that is a way to change the numbers of nodes in this site > http://thesprawl.org/research/tor-control-protocol/#creating-really-fast-on… > > any one knows how it works, there is not enough information how to use > it. > > "Since we will use the same node for both entry and exit, we must find a > node which supports appropriate exist policy" > > By default, recent Tor versions do not allow single hop exits, because the > exit learns the client's IP address and the destination domain. > > If you want this feature, run your clients and exits in a test network > with: > > RefuseUnknownExits 0 > > T >

1 0

Running A Bridge Alongside My Relay
by Keifer Bly 27 May '18

27 May '18

Hello, So I am considering running a bridge alongside my relay gotland, as the network could probably use some more bridges. As I have said, I do not have any other network that I can run my relay from, however, what I might do is run my obsfacted bridge on a Linux Virtual Machine through a proxy server. Does anyone know any free proxy software out there this might be achievable with? Let me know what you think, thank you.

4 7

New relay operator here
by privatesociety Tor 25 May '18

25 May '18

Hello tor relay community! I‘d like to introduce six new relays, which are operated by privatesociety, a community of people, which fighting for privacy based in europe. The six relays provide a capacity of around 300 mbit/s (total) and are hosted on networks, which aren‘t much used - so better for the tor community. I hope we are working great together. :) Look at meetrics for more details: https://metrics.torproject.org/rs.html#search/family:7AF3F4E88A5AE224DB7757… Anyway: We are maybe setting up an exit in the future, but for this we‘d like to join forces with other exit operators like TORSERVERS.net to have better connections in case of problems. Does anyone have contacts, which could be helpful?

4 4

Tor Software Update Question
by Keifer Bly 24 May '18

24 May '18

Hello, So I just updated the tor software using command “brew upgrade tor” on macOS. It upgraded from tor 0.3.3.0 to tor 0.3.3.6. I am wondering, do I need to restart my relay after doing this? I am also wondering, I have this email address in the “ContactInfo” in my torn file for tor project to contact me regarding issues with my relay, etc, but am wondering if there is a way to have this email for them to contact without displaying it publicly on my relay? Thank you very much.

6 11

Verizon AS701 blocking Tor consensus server tor26 (86.59.21.38)
by Neel Chauhan 24 May '18

24 May '18

Hi tor-relays mailing list, I have noticed that the Tor consensus server tor26 (https://metrics.torproject.org/rs.html#details/847B1F850344D7876491A54892F9…) is blocked on Verizon's UUNET (AS701) backbone, and therefore, Verizon's retail services like FiOS and Wireless. I can confirm this on FiOS, but I don't use Verizon Wireless (my smartphone uses Sprint) so I can't test it there. A traceroute to tor26's IP address 86.59.21.38 from a Brooklyn apartment shows this is filtered on Verizon's backbone: neel@xb2:~ % traceroute 86.59.21.38 traceroute to 86.59.21.38 (86.59.21.38), 64 hops max, 40 byte packets 1 unknown (192.168.1.1) 1.128 ms 0.780 ms 0.613 ms 2 lo0-100.NYCMNY-VFTTP-401.verizon-gni.net (173.68.77.1) 1.001 ms 3.632 ms 0.900 ms 3 B3401.NYCMNY-LCR-22.verizon-gni.net (100.41.137.96) 2.291 ms B3401.NYCMNY-LCR-21.verizon-gni.net (100.41.137.94) 3.172 ms 4.046 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * ^C neel@xb2:~ % In a normal traceroute, you will see ALTER.NET at hop 5. Also, the subnet 86.59.21.0/24 is not filtered on UUNET. A traceroute to 86.59.21.1 works: neel@xb2:~ % traceroute 86.59.21.1 traceroute to 86.59.21.1 (86.59.21.1), 64 hops max, 40 byte packets 1 unknown (192.168.1.1) 0.863 ms 0.757 ms 0.579 ms 2 lo0-100.NYCMNY-VFTTP-401.verizon-gni.net (173.68.77.1) 1.010 ms 1.545 ms 1.034 ms 3 B3401.NYCMNY-LCR-22.verizon-gni.net (100.41.137.96) 3.616 ms B3401.NYCMNY-LCR-21.verizon-gni.net (100.41.137.94) 5.696 ms 10.062 ms 4 * * * 5 0.et-5-1-5.BR3.NYC4.ALTER.NET (140.222.2.127) 3.492 ms 3.506 ms 2.996 ms 6 204.255.168.118 (204.255.168.118) 8.462 ms 7.479 ms 7.252 ms 7 144.232.4.84 (144.232.4.84) 5.041 ms 4.688 ms sl-crs3-lon-0-6-3-0.sprintlink.net (144.232.9.165) 71.865 ms 8 sl-crs2-lon-0-0-3-0.sprintlink.net (213.206.128.181) 72.214 ms 73.579 ms 72.339 ms 9 213.206.129.142 (213.206.129.142) 81.390 ms sl-crs4-ams-0-7-0-3.sprintlink.net (213.206.129.139) 85.854 ms 93.238 ms 10 217.149.47.46 (217.149.47.46) 79.004 ms 85.669 ms 79.392 ms 11 ams5-core-1.bundle-ether1.tele2.net (130.244.82.54) 86.507 ms 78.374 ms 77.740 ms 12 ams-core-2.bundle-ether9.tele2.net (130.244.82.57) 79.642 ms 77.926 ms 81.515 ms 13 wen3-core-2.bundle-ether15.tele2.net (130.244.71.47) 105.400 ms 105.089 ms 109.751 ms 14 tele2at-bundle2-vie3.net.uta.at (212.152.189.65) 122.716 ms 110.820 ms 114.354 ms 15 86.59.21.1 (86.59.21.1) 106.389 ms * 105.379 ms neel@xb2:~ % I got in contact with Peter Palfrader and he says he couldn't help, and also with Verizon FiOS support and they said the filtering 'isn't on Verizon's network' (read: isn't on Verizon's internal FiOS network but still on Verizon's AS701 which I have to go to to get anywhere on the Internet here). I know that this IP could have been blackholed, and you may think that if Verizon is blocking it, then isn't Level 3 or Cogent? Well, Cogent doesn't block tor26: traceroute to 86.59.21.38 (86.59.21.38), 30 hops max, 60 byte packets 1 gi0-1-1-19.5.agr21.jfk02.atlas.cogentco.com (66.28.3.113) 0.727 ms 0.727 ms 2 be2605.ccr41.jfk02.atlas.cogentco.com (154.54.1.153) 2.177 ms be2606.ccr42.jfk02.atlas.cogentco.com (154.54.2.29) 0.734 ms 3 be2490.ccr42.lon13.atlas.cogentco.com (154.54.42.86) 68.557 ms be2317.ccr41.lon13.atlas.cogentco.com (154.54.30.186) 70.829 ms 4 be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42) 74.570 ms be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94) 76.767 ms 5 be2434.agr21.ams03.atlas.cogentco.com (130.117.2.241) 74.515 ms 74.612 ms 6 149.6.129.250 (149.6.129.250) 80.758 ms 74.625 ms 7 ams5-core-1.bundle-ether1.tele2.net (130.244.82.54) 75.421 ms 75.425 ms 8 ams-core-2.bundle-ether9.tele2.net (130.244.82.57) 74.516 ms 74.558 ms 9 wen3-core-2.bundle-ether15.tele2.net (130.244.71.47) 97.605 ms 95.470 ms 10 tele2at-bundle2-vie3.net.uta.at (212.152.189.65) 100.314 ms 97.947 ms 11 86.59.118.145 (86.59.118.145) 96.918 ms 98.620 ms 12 tor.noreply.org (86.59.21.38) 97.853 ms 98.110 ms (Source: http://www.cogentco.com/en/network/looking-glass) It could be possible that other Tier 1 networks formerly blocked tor26, and also unblocked, but Verizon was sloppy not to do so. It's also possible that Verizon could be doing it because the FCC repealed Net Neturality, and wants to discourage use of Tor to mine FiOS/VZW customers' browsing habits. But despite a NN repeal I can still access Tor on FiOS, and also run a relay (I do both) because other consensus relays are still unblocked. But if Verizon didn't unblock tor26, could it actually mean that Verizon wants to discourage Tor (and VPN/proxy) use to try to mine information of their customers (and sell ads/information) and direct users to VZ-owned AOL and Yahoo? Well, I hope they were just sloppy and don't mean to wage war on Tor. While I'm not saying you should avoid using anything Verizon at all costs (I certainly wouldn't want to go to the local cable company), I just want to point out a blocked consensus server. Thank You, Neel Chauhan === https://www.neelc.org/

8 13

Unable to confirm my ORPort is reachable
by Yash Kumar 24 May '18

24 May '18

Hi all, I have set up a tor relay on my Ubuntu machine by following the instructions given in the link <https://trac.torproject.org/projects/tor/wiki/TorRelayGuide>. To confirm whether the setup was done properly, I checked the status using the command: $ sudo service tor status and was getting status as "Active". Further, I looked into the log file /var/log/tor/notices.log using the command: $ tail -f /var/log/tor/notices.log and following was the output: May 24 18:24:54.000 [notice] Starting with guard context "default" May 24 18:24:54.000 [notice] Bootstrapped 80%: Connecting to the Tor network May 24 18:24:54.000 [notice] Signaled readiness to systemd May 24 18:24:55.000 [notice] Guessed our IP address as x.x.x.x (source: 204.13.164.118). May 24 18:24:55.000 [notice] Bootstrapped 85%: Finishing handshake with first hop May 24 18:24:56.000 [notice] Bootstrapped 90%: Establishing a Tor circuit May 24 18:24:59.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. May 24 18:24:59.000 [notice] Bootstrapped 100%: Done May 24 18:24:59.000 [notice] Now checking whether ORPort x.x.x.x:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) May 24 18:44:55.000 [warn] Your server (x.x.x.x:9001) has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Can anyone please help me with this issue? I am not able to figure out the reason behind this error message "Your server (x.x.x.x:9001) has not managed to confirm that its ORPort is reachable". Please also let me know if you feel there is any issue with the tor configuration. Thank you, Yash Kumar

4 3

Re: [tor-relays] tor-relays Digest, Vol 88, Issue 41
by Yash Kumar 24 May '18

24 May '18

Hi Jonathan, Thank you for offering your support. Yes, you are absolutely right.The exact problem which I was facing was that, I wasn't able to find the "Self-testing" line in /var/log/syslog file. I followed the instructions as told by you and I'm mentioning their results as well below. 1. I executed the command: $ sudo systemctl status tor I got the following output: [image: tor status.jpg] 2. I checked whether there was an issue related to permissions for the command: $ cat /var/log/syslog I figured out that there wasn't any error running that command (although I'm not attaching the output of that command). I am still not getting that "Self-testing" line in /var/log/syslog, which is the problem I'm facing specifically. It would be of great help if you can think of any other possible issue because of which I am facing this problem. Thanks, Yash Kumar On Wed, 23 May 2018 at 17:30, <tor-relays-request(a)lists.torproject.org> wrote: > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > > Today's Topics: > > 1. Re: tor enters uninterruptible sleep forever when using > transparent proxy (Zack Weinberg) > 2. Setting up tor relay (Yash Kumar) > 3. Re: Setting up tor relay (Jonathan Marquardt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 22 May 2018 20:25:33 -0400 > From: Zack Weinberg <zackw(a)cmu.edu> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] tor enters uninterruptible sleep forever > when using transparent proxy > Message-ID: > <CAKCAbMgwDwAsKLf3egHAprr=Up==jmpoEd= > a_Y1iP11WXJRPVg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Tue, May 22, 2018 at 8:11 PM, Nicolás Dato <nicolas.dato(a)gmail.com> > wrote: > >> tor enters uninterruptible sleep forever when using transparent proxy > > > > For future references, the issue was the kernel version 4.4.118, > > upgraded and the problem was gone. > > A bit of Unix sysadmin lore that isn't as widely advertised as it once > was (because, thankfully, it comes up far less often than it used to): > there are only three reasons why a process would remain in an > uninterruptible sleep for more than a few milliseconds: an abnormally > slow storage peripheral (e.g. a tape drive being rewound, or a hard > drive that's about to fail), a network file server that isn't > responding to messages, or a kernel bug. > > zw > > > ------------------------------ > > Message: 2 > Date: Wed, 23 May 2018 10:48:10 +0530 > From: Yash Kumar <yashkr.99(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: [tor-relays] Setting up tor relay > Message-ID: > <CAGagdeCFKM=pw5+E5+YFn5Y9Fj3yOvq5N5R0= > C7N2kvBKLDWCQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Dear all, > I want to setup my machine as a tor relay. I am using Ubuntu 16.04 LTS on > a Intel i5 processor with 4 GB of memory. > I followed the instructions given on this link > <https://trac.torproject.org/projects/tor/wiki/TorRelayGuide>, but was > getting some issue. In one of the later steps, it says "Verify that your > relay works". This is done by checking my logfile(syslog) contains the > following text: > > "Self-testing indicates your ORPort is reachable from the outside. > Excellent. Publishing server descriptor." > > I checked the syslog by the command: > > $ cat /var/log/syslog > > > To bring it to your knowledge, I have followed all the previous steps > mentioned on that link > <https://trac.torproject.org/projects/tor/wiki/TorRelayGuide>, and was > successfully able to execute all the commands. I would request you to > please help me out in setting up my machine as a relay to make tor network > faster and more usable. > > Thank you, > Yash Kumar >

1 0

Re: [tor-relays] can dirport be disabled on fallback directory?
by teor 23 May '18

23 May '18

Hi, I didn't get your original email, it appears my spam filter is eating all your emails. (And a few other emails.) At 12:25 5/18/2018 -0400, starlight.2017q4 at binnacle.cx wrote: >Lately seeing escalating abuse traffic on the relay dirport, now up to 20k rotating source IP addresses per week. > >The simple solution is to disable dirport, but the relay is a fallback directory and I don't want to make a change that will negatively affect the relay's ability to function as such. Would >disabling dirport be a problem? All supported Tor clients use the ORPort. They won't notice if you remove the DirPort. >also: > >can a non-advertised dirport be left configured for local-system use while the public advertised dirport is disabled? This config doesn't work, and that's a bug: https://trac.torproject.org/projects/tor/ticket/26136 >does a command utility or method exist for querying dirport documents via tunnelled-dir-server? including miscellanous documents such as > >/tor/status-vote/current/consensus.z … Stem master supports ORPort endpoints in stem.descriptor.remote.Query requests: https://stem.torproject.org/change_log.html There might not be convenience functions for some of the document types you listed, so you'll need to pass their paths in the resource argument. You might also want to avoid compression locally by dropping the ".z". There don't seem to be any examples of ORPort endpoints in the Stem repository. I think Dave plans to add some more documentation as part of Tor Summer of Privacy. T

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays