- tor-relays - lists.torproject.org

FallbackDirectoryMirrors relay IP change
by Cristian Consonni 04 Aug '21

04 Aug '21

Hi, After 7+ years of running a relay on DigitalOcean, I have decided to move it somewhere else, as there are cheaper options. I kept the same keys and fingerprint and it seems that it has been picked up correctly on Atlas/Tor metrics, as it is showing with the new IP. I believe that this relay was listed as a fallback directory mirror - how can I check this? According to the doc[1] I should open a ticket to signal the change or write here. The link[2] for opening the ticket seems broken, so here I am. Also, I am wondering if I should have done this *before* moving the relay, if that's the case I think it could be worth putting a note in the FAQ about upgrading/moving a node[3]. Best, Cristian [1]: https://gitlab.torproject.org/legacy/trac/-/wikis/doc/FallbackDirectoryMirr… [2]: https://trac.torproject.org/projects/tor/newticket?keywords=fallback-change… [3]: https://2019.www.torproject.org/docs/faq.html.en#UpgradeOrMove

2 1

Is my node dropping packets?
by Marco Predicatori 02 Aug '21

02 Aug '21

Hi, my Tor node is inside a local network protected by a firewall. Only port 9001 is NATted towards the Tor server. Moreover, I have iptables active on the Tor server itself. The outer firewall blocks any incoming packet except for packets on port 9001 and returning packets from established connections. My iptables blocks several packets which were allowed through by the outer firewall, where I assume they are recognized as returning packets from established connections. Then my local iptables drops them. I can't understand why. You can find here an extract from my Tor node "iptables -L -n" and a typical day's log of dropped packets on the Tor node: https://easyupload.io/m/48if5l Many packets coming from other Tor nodes where dropped. The Tor log doesn't mention any problem. What may be wrong? -- Bye, Marco https://metrics.torproject.org/rs.html#details/A4E74410D83705EEFF24BC265DE2…

2 2

Question about Tor updates
by potlatch 31 Jul '21

31 Jul '21

Hello Tor people, I have several Tor relays in a developing country so I suspect their VPS and network expertise may be developing as well. When I update my ubuntu 20.04.2 LTS (Focal Fossa) I get the following message: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://deb.torproject.org/torproject.org focal InRelease' doesn't support architecture 'i386' Everything else updates fine. The cpus are AMD Ryzen 5 6-core. I see cpus as 32-bit and 64-bit. The installation has been working for over 1-year. Did I install the wrong Tor? (It's 0.4.5.9) Is there a soft/hardware conflict? --potlatch Sent with [ProtonMail](https://protonmail.com/) Secure Email.

2 1

My Family
by Kathi 29 Jul '21

29 Jul '21

Hi - I'm running three relays. Is it necessary to list all three relays in my family on each relay? Thank you! :-)

5 5

Relay Bandwidth/Burst Change
by Kathi 29 Jul '21

29 Jul '21

I set torrc bandwidth/Burst to 5 MBs/6MBs respectively Then I get @7pm Local: Received reload signal (hup). Reloading config and resetting internal state. Read configuration file "/usr/share/tor/tor-service-defaults-torrc". Read configuration file "/etc/tor/torrc". After the above happens I'm back to Kb second. If I understand correctly, torrc is the 'go to' default and those settings [*should be*] used. So why is the bandwidth/Burst being changed? Which is REALLY annoying. There must be another setting somewhere in Tor that I am missing? Thank you for your help!

2 1

Updates to Tor Bridge?
by doTheRightThing655＠protonmail.com 28 Jul '21

28 Jul '21

Hello everyone, I recently started running a Tor Bridge on my Windows 10 PC. How do I update it? Does updating the Tor Browser app update my Bridge? Or is there a method to doing this? Thanks! Sent from ProtonMail

3 2

Relay appears to be broken
by Sarah Alston 28 Jul '21

28 Jul '21

Hi, I just setup a relay on some spare hardware I had around, but it doesn't appear to be functioning properly. It bootstraps fine, and the WAN ports are open. Additionally, the relay doesn't appear to be listed in the relay directory, either.However, the only connections appear to be to directory authorities, and for the life of me I can't work out what the issue is. This is the log from tor systemd service: https://pastebin.com/KsyNnBBq If anyone could help, it would be greatly appreciated.

1 0

relayor v21.0.1 is released
by nusenu 25 Jul '21

25 Jul '21

Hi, relayor v21.0.1 is released. relayor is an ansible [1] role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor [1] https://www.ansible.com/ changes since relayor v21.0.0 * install the gpg package by default on debian based systems (patch by @ anadahz) * reload tor when the tor-exit-notice html file is changed (patch by @ anadahz) https://github.com/nusenu/ansible-relayor/releases/tag/v21.0.1 kind regards, nusenu -- https://nusenu.github.io

1 0

APPCRASH on Windows Server Core 2019
by Saswat Padhi 22 Jul '21

22 Jul '21

Hello, I recently switched to a Windows Server Core 2019 machine for running my (exit) relay. Previously I was able to run the relay without any issues on Windows Server 2019, but it crashes without any errors or warnings on Core 2019. Has anyone tried running a Tor relay on Windows Server Core? I have attached my notice.log file and the error report from Windows events log, but none of them have anything informative at all. What I see is very similar to what's described on this thread: https://lists.torproject.org/pipermail/tor-relays/2021-April/019597.html. OP was finally able to resolve it, but they didn't post their solution ... Thanks and regards.

1 0

OVH killed me
by gerard＠bulger.co.uk 17 Jul '21

17 Jul '21

I have had no reports of abuse with my partial exit for a couple of years, then suddenly OVH kills the server (Reinstalling is a pain and IPV6 not autoloaded and they and Ubuntu keep changing networking) Anyway “Abnormal activity has been detected on your VPS vps585081.ovh.net. As your VPS poses too greater threat to our infrastructure, we had no choice but to put it in FTP rescue mode. This mode enables you to access the data on your VPS. An email containing information on FTP rescue mode has been sent to you. Actions can no longer be carried out on your VPS via your Manager/API. Only the following actions are possible: - Reinstallation of your VPS. Please do not hesitate to contact our technical support team so that this situation does not become critical. You will find the logs brought up by our system below, which led to this alert. - START OF ADDITIONAL INFORMATION - Attack detail : 7Kpps/3Mbps dateTime srcIp:srcPort dstIp:dstPort protocol flags bytes reason 2021.07.17 15:44:37 CEST 51.38.64.xxx:39859 192.124.249.xx:443 TCP SYN 60 ATTACK:TCP_SYN 2021.07.17 15:44:37 CEST 51.38.64.xxx:38510 67.222.30.xx:443 TCP SYN 60 ATTACK:TCP_SYN 2021.07.17 15:44:37 CEST 51.38.64.xxx :43014 67.222.30.xx:443 TCP SYN 60 ATTACK:TCP_SYN When I fire it up how to mitigate against this? My new server with the original IPV4 address is under attack already but tor is not running yet Gerry

1 0