- tor-relays - lists.torproject.org

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 23 Jul '21

23 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

Nodes on dynamic IPs don't survive an IP change any more
by Marco Predicatori 12 Jul '21

12 Jul '21

Hi, whenever my IP changes, my node stops relaying traffic, and after a few hours I see in the logs [notice] Heartbeat: It seems like we are not in the cached consensus. In past versions I remember seeing in the logs something like "...your ip seems to have changed...", followed by a new "...publishing server descriptor...", as far as I remember. Now I have to monitor my ip, and restart Tor whenever it changes. Wouldn't it be nice to go back to the previous behaviour? Bye, Marco -- https://metrics.torproject.org/rs.html#details/A4E74410D83705EEFF24BC265DE2…

1 1

(no subject)
by W H 12 Jul '21

12 Jul '21

Hello dear people I have an OBSF4 bridge to support the free internet. If I look at my bridge via https://metrics.torproject.org/ then the bridge distribution mechanism is set to HTTPS. But I would like to activate Moat. How does it work? Thank you very much

1 0

significant decrease in onionoo AS data coverage after switch to ipfire geoip db?
by nusenu 10 Jul '21

10 Jul '21

Hi, the following table shows how many relays in onionoo data have no as_name data. Since a long time the underlying DB has not been updated and there is a plan to improve things https://gitlab.torproject.org/tpo/metrics/relay-search/-/issues/40004 Now I'm wondering if this improvement made things worse? +------------+----------+ | 2021-06-10 | 419 | | 2021-06-11 | 422 | | 2021-06-12 | 422 | | 2021-06-13 | 424 | | 2021-06-14 | 421 | | 2021-06-15 | 422 | | 2021-06-16 | 420 | | 2021-06-17 | 414 | | 2021-06-18 | 1748 | kind regards, nusenu -- https://nusenu.github.io

2 2

Dotsrc.org is looking for IPv4 address space for exit nodes
by Anders Trier Olesen 07 Jul '21

07 Jul '21

Hi All! A while back, I sent an email to the tor-relays-universities mailing list, announcing that we (dotsrc.org) are attempting to run fast exit nodes on the Danish national research network: https://lists.torproject.org/pipermail/tor-relays-universities/2020-Decembe… Since then, our ISP has told us that they still don't like the idea of running an exit node on a Danish research network IP, so they'll register an AS number and request separate IPv6 addresses to dotsrc. As far as I know, it is still not possible to run IPv6 only exit nodes, which is why we're currently looking for a Provider Independent (PI) IPv4 address space that we can announce. IPv4 addresses have become a scarce resource, and are too expensive for dotsrc.org to buy on the open market. If you happen to have an unused IPv4 block (or know someone who might) that you're willing to donate or let dotsrc.org announce, please contact us at staff(a)dotsrc.org. https://dotsrc.org/news/2021-07-06_searching_for_ipv4_address_space/ Best regards Anders Trier Olesen staff(a)dotsrc.org

1 0

end of life: tor 0.4.4 (2021-06-15)
by nusenu 06 Jul '21

06 Jul '21

Reminder: tor 0.4.4 reached it's end of life on 2021-06-15. Over 1000 relays and about 20% of the network capacity runs an unsupported version of tor. https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorRele… Consider upgrading if you are one of the affected operators https://nusenu.github.io/OrNetStats/#end-of-life-relays-share -- https://nusenu.github.io

2 1

Publishing rejected fingerprints
by Trofim Maslow 03 Jul '21

03 Jul '21

Hi everyone. I think it’s a good idea to publish a list of rejected relay fingerprints and reason why they are rejected once a month. This should make Tor more transparent.

3 2

Re: [tor-relays] "Verify My Relay"
by S1l3nt Hash 29 Jun '21

29 Jun '21

Thank you for everyone's helpful input. Ive managed to get it up and running. This is the updated config I used for everyones interest. Main change was: ORPort xxx.xxx.xxx:9001 No Listen (static public ip) ------> This was removed After this, ORPort could reach external, and form connections. Address xxx.xxx.xxx.xxx (static public ip) -------> Removed AddressDisableIPv6 1 -------> Added as I'm not using IPv6 at this stage There was low performance for a few days, however i've read https://blog.torproject.org/lifecycle-new-relay and can see a steady increase in speed over the last few days. @Zakwan Kalb: My relay hasn't been marked as bad, just initial misconfig due to lack of understanding, should be all sorted now. @Georg Koppen: Not sure, but seems to be all sorted now @Toralf: Yeah i've noticed just habit i gues :D @John: Thx for the head up with ports, it helped with the fault finding!

1 0