- tor-relays - lists.torproject.org

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

Relay consensus weight drop
by mikefloyd2 26 Jun '21

26 Jun '21

Hi, I've noticed that my relay's bandwidth has been continuously dropping during the last couple of weeks. My bandwidth has been stable during that time, and I haven't changed anything in terms of configuration. I've also noticed that bastet, longclaw and maatuska are showing lower weights for my relay. Have been any changes recently in the network that could cause this? My relay - https://metrics.torproject.org/rs.html#details/671A68ABADA1402FB00676055F48… Thanks in advance, Mike Sent with [ProtonMail](https://protonmail.com/) Secure Email.

6 11

Log message
by Zakwan Kalb 24 Jun '21

24 Jun '21

Hi, I have an issue: a day after I start my relay I get a bunch of error messages from Tor. Here is an example: http status 400 ("Fingerprint and/or ed25519 identity is marked rejected -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to bad-relays(a)lists.torproject.org mentioning your fingerprint(s)?") response from dirserver 204.13.164.118:80. Please correct. Did anyone have the same issue?

3 5

Verify my Relay
by S1l3nt Hash 24 Jun '21

24 Jun '21

Hello, I wanted to do my part in helping the TOR network grow, so I've started a tor relay on a debian system. After running for a while and monitoring on Nyx, and checking Relay Search I've notice my link says "Offline". Just wanted to know if there is a way to confirm working status, apologies in advance as I'm quite new to this. Torrc Nickname **** SocksPort 0 RunAsDaemon 1 Address xxx.xxx.xxx.xxx (static public ip) DirPort 9030 NoAdvertise DirPort xxx.xxx.xxx.xxx:9030 NoListen (static public ip) ORPort 9001 NoAdvertise ORPort xxx.xxx.xxx.xxx:9001 NoListen (static public ip) ContactInfo (my email) Log notice file /var/log/tor/notices.log ExitPolicy reject6 *:*, reject *:* RelayBandwidthRate 16777216 RelayBandwidthBurst 16777216 DisableDebuggerAttachment 0 ControlPort 9051 CookieAuthentication 1 CookieAuthFile /var/lib/tor/control_auth_cookie CookieAuthFileGroupReadable 1 DataDirectoryGroupReadable 1 HashedControlPassword *** Also configured Port Forwarding on my router for 9001 and 9030 to the private IPv4 address on the tor relay. Confirmed with my ISP no ports are being blocked. When I first started I had the confirmation MSG that DirPort could be reached, and have active incoming and outing connections. Now currently only have several outgoing connections. Was at one stage appearing "Online" on Relay Search, now "Offline" Currently have: [NOTICE] No circuits are opened. Relaxed timeout for circuit *** (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 7740 seconds] Have not configured 9001 and 9030 to open in linux, are they by default? Thanks in advance for any help and knowledge, looking forward to helping. Hash.

4 3

Bad relay mark
by Zakwan Kalb 24 Jun '21

24 Jun '21

Please email me (kalbzakwan(a)gmail.com) if your relay was marked as bad relay. There is something suspicious happening, I would like to discuss it.

1 0

Torweather is still alive or back ;-)
by lists＠for-privacy.net 21 Jun '21

21 Jun '21

Damn cool, I was surprised when I got mail from torweather.org. (Some IPv6 addresses were down and I didn't notice.) And you can adjust your delivery frequency. Relay down since 3, 12, 24, 48 Hours or 1 Week. https://github.com/thingless/torweather Hint: You must have a working mail address in torrc contact info for it. -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

1 0

tor fails on start-up after yum update
by Eddie 21 Jun '21

21 Jun '21

Running a CentOS 7.9 system, pulling tor updates from https://rpm.torproject.org/centos/$releasever/$basearch The last 2 times that tor has been yum updated, the restart of the service has just stopped, at exactly the same point: Jun 18 06:46:50.000 [notice] Tor 0.4.6.5 opening log file. Jun 18 06:46:50.830 [notice] We compiled with OpenSSL 100020bf: OpenSSL 1.0.2k 26 Jan 2017 and we are running with OpenSSL 100020bf: 1.0.2k-fips. These two versions should be binary compatible. Jun 18 06:46:50.831 [notice] Tor 0.4.6.5 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.2k-fips, Zlib 1.2.7, Liblzma 5.2.2, Libzstd 1.5.0 and Glibc 2.17 as libc. Jun 18 06:46:50.831 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Jun 18 06:46:50.831 [notice] Read configuration file "/usr/share/tor/defaults-torrc". Jun 18 06:46:50.831 [notice] Read configuration file "/etc/tor/torrc". Jun 18 06:46:50.833 [notice] Based on detected system memory, MaxMemInQueues is set to 6342 MB. You can override this by setting MaxMemInQueues by hand. Jun 18 06:46:50.833 [notice] You configured a non-loopback address '192.168.0.254:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted. Jun 18 06:46:50.833 [notice] Opening Socks listener on 192.168.0.254:9100 Jun 18 06:46:50.833 [notice] Opened Socks listener connection (ready) on 192.168.0.254:9100 Jun 18 06:46:50.833 [notice] Opening Control listener on 127.0.0.1:9051 Jun 18 06:46:50.833 [notice] Opened Control listener connection (ready) on 127.0.0.1:9051 Jun 18 06:46:50.833 [notice] Opening OR listener on 0.0.0.0:9001 Jun 18 06:46:50.834 [notice] Opened OR listener connection (ready) on 0.0.0.0:9001 Jun 18 06:46:50.834 [notice] Opening Directory listener on 0.0.0.0:9030 Jun 18 06:46:50.834 [notice] Opened Directory listener connection (ready) on 0.0.0.0:9030 Jun 18 06:46:51.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip. Starting the service then it starts correctly. I also couldn't see anything out of the ordinary in the main system logs, other than it echoing the above. Any ideas on what's going on here. Also, what is the correct setting for systemctl enable/disable tor/tor-master (I don't have any tor@ services), because I get inconsistent results using tor-master. Issuing "systemctl stop tor-master" will stop the accompanying tor instance, but "systemctl start tor-master" doesn't start it, but a "systemctl restart tor-master" does do a stop/start. I haven't had time to experiment with what happens on a re-boot (yet). Cheers.

2 1