- tor-relays - lists.torproject.org

Question about new log messages after 0.4.7.7 upgrade
by wardz 27 May '22

27 May '22

Been getting these syslog messages occasionally *after* the 0.4.7.7 upgrade on my bridge: -- May 26 21:00:58 torbridge Tor[ ]: Unexpected path length 4 for exit circuit 66 5, purpose 5 [3 similar message(s) suppressed in last 5400 seconds] May 26 16:26:17 torbridge kernel: [ ] TCP: eth0: Driver has suspect GRO implementation, TCP performance may be compromised. -- Anyone know what they mean and if it's something I should be worried about? Calculated advertised bandwidth seems to be about the same. For reference, im running latest Raspbian 64-bit Lite on a Raspberry 4 with latest firmware aswell. driver: bcmgenetversion: 5.15.41-v8+ Sent with [Proton Mail](https://proton.me/) secure email.

2 1

Ext Relay Operators: Please Upgrade to 0.4.7.7!
by Mike Perry 27 May '22

27 May '22

Tor 0.4.7.7-stable contains a very important performance improvement, called Congestion Control. You can read more about this improvement here: https://blog.torproject.org/congestion-contrl-047/ The TL;DR is that users of Tor 0.4.7 will experience faster performance when using Exits or Onion Services that have upgraded to 0.4.7. We have packages in available for Debian, Ubuntu, Fedora, CentOS, and BSD: - Debian: https://support.torproject.org/apt/tor-deb-repo/ - Ubuntu: https://support.torproject.org/relay-operators/operators-4/ - Fedora/CentOS: https://support.torproject.org/rpm/tor-rpm-install/ - BSD: https://lists.torproject.org/pipermail/tor-relays/2022-May/020528.html We would like to have a large fraction of Exit relays upgraded before our next Tor Browser Stable Release, on May 31st. Please let us know if you have any problems upgrading to this release. Additionally, while non-Exit relays do not need to upgrade, they will notice the effects of congestion control. All relay operators who pay for bandwidth by the gigabyte may want to consider enabling hibernation, to avoid surprise cost increases: https://support.torproject.org/relay-operators/limit-total-bandwidth/ All relays may also experience higher CPU usage. If this is a problem, rate limiting relay bandwidth will also help: https://support.torproject.org/relay-operators/bandwidth-shaping/ We also recently fixed an issue with overload reporting in 0.4.6.10 and 0.4.7.7: https://gitlab.torproject.org/tpo/core/tor/-/issues/40560 This should mean that there are far fewer false positives in the overload reporting on https://metrics.torproject.org/rs.html. If after upgrading to either of those versions, you still see overload, please see: https://support.torproject.org/relay-operators/relay-bridge-overloaded/ P.S. There is a known warn bug with vanguards-lite on first startup. It is harmless: https://gitlab.torproject.org/tpo/core/tor/-/issues/40603 -- Mike Perry

5 7

Revisit issue on incorrect time stamps on metrics
by a tor op 21 May '22

21 May '22

Hi I wrote about incorrect date stamps for relays/bridges on atlas/metrics site in December 2021. This has reappeared since some time (dont know for how long). First seen fullt incorrect by years and all times unlogic, first seen later than last restarted etc. Is this a common problem or just some relays? TIA, A tor op

2 1

Introduction
by roelquerimi 18 May '22

18 May '22

Hello the Tor relay operators. Nice to meet you. I'm Roel Querimi, I operate 9 exit relays: 0B1120660999AD1022D08664BE1AD08A77F55E50, 05757E11F488C50E3425F5F7E9319411B4270365, 5D2871217ABD67C2569C49919B46F3DFC6281D63, 983548730C7F3F52170BF2195C85D1423C33253B, 72152AE84ECF44727A9506237A93D63EAFB22B07, 7AE15D809ED86C1F2998B45985A40E7F07F078B6, 5C1B834B2E8D982B82B23D05773C78CC23BB0EB9, 3075E246EE9AAE3EECABF92A9B40A598EC77608E, 92A9547A61E21357CBA0A6E64340BCD5DF29D94F Sent with [ProtonMail](https://protonmail.com/) secure email.

1 0

Tor exit Spain
by potlatch 17 May '22

17 May '22

Hello Paul, I've run exit relays for 15-years. I put the first relay into Albania and followed with the first exit relay in Albania. I lost my two Albanian relays when the Ukraine conflict started. I currently have relays in Moldova (2), Romania, Finland (2), Chile, Estonia, Latvia, Bulgaria. Most are smaller than your server w/Consensus Weight around 8000. Further, I operate bridges in Kazahkstan (3), Finland and Albania. I would like to know a bit more before offering to take your server. Do you have good relationship with IONOS SE? What is physical machine compliment? etc.? I operate out of Seattle Washington and have good communications with the Tor office here. I am retired electrical engineer with time to help Tor and Electronic Frontier Foundation. Hope you find a good operator for your primo relay. I can be contacted directly at potlatch(a)proton.me Stay safe always,potlatch The imagination of nature is far, far greater than the imagination of man. --Richard Feynman Sent with [ProtonMail](https://protonmail.com/) secure email.

1 0

Re: [tor-relays] (No Subject) (allforprivacy)
by Isaac Grover, Aileron I.T. 12 May '22

12 May '22

Good afternoon, The Library Freedom Project is what you're seeking, for libraries: https://libraryfreedom.org/ Also, I found this response on Slashdot for hosting at a university: https://yro.slashdot.org/comments.pl?sid=7773441&cid=50227785 Make your day great, Isaac Grover

1 0

(No Subject)
by allforprivacy 12 May '22

12 May '22

Good evening, I'd like to ask: How would one go about encouraging an organization (such as a college, university or library), that they are affiliated with to some extent, to operate a Tor Exit Relay? I currently operate a Non-Exit relay at home, but I would like to also see if me and some others in my organization could start an exit relay as well (Our jurisdiction is the United Kingdom). Thank you for reading, allforprivacy operator.

1 0

OpenBSD -stable net/tor and 0.4.7.7
by George 10 May '22

10 May '22

The OpenBSD net/tor -current port is correctly on 0.4.7.7, but the -stable port is still on 0.4.6.10. I submitted a diff to update -stable port to 0.4.7.7 last week, but it has not been committed yet. https://marc.info/?l=openbsd-ports&m=165179875418235&w=2 It's attached and should work fine. In order to update the OpenBSD -stable port you need an updated -stable 7.1 ports tree, then you apply the patch within the /usr/ports/net/tor port, and build from there. I can provide more guidance if necessary, but in order to not bore everyone else, maybe the Tor-BSD list is more appropriate? https://lists.nycbug.org:8443/mailman/listinfo/tor-bsd I can send out an amd64 -stable package, but then you'd have to trust me. g

1 0

Bridge not used
by Arnim Wiezer 10 May '22

10 May '22

Hi Tor-Operators, I have installed a bridge according to the official how-to. The config is as follows: Log notice file /var/log/tor/notices.log DataDirectory /var/lib/tor Address bridge.xxx.de BridgeRelay 1 ORPort 1044 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:9043 ExtORPort auto ContactInfo arnimw(a)mailbox.org Nickname lunabridge PublishServerDescriptor 1 BridgeDistribution any Under https://metrics.torproject.org/rs.html#details/4DD98FB1959065309FD4A183530B… I see basically no usage, the logs are fine - as far as I can tell. Any help appreciated! Best, Arnim

3 4

Tor 0.4.7.7 Segmentation fault on Ubuntu 22.04 caused by "rseq"
by Xiaoqi Chen (Danny) 07 May '22

07 May '22

Dear relay operators, I recently upgraded one of my relays to Ubuntu 22.04 and now tor keeps crashing. I debugged a little bit and saw the following error in the log. It appears that it's due to seccomp not allowing "rseq" syscall, and possibly related to the latest version of Glibc. I temporarily mitigated the issue by turning off sandbox mode (remove "Sandbox 1" in torrc). Does anyone know how to properly resolve the crashing issue? Cheers, Danny Chen -- $ sudo tor -f /etc/tor/torrc May 07 02:10:46.831 [notice] Tor 0.4.7.7 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.2, Zlib 1.2.11, Liblzma 5.2.5, Libzstd 1.4.8 and Glibc 2.35 as libc. ...... May 07 02:10:46.833 [notice] Opening Directory listener on 0.0.0.0:8080 May 07 02:10:46.833 [notice] Opened Directory listener connection (ready) on 0.0.0.0:8080 Fatal glibc error: rseq registration failed ============================================================ T=Fatal glibc error: rseq registration failed 1651889448 Tor 0.4.7.7 died: Caught signal 11 Fatal glibc error: rseq registration failed Fatal glibc error: rseq registration failed tor(+0xee525)[0x55c6431d6525] /lib/x86_64-linux-gnu/libc.so.6(abort+0x178)[0x7fe6da9ee898] /lib/x86_64-linux-gnu/libc.so.6(abort+0x178)[0x7fe6da9ee898] /lib/x86_64-linux-gnu/libc.so.6(+0x8945c)[0x7fe6daa4f45c] /lib/x86_64-linux-gnu/libc.so.6(+0x89770)[0x7fe6daa4f770] /lib/x86_64-linux-gnu/libc.so.6(+0x94b31)[0x7fe6daa5ab31] /lib/x86_64-linux-gnu/libc.so.6(+0x126a00)[0x7fe6daaeca00] Fatal glibc error: rseq registration failed

4 3