June 2020 - tor-relays - lists.torproject.org

Q: Is my bridge up?
by torix＠protonmail.com 10 Jun '20

10 Jun '20

I put up a new bridge and thought things were okay; I could see outbound, sometimes inbound connections in nyx, and seemed to have some throughput in the first nyx screen. The start up log lines seem okay: "Jun 10 11:05:07.000 [notice] Bootstrapped 100% (done): Done Jun 10 11:05:07.000 [notice] Now checking whether ORPort 108.52.155.127:11340 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Jun 10 11:05:09.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jun 10 11:06:09.000 [notice] Performing bandwidth self-test...done. Jun 10 14:13:20.000 [notice] New control connection opened. Jun 10 15:33:16.000 [notice] No circuits are opened. Relaxed timeout for circuit 133 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. Jun 10 16:25:18.000 [notice] New control connection opened." And the 6hr heartbeat seems to show stuff is happening" "Jun 10 17:05:06.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 1.91 MB and received 5.84 MB." But when I use the bridge reach-ability test at https://bridges.torproject.org/scan/ It fails to find my obfs4 port. I have the two ports port-forwarded in my local router, but when I turn on ping to the router, nmap from outside sees them as filtered. Am I sending people down a black hole? Because tor does seem to be making tor connections. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 3

Anyone getting Failed to find node for hop #2 of our path. Discarding this circuit. on relays after update?
by s7r 10 Jun '20

10 Jun '20

Hello, I have upgraded Tor to 0.4.5.0-alpha-dev-20200609T194914Z-1~d9.stretch+1 yesterday and got this message on all relays and bridges after upgrade: [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [notice] Our circuit 0 (id: 4) died due to an invalid selected path, purpose Testing circuit. This may be a torrc configuration issue, or a bug. [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. ... like 10-14 more times same message ... It eventually healed by itself on some relays, and on some only after another restart of the Tor process. I am only wondering if anyone else got this. What made me want to ask this is what I somehow got it on each and every relay and bridge I did the update on. Could this be triggered by a skewed clock? The virtual machines usually start with hwclock which is usually behind (virtualbox bug) and few seconds after boot ntp takes over and corrects the time. Will keep an eye on this. Things appear to run fine after it starts. Thanks.

1 0

Help via Skype teamviewer
by Pac-Man 10 Jun '20

10 Jun '20

I have everything ready to roll with a fresh Ubuntu install all updated could I get configuration help via Skype and teamviewer? Rgds, Pac-Man Sent from ProtonMail Mobile

3 2

Limiting Tor Resources
by AceOfSpadez79 09 Jun '20

09 Jun '20

When setting up a relay, we are told that Tor doesn't scale well beyond dual core systems. So with me having a 6 core CPU, is there a way to sandbox my relay and restrict system resources to say, at most 2 cores(4 threads) and 2 gigs of RAM? Now I know simply setting up a virtual machine could solve this, however I've had no luck getting the ORPort and DirPort to reach the outside world. Probably missed something in the Tor relay or KVM(hate virtualbox btw) documentation. \-AceOfSpadez79-

3 2

key expired and can't renew
by torix＠protonmail.com 08 Jun '20

08 Jun '20

Dear LIst, My bridge, tor version 0.4.2.7 stopped this morning with a bunch of lines like this: "It looks like I should try to generate and sign a new medium-term signing key, because the one I have is going to expire soon. To do that, I'm going to have to try to load the permanent master identity key. If the master identity key was not moved or encrypted with a passphrase, this will be done automatically and no further action is required. Otherwise, provide the necessary data using 'tor --keygen' to do it manually. [warn] We needed to load a secret key from /var/db/tor/keys/ed25519_master_id_secret_key, but i t was encrypted. Try 'tor --keygen' instead, so you can enter the passphrase." I put it up a month ago, so I assume this is the frst time the key needed to be changed. When I look at the keys directory, it looks the same as my still-running one, put ip 42 days ago. 42day one: /var/db/tor # ll keys total 28 -rw------- 1 _tor _tor 64 Apr 27 01:49 ed25519_master_id_public_key -rw------- 1 _tor _tor 96 Apr 27 01:49 ed25519_master_id_secret_key -rw------- 1 _tor _tor 172 May 26 02:00 ed25519_signing_cert -rw------- 1 _tor _tor 96 May 26 02:00 ed25519_signing_secret_key -rw------- 1 _tor _tor 888 Apr 27 01:49 secret_id_key -rw------- 1 _tor _tor 888 May 25 02:03 secret_onion_key -rw------- 1 _tor _tor 96 May 25 02:03 secret_onion_key_ntor Expired one: /var/log/tor # ll /var/db/tor/keys/ total 28 -rw------- 1 _tor _tor 64 May 9 01:29 ed25519_master_id_public_key -rw------- 1 _tor _tor 227 May 9 01:29 ed25519_master_id_secret_key_encrypted -rw------- 1 _tor _tor 172 May 9 01:29 ed25519_signing_cert -rw------- 1 _tor _tor 96 May 9 01:29 ed25519_signing_secret_key -rw------- 1 _tor _tor 888 May 9 02:09 secret_id_key -rw------- 1 _tor _tor 888 May 30 21:11 secret_onion_key -rw------- 1 _tor _tor 96 May 30 21:11 secret_onion_key_ntor I have never encrypted any tor keys; I just downloaded and installed it. Permissions seem the same on both. I can delete the keys directory and reinstall tor, but that's probably a hammer to kill a gnat. Hope that this has happened many times before and it's something simple. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Tor end-of-life pre-removal notification for tor 0.4.1.x relays
by nusenu 07 Jun '20

07 Jun '20

Tor v0.4.1.x reached its end of life on 2020-05-20. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… Tor developers are preparing a patch to remove 0.4.1 relays from the Tor network. If you are one of the affected tor relay operators (listed bellow), please upgrade to a supported tor release to protect yourself and the entire network from attacks exploiting older tor versions. List of end-of-life relays (updated daily): https://nusenu.github.io/OrNetStats/eolrelays It is recommended to configure your relays to auto-update to minimize the risk of outdated software. https://community.torproject.org/relay/setup/guard/ -- https://mastodon.social/@nusenu

1 0

Unused Relay - Why?
by petrarca＠protonmail.ch 06 Jun '20

06 Jun '20

Hello all, my relay is set up to support 42 Mbps, however does not get any real traffic routed through it (605EE4375EE4C38215C8949F5808863749FD4F4A). I checked anything I could think of but everything looks fine to me. Anyone with an idea what could be wrong here? Many thanks!

3 3

Nyx questions
by G 02 Jun '20

02 Jun '20

I have a few questions involving mostly the connection information provided by Nyx. In the past I have used standalone tor as a proxy for Firefox. At times Nyx would show my internal 127.x.x.x as the 'originating' IP and other times would show my internet facing 183.x.x.x as the originating IP. I now have two Ubuntu machines with older OS versions running Tor Browser 9.5. One machine has Nyx (-i 9151) showing the internal 127.x.x.x while the other shows 24.64.x.x as the originating IP. What is the significance of these differences? On a different topic are the torrc options the same for standalone tor and tor packaged with Tor Browser? For example with Tor Browser can additional socks ports be opened and utilized (obviously while Tor Browser is active)? Thanks (sorry if this info is documented somewhere - not easily found?)

1 0

Ubuntu Focal
by Pac-Man 01 Jun '20

01 Jun '20

When will there be support for Ubuntu 20.04 LTS? There does not seem to be a repo setup where you can use focal. I have plenty of bandwidth and everything to run a really good relay, but getting any kind of help is not happening. I have reached out to the TOR Project community and have received no answer. HOW do you expect new people to become a part of the TOR network when no one is there to answer any questions? Everything on youtube is old and outdated and no one seems to want to keep any software projects going. Maybe one day I will be good enough at this to help people in realtime, but until then unless there is anyone that is willing to help me I am going to probably mothball my relay. I am sad about it but life goes on. Other projects have needs as well. Rgds, Nicholas Miller Pacman Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 3