- tor-relays - lists.torproject.org

Considering running a relay on AWS Free tier
by Keifer Bly 29 Nov '22

29 Nov '22

Hi, So I don't know if I will do it, but I am considering setting up a tor middle relay on AWS free tier. I have been asking their support tem regarding how much traffic one can push and remain free tier, their response was: If your microservice application is using an RDS or Amazon DynamoDB Accelerator (DAX) database, the Lambda-to-database traffic will be free if it’s in the same region, including if VPC peering is used. Traffic to databases in a different region will incur a regional transfer fee of $0.09 per GB for both the Lambda and database egress traffic. Ingress traffic is free for both.\" I am wondering does anyone else run tor middle relays on AWS free tier, and what is the best torrc configuration to use for keeping the inbound and outbound traffic in free tier in case I do go fourth with this? Thanks. --Keifer

2 1

Next Tor relay operator - November 19th at 19.00 UTC
by gus 23 Nov '22

23 Nov '22

Dear relay operators, The next Tor relay operator meetup will happen on Saturday, November 19th at 19.00 UTC. ## Where BigBlueButton: https://tor.meet.coop/gus-og0-x74-dzn ## Agenda (WIP) - Announcements - State of DoS attack - Q&A - Next Tor Relay Operator Meetup Meeting pad: - https://pad.riseup.net/p/tor-relay-op-meetup-n19-keep - http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor… Everyone is free to bring up additional questions or topics at the meeting itself. ## Registration No need for a registration or anything else, just use the room-link above. We will open the room 10 minutes before so you can test your mic setup. Please share with your friends, social media and other mailing lists! cheers, Gus -- The Tor Project Community Team Lead

1 1

Re: [tor-relays] preventing DDoS is more than just network filtering
by Toralf Förster 15 Nov '22

15 Nov '22

On 11/8/22 10:57, Chris wrote: > The main reason is that a simple SYN flood can quickly fill up your > conntrack table and then legitimate packets are quietly dropped and you > won't see any problems thinking everything is perfect with your server > unless you dig into your system logs. Hhm, my system log doesn't show any problems, maybe due to (or regardless of?): CONFIG_SYN_COOKIES=y ? Nevertheless, I updated the Readme to explain my point of view [1] [2]. [1] https://github.com/toralf/torutils#block-ddos-traffic [2] https://github.com/toralf/torutils#rule-set -- Toralf

3 3

Tor Relay on Gandi.net
by protectmyonion 14 Nov '22

14 Nov '22

mailto:tor-relays@lists.torproject.org I was wondering if anyone had experience running a Tor relay on Gandi. According to [good-bad-isps](https://community.torproject.org/relay/community-resources/g…, Gandi supports all relays. However, I contacted support asking them their policy on Tor and if their policy was the same for all Tor relays. Their response was basically 'You can install any software you want, but its use is subject to French law and our terms of service. If a complaint is received, the Abuse department will take appropriate action and notify you.'. This was pretty vague and kind of seemed like they didn't know what Tor was. I responded and tried to explain what Tor was using most of what was in the Common Boilerplate template. I explained that there were things that I could do to reduce potential abuse, like limiting the exit policy, but that there was always still potential for abuse. The next response came from the Abuse department and basically said 'Any illegal activity on your IP will result in your server being shutdown.'. Based on this, it seems like Gandi is not a good ISP for Tor exits, but likely fine for all other relays. What's a little confusing is that according to Tor metrics, Gandi currently has Tor exits. It is only 2, but nevertheless, they exist. [France](https://metrics.torproject.org/rs.html#search/as:AS203476) location has 2 exits, but [Luxembourg](https://metrics.torproject.org/rs.html#search/as:AS29169) has none. I'm not sure if [good-bad-isps](https://community.torproject.org/relay/community-resources/g… should be updated, given there's conflicting information, but I figured I'd ask if anyone had personal experience with Gandi. Thanks.

3 2

new bridge
by Anonforpeace 10 Nov '22

10 Nov '22

Hello: I have setup a new bridge. Relay Search confirms it is up, however I wanted to verify with you as well. The nickname is: h4ck3rspace Thank you Sent with [Proton Mail](https://proton.me/) secure email.

1 0

Tor DDoS Mitigation iptables scripts updated to version 3.0.0
by Chris 09 Nov '22

09 Nov '22

1 0

Middle relay and snowflake
by andrew reid 08 Nov '22

08 Nov '22

Is it possible to run a tor relay and a snowflake on the same IP. I have had the snowflake add on installed on my browser for a few months and noticed it has never gotten any traffic. Is this because of the tor relay on the same IP ?

1 0

State of the Onion 2022
by Gaba 08 Nov '22

08 Nov '22

Hi! We're happy to announce that the State of the Onion, a livestream event highlighting updates from onion-world over the last year, is returning this month! This year, we'll State of the Onion will be a two-part event: - Wednesday, Nov 9, State of the Onion: the Tor Project @ 17:00-18:30 UTC: https://www.youtube.com/watch?v=uSyBZ7GIzJY - Wednesday, Nov 16, State of the Onion: the Tor community @ 17:00-18:30 UTC: https://www.youtube.com/watch?v=O-7k0PjnBbk Everyone is invited to hear news, accomplishments, challenges, and next steps of all the Tor Project's teams + Tor community projects during these live events. More information about the Tor Project's event in https://blog.torproject.org/state-of-the-onion-2022/ cheers, gaba -- pronouns she/her/they GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

preventing DDoS is more than just network filtering
by Toralf Förster 07 Nov '22

07 Nov '22

The graphs in [1] and [2] are IMO good examples related to [3]: "... in addition to network filtering, the (currently) sharp input signal ... is transformed into a smeared output response ... This shall make it harder for an attacker to gather infromation using time correlation techniques." Feedback is welcome. [1] https://github.com/toralf/torutils/blob/main/doc/network-metric.svg [2] https://github.com/toralf/torutils/blob/main/doc/network-metric-nextday.svg [3] https://github.com/toralf/torutils/tree/main#block-ddos-traffic -- Toralf

1 0

Need a little assistance with a relay
by Ronvau 05 Nov '22

05 Nov '22

Hello Tor, I am looking to set up a relay but have not been successful yet. ALthough I believe I followed instructions, the relay "Walton" does not appear to be functioning as I would expect. I was using SNAP as a vehicle to launch the relay but no luck there as it fails as well. Is there anyone that can work with me to get this relay up and online?? Thank you.Ron V.

3 3

Re: [tor-relays] security update for obfs4proxy
by Toralf Förster 03 Nov '22

03 Nov '22

On 10/14/22 19:09, meskio wrote: > The upstream changelog is here: > https://gitlab.com/yawning/obfs4/-/blob/master/ChangeLog > But I understand is not easy to understand what the problem is from that > changelog. Indeed. BTW the fix was made 5 weeks ago, so I do assume, the (eg. Debian) package needed time to stabilize, or ? -- Toralf

3 3

My bridge has no distribution mechanism
by Keifer Bly 30 Oct '22

30 Oct '22

https://metrics.torproject.org/rs.html#details/4D6E3CA2110FC36D3106C86940A1… Hey, So my bridge, listed above, says it has no distribution mechanism. Does this mean it is not currently being used? Thank you. --Keifer

1 0

DoS attacks -- status update
by Georg Koppen 28 Oct '22

28 Oct '22

Hello everyone! It's been a while since we last provided some update on this mailing list about our ongoing work fighting several DoS attacks. We can use the attached graph about detected overload over the last couple of months to show what is going on and what we do/plan to do about it. The first noteworthy incident on that graph is the sharp rise in overloaded non-exit nodes since the middle of July caused by a drop of onionskins[1] which the relay's available CPU/memory can't handle anymore. There are currently two ideas we are working on to cope with such a flood of onionskins: 1. Developing a Proof of Work (PoW) system to has a rate-limitation knob rejecting the load of onionskins while letting legitimate ones through.[2] We still need to solve some design issues (feel free to help!) but hope to have that feature integrated into Tor soon. 2. Relay operators started to experiment with iptables/nftables rules and having the right ones available might be a good stopgap approach against the onionskin related DoS. We are coordinating that effort[3], so we have something available to propose to the wider community, which is kept up-to-date and limits the risks of traffic overblocking. Feel free to help as well with that effort. The other noteworthy incident started around September 13 when exit nodes began to get overloaded (while the other DoS was and is still ongoing). Unfortunately, that exit related DoS is heavily impacting our users' experience as can be seen in our OnionPerf data[4]. While we are still investigating the nature of that DoS attack it turns out that blocking particular IP addresses with ExitPolicy rules seems to help on exit nodes this is tested on. The Artikel10 exit node operators provided even a script recently[5] to help with that (much appreciated, thanks!). This approach is highly experimental at this point and it might help us at least to come up with an actual design idea to counter that particular exit DoS. Thanks, Georg [1] For information about overload in general and what "drop of onionskins" means, see: https://support.torproject.org/relay-operators/#relay-bridge-overloaded. It contains as well a guide on how to enable MetricsPort monitoring yourself so you see the actual metrics of your own relay. [2] https://gitlab.torproject.org/tpo/core/tor/-/issues/40634 [3] https://gitlab.torproject.org/tpo/community/support/-/issues/40093 [4] https://metrics.torproject.org/torperf.html [5] https://lists.torproject.org/pipermail/tor-relays/2022-October/020848.html

1 0

MetricsPort: tor_relay_connections_total type confusion
by nat＠danwin1210.de 28 Oct '22

28 Oct '22

Hello David, again, thanks for your work on adding more metrics to tor's MetricsPort! Many relay operators will love this and documentation will be useful [1]. I reported https://gitlab.torproject.org/tpo/core/tor/-/issues/40699 which got closed yesterday, but there was likely a misunderstanding and the changes did not solve the underlying issue. The core issue is: The metric called tor_relay_connections(_total) [2][3] contains a mix of different types (gauge, counter). When mixing types in a single metric, the TYPE definition will always be wrong for one or the other value. For example grafana will show this if you use a counter metric without rate(): "Selected metric is a counter. Consider calculating rate of counter by adding rate()." It is a best practice to avoid mixing different types in a single metric. >From the prometheus best practices [4]: "As a rule of thumb, either the sum() or the avg() over all dimensions of a given metric should be meaningful (though not necessarily useful). If it is not meaningful, split the data up into multiple metrics. For example, having the capacity of various queues in one metric is good, while mixing the capacity of a queue with the current number of elements in the queue is not." An idea to address the underlying issue: One connection metric for counter and one for gauge: - tor_relay_connections_total for counters, like the current label state="created" - tor_relay_connections for gauge metrics, like the current label state="opened". "rejected" also appears to be a gauge metric. Another nice feature of these metrics would be to have a label for what type of system is connecting (src="relay", src="non-relay") - more on that in yesterday's email. A tool by toralf [4] also shows these and uses the source IP but tor itself does not need to look at the source IP to determine the type, something discussed in last week's relay operator meetup. best regards, nat [1] https://gitlab.torproject.org/tpo/web/support/-/issues/312 [2] https://gitlab.torproject.org/tpo/core/tor/-/commit/06a26f18727d3831339c138… [3] https://gitlab.torproject.org/tpo/core/tor/-/commit/6d40e980fb149549bbef5d9… [4] https://prometheus.io/docs/practices/naming/

2 2

Upcoming OpenSSL 3 security bugfix release
by Georg Koppen 28 Oct '22

28 Oct '22

Hello relay operators! If you are running OpenSSL 3 please be aware that you might need to upgrade it to 3.0.7 as fast as possible on next Tuesday (Nov 1). In an announcement[1] it got said 3.0.7 fixes a CRITICAL security issue. Operators running on the 1.1 series are fine as far as we know so far. Georg [1] https://www.openwall.com/lists/oss-security/2022/10/25/4

1 0

(Invitation) Join us! Tor Relay Operator Meetup - October 22, 2022 - 1900 UTC
by gus 24 Oct '22

24 Oct '22

Dear relay operators, The next Tor relay operator meetup will happen on Saturday, October 22 at 19.00 UTC. ## Where BigBlueButton: https://tor.meet.coop/gus-og0-x74-dzn ## Agenda (WIP) * Announcements * Tor and Snowflake in Iran * EOL rejection * State of DoS attack * New network health project * Q&A * Next Tor Relay Operator Meetup Meeting pad: https://pad.riseup.net/p/tor-relay-op-meetup-o22-keep Everyone is free to bring up additional questions or topics at the meeting itself. ## Registration No need for a registration or anything else, just use the room-link above. We will open the room 10 minutes before so you can test your mic setup. Please share with your friends, social media and other mailing lists! cheers, Gus -- The Tor Project Community Team Lead

4 5

Performance issues/DoS from outgoing Exit connections
by Alexander Dietrich 22 Oct '22

22 Oct '22

Hello, on the evening of 2022-10-18, we (Artikel10) started getting alerts about our Tor servers, while our traffic declined sharply. When we investigated, we found that there were hundreds of thousands of TCP connections (per server) open to a single address, orders of magnitude more than any other address. We blocked this address via "ExitPolicy reject", then another one, and since then things seem to have improved. I have thrown together a small Python script to detect this and generate "ExitPolicy reject" lines automatically: https://github.com/artikel10/surgeprotector This is still experimental, so if you decide to give the script a try, please keep an eye on it. Kind regards, Alexander -- PGP Key: https://dietrich.cx/pgp | 0x52FA4EE1722D54EB

3 3

List number of circuits per connection
by Logforme 20 Oct '22

20 Oct '22

I run the relay 8F6A78B1EA917F2BF221E87D14361C050A70CCC3 Like most relays mine has been targeted by the DoS attack. Hundreds of VPS IPs creating millions of IP connections. This I mitigated with rules in my firewall. Looking at the firewall counters it looks like that attack has now stopped. However the relay is still overloaded from lots of circuit creations. Normally my little relay reports around 100K circuits open in the log file but since the overloading started it's closer to 1M circuits open. All these circuit creations put a strain on the CPU, sometime pegging it at 100% (4 core i5-4670K CPU @ 3.40GHz). Worse, it seems to eat memory. Normally the tor process uses about 3GB (out of 8GB) but I have seen it quickly shoot up to using all memory and all swap. I assume this is because of the circuit creation DoS (it's new behavior) and what causes the oom killer to kill the tor process at least once a day or so. So, how do I mitigate the circuit creation DoS? My immediate thought is to identify if there are a few IPs responsible for the majority and add those to my firewall naughty list. Is there a way to query the tor process about number of open circuits mapped to IP addresses?

3 4

bridge down
by Anonforpeace 19 Oct '22

19 Oct '22

Hello: My Tor Bridge has been down for awhile as I was moving to a new home. I have been trying to bring it up again and have been receiving the messages you see below. I have checked the the tor project status and see that there is a Ddos attack affecting the network. Is that why I am getting this or am I doing something wrong? Thank you. darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ sudo systemctl enable --now tor.service Synchronizing state of tor.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable tor darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ sudo systemctl restart tor.service darkhoodie@darkhoodie-HP-Compaq-Pro-6300-SFF:~$ journalctl -e -u tor@default Oct 16 00:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 00:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 01:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 01:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 > Oct 16 01:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 01:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 02:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 02:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 02:14:16 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: No circuits are opened. Relaxed timeout for circuit 875 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the> Oct 16 02:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 02:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 03:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 03:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 03:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 03:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 04:00:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Heartbeat: Tor's uptime is 1 day 12:00 hours, with 0 circuits open. I've sent 6.47 MB and received 36.85 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 161 c> Oct 16 04:00:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: While not bootstrapping, fetched this many bytes: 28998071 (server descriptor fetch); 2431916 (consensus network-status fetch); 310310 (microdescriptor fetch) Oct 16 04:00:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Heartbeat: Since last heartbeat message, I have seen 0 unique clients. Oct 16 04:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 04:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 > Oct 16 04:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 04:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 05:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 05:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 05:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 05:24:16 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: No circuits are opened. Relaxed timeout for circuit 920 (a Testing circuit 3-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the> Oct 16 05:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 06:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 06:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 06:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 06:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 07:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 07:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 > Oct 16 07:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 07:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 08:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 08:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 08:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 08:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 09:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 09:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 09:02:21 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 103 buildtimes. Oct 16 09:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 09:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 10:00:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Heartbeat: Tor's uptime is 1 day 18:00 hours, with 0 circuits open. I've sent 7.75 MB and received 43.92 MB. I've received 0 connections on IPv4 and 0 on IPv6. I've made 188 c> Oct 16 10:00:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: While not bootstrapping, fetched this many bytes: 34600394 (server descriptor fetch); 2858305 (consensus network-status fetch); 361968 (microdescriptor fetch) Oct 16 10:00:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Heartbeat: Since last heartbeat message, I have seen 0 unique clients. Oct 16 10:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 10:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 > Oct 16 10:20:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 10:40:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 11:00:14 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Your server has not managed to confirm reachability for its ORPort(s) at 100.2.224.20:443. Relays do not publish descriptors until their ORPort and DirPort are reachable. Plea> Oct 16 11:00:15 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Unable to find IPv6 address for ORPort 443. You might want to specify IPv4Only to it or set an explicit address or set Address. [60 similar message(s) suppressed in last 3540 > Oct 16 11:05:13 darkhoodie-HP-Compaq-Pro-6300-SFF systemd[1]: Stopping Anonymizing overlay network for TCP... Oct 16 11:05:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Interrupt: we have stopped accepting new connections, and will shut down in 30 seconds. Interrupt again to exit now. Oct 16 11:05:13 darkhoodie-HP-Compaq-Pro-6300-SFF Tor[16182]: Delaying directory fetches: We are hibernating or shutting down. Sent with [Proton Mail](https://proton.me/) secure email.

4 4

Most useful bridge distribution
by Thoughts 12 Oct '22

12 Oct '22

Hi all - Running a bridge, and per some stats I saw earlier Moat seems to be the most popular distribution method. Just curious is something else is recommended? Some seem less secure than others, but I don't know the methods used to prevent abuse. Would appreciate guidance. Cheers, Kevin

2 1

Tor 0.4.6.x is unsupported, please upgrade
by Georg Koppen 09 Oct '22

09 Oct '22

Hello! To repeat what recently[1] got brought up: it's time to get relays upgraded in case they are running the EOL 0.4.6.x Tor series. We'll start reaching out to operators with valid contact information this week and plan to reject relays which are still on 0.4.6.x in about 5 weeks from now on at the end of September. You can follow along that process in our bug tracker[2] if you want. For the general processes around dealing with EOL relays in the Tor network see my mail from last October[3]. Feedback and improvements are welcome, as always. Georg [1] https://twitter.com/torproject/status/1557392816250441728 [2] https://gitlab.torproject.org/tpo/network-health/team/-/issues/252 [3] https://lists.torproject.org/pipermail/tor-relays/2021-October/019862.html

4 4

many connections
by Sandro Auerbach 09 Oct '22

09 Oct '22

Hello, After changing my server, the connections settled between 6000-8000 incoming connections in the first 2 weeks of the warm-up period. (Guard/non exit) Since it seems that many relays have been overloaded in the last few weeks, I think a big DDOS is running again. Yesterday I tried to reduce the bandwidth a bit.I've just looked again and see over 26800 incoming connections. Is this even possible or is it more of a bug in the system?30 minutes later still 22000 connections... Have you observed something similar? Many greetings Sandro

4 9

'nudging' is a crime - 1B98468097E7F3FF102926423DF44315E414CBCF: down
by Fred 08 Oct '22

08 Oct '22

1 0

Lots of dropped onion skins
by Jonathan D. Proulx 07 Oct '22

07 Oct '22

HI All, I was checkign up on my (middle) relay stats: https://metrics.torproject.org/rs.html#details/9715C81BA8C5B0C698882035F75C… and saw an "overload" banner, after some learning I see lots of onionskins being dropped in the metrics: tor_relay_load_onionskins_total{type="tap",action="processed"} 890 tor_relay_load_onionskins_total{type="tap",action="dropped"} 0 tor_relay_load_onionskins_total{type="fast",action="processed"} 0 tor_relay_load_onionskins_total{type="fast",action="dropped"} 0 tor_relay_load_onionskins_total{type="ntor",action="processed"} 3096501 tor_relay_load_onionskins_total{type="ntor",action="dropped"} 2827649 tor_relay_load_onionskins_total{type="ntor_v3",action="processed"} 3096501 tor_relay_load_onionskins_total{type="ntor_v3",action="dropped"} 2827649 processed and dropped are growing pretty rapidly so maybe this is a know and ongoing attack, but I don't see why I would be dropping. The system has 8 corse and 8G RAM neither of which seems stressed. Less than 2G or RAM is in use and systrrem load (top under linux) reports ~70% idle (I guess if they're coming in really tight bursts it could average to that and still be droppong peaks). Anyone know what this is or have hints as to where to look? Thanks, -Jon

2 1

Re: [tor-relays] consensus weight tanking
by Me 07 Oct '22

07 Oct '22

Thanks for the prompt response. My apologies for the omission in the original post. My relays are called 405test1 and 405test2. Both relays are vm's on a proxmox server with the only difference in set up being port numbers. I have had both operating since July 2022 with no issues. Thanks again! On October 6, 2022 4:59:22 AM CDT, tor-relays-request(a)lists.torproject.org wrote: >Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > >You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of tor-relays digest..." > > >Today's Topics: > > 1. Re: Moving middle relays to bridges? (Chris) > 2. Consensus weight tanking (Me) > 3. Re: Consensus weight tanking (Georg Koppen) > 4. Re: many connections (Chris) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Wed, 05 Oct 2022 05:32:20 -0400 >From: Chris <tor(a)wcbsecurity.com> >To: tor-relays(a)lists.torproject.org >Subject: Re: [tor-relays] Moving middle relays to bridges? >Message-ID: <2d1975a2-6362-48d3-8dc3-05bd16797797(a)wcbsecurity.com> >Content-Type: text/plain; charset="utf-8" > >Bridges more or less function as guard relays except their IP addresses are not known. Having a bridge with an IP address that's already know somehow defeats the purpose. > >As far as I'm concerned the list of relays should not be public. Only exit relays need to be known for liability reasons. Once we stop publishing IP addresses of relays, the need for bridges will be greatly reduced. > >That being said, I believe if your relay is no longer a relay for a week, it will be removed from the public relay list. Not sure if it will be removed from the censors' list. >?? > > >-------- Original Message -------- >From: "Isaac Grover, Aileron I.T." <igrover(a)aileronit.com> >Sent: Tue Oct 04 12:15:52 EDT 2022 >To: "tor-relays(a)lists.torproject.org" <tor-relays(a)lists.torproject.org> >Subject: [tor-relays] Moving middle relays to bridges? > >Good morning, > >According to tor metrics, there have been nearly three times the number of relays as bridges over the last three months so I would like to move my handful of middle relays to bridges. They will keep their same IP address. Is there a best practice with regards to doing this so the directories don't get confused? > >Make your day great, >Isaac Grover > > > >------------------------------------------------------------------------ > >_______________________________________________ >tor-relays mailing list >tor-relays(a)lists.torproject.org >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >

2 1