November 2024 - tor-relays - lists.torproject.org

Standalone snowflake proxy re-testing as restricted
by 0x5fcfbd30＠proton.me 21 Dec '24

21 Dec '24

Hey there, I have been running a standalone snowflake proxy for quite some time now. First in a docker container, but now in its own linux container to have more control over it myself. This has worked out great so far with an ephemeral-ports-range of 200 ports. Those are forwarded to the linux container in my router. Since a few days, I noticed a big drop in connections per hour. I restarted the proxy and it tested as restricted even though all ports are properly forwarded and I see the UDP packets reaching the machine via tcpdump. After several restarts, I finally got it to confirm unrestricted but 6 hours later (default re-test period?), its restricted again. Just to rule out the obvious, is it only me having this problem? I'm building from source and git log says: commit f940d7d6efe423c4d7a901a33d34bb51086b4a41 Date: Tue Nov 26 16:19:49 2024 +0000 chore(deps): update module github.com/pion/ice/v4 to v4.0.3 I wonder if this is a problem of my local setup or a bug snowflake itself. Any ideas? Best regards, 0x5fcfbd30

3 3

Next Tor Relay Operator Meetup - December 7th 2024 @ 1900 UTC
by gus 17 Dec '24

17 Dec '24

Dear Relay operators, Save the date! Our next online meetup is happening on Saturday, December 7th, 2024 at 1900 UTC[1]. I'm happy to announce that we'll have a special guest, Ben Collier, joining us to discuss his new book:"Tor: From the Dark Web to the Future of Privacy."[2] (2024) ## Agenda 1. Announcements - New WebTunnel bridges campaign - https://blog.torproject.org/call-for-webtunnel-bridges/ - Upcoming in-person events 2. Ben Collier's book presentation & discussion ## How to join Meetup details: - Room link: https://tor.meet.coop/gus-og0-x74-dzn - Date & Time: Saturday, December 7th, 2024 @ 19.00 UTC - Duration: 60 to 90 minutes - Tor Code of Conduct: https://community.torproject.org/policies/code_of_conduct/ - Registration: No need for a registration or anything else, just use the room link above. The room will open 10 minutes before the meetup starts. ## DON'T MISS SOTO This month, the Tor team was very busy with State of the Onion (SOTO), and I'd like to invite you all to watch the videos: - Community Day: https://www.youtube.com/watch?v=EODNtLqD7f8 - Tor Project Teams update: https://www.youtube.com/watch?v=HjPdReNmf_g cheers, Gus [1] If you're confused about UTC and your timezone, @anarcat maintains a cool project called undertime - https://gitlab.com/anarcat/undertime [2] "Tor: From the Dark Web to the Future of Privacy" book is available here: https://direct.mit.edu/books/oa-monograph/5761/TorFrom-the-Dark-Web-to-the-… -- The Tor Project Community Team Lead

2 3

install OBFS4
by Keifer Bly 13 Dec '24

13 Dec '24

Hi, So for Debain 12, what is the command to install OBFS4? For my bridge at https://metrics.torproject.org/rs.html#details/0E547D99DEB753B20A19EEAA053C… Even though I configured obfs4 in torrc its saying no transport protocols. Thanks. The torrc Nickname udeservefreedom ORPort <hidden> Log notice file /var/tornitces.log/notices.log SocksPort 0 BridgeRelay 1 PublishServerDescriptor bridge BridgeDistribution email ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:<hidden> ExtOrPort auto ExitPolicy reject *:* ContactInfo keiferdodderblyyatgmaildoddercom --Keifer

4 6

Regarding IPv6 & webtunnel bridge
by Dionysios K. 29 Nov '24

29 Nov '24

Hello, Is there any particular configuration change I have to do in torrc/nginx for my bridge to be listed as both v4/v6 on the metrics website? It's a webtunnel bridge and that complicates things, for obfs4 the configuration is pretty much straightforward. D.

3 2

Restart of standalone Snowflake proxies required
by Cecylia Bocovich 27 Nov '24

27 Nov '24

We recently completed an upgrade to the Snowflake broker machine[0] that required us to move the broker to a different IP address. We found, after updating our DNS records, that the standalone (command-line) proxies will not re-resolve the domain name of the broker and will continue to make connections to the old IP address until restarted. If you run a standalone Snowflake proxy, please restart when you get a chance. Thanks! [0] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…

1 0

relay operator meeting postponed
by George 23 Nov '24

23 Nov '24

Greetings fellow relay operators! Sorry for the last minute notice, but we're postponing the usual relay operators meeting previously set for tomorrow. Stay tuned for a new date. George -- 43C2 85B0 41B6 4AC1 0E02 2767 7092 AEB3 40B0 C804

1 0

Solicitation for an IPv4 block
by Christopher Sheats 20 Nov '24

20 Nov '24

Hello everyone, In light of Tor Project's push into the global south, I'm bringing on a new advisory board member (https://freeradical.zone/@kedislav) from Chile, and together we're documenting co-location and IP transit costs in the country for a possible Tor exit relay deployment. However, in order to do this, we need some company/university/nonprofit, or some kind person, to donate to us a /24 (or greater) IPv4 block. If said entity is in the USA, it's possible to make this a tax-deductible donation since we are a 501(c)(3). If you could connect me to anyone who might be able to do this for Tor, please feel free to connect me over Signal or email. We can use our existing IPv6 block for dual-stack relays. Or we might get a new ASN and new IPv6 block for that region. If you have any information about Chilean co-location and/or IP transit deals, or contacts, or even good places to get used or new servers, please let me know. I'm hoping that our involvement in the region will help inspire others to do something similar. We'll of course do a full bi-lingual write up like we did in 2017 (https://emeraldonion.org/blog/starting-a-human-rights-isp/) -- Christopher Sheats Director, Emerald Onion Signal: +1 206.739.3390 // emerald.01 Web: https://emeraldonion.org Mastodon: https://digitalcourage.social/@EmeraldOnion

1 0

Journal warnings spam
by Dionysios K. 19 Nov '24

19 Nov '24

Hey guys, Do you have any solution to stop the spam caused by tor: The IPv4 ORPort address 127.0.0.1 does not match the descriptor address <IP>. If you have a static public IPv4 address, use 'Address <IPv4>' and 'OutboundBindAddress <IPv4>'. Indeed I have a static IP but behind nat, so defining it in torrc is not possible as it can't bind to it.

2 2

Re: Looking for a new provider? Try Wedos.
by George Hartley 15 Nov '24

15 Nov '24

First of all, sorry for the late re-post of this e-mail to the list. An individual also active on the tor-relays list messaged regarding a new provider, I recommended one which is not crowded with Tor nodes, but our fellow decided to lie about the provider. Please read their quote. I can still recommend Wedos.cz for Guards/Middle relays, as well as bridges, and if you have very restrictive exit policy, maybe also for exits - however, confirm with staff first, and let them know which ports you want to allow. Also, always reply to all non-automated abuse reports, and forward them to the address for processed abuse reports given to you by staff. This was my original reply: Because their AI chat bot has infinite intelligence right? I know 2 people working there personally, Michal Jakubec and Roman Mondek, and they both reassured me yesterday that Guard/Middle and Bridge are NOT a problem, as long as they stay Guard/Middle or Bridge nodes. Using Tor FROM their network is also no problem.. using Tor to access THEIR is no problem. But, I did not trust their word.. So I tried it myself: No problem accessing the website using around 10 different exit nodes.. Then, I tried to order: Again, no problem! Received bitcoin payment information using a Tor mail service within 10 minutes: This is where I stopped, I did not pay the invoice and e-mailed Wedos stafff to please remove the order. But, Wedos supports Tor, and is a great choice especially for Guards/Middle nodes as well as bridges. Please don't lie about providers.. alternatively, if they still don't support Tor for you, please show the symptoms you are encountering. -GH On Thursday, November 7th, 2024 at 5:11 PM, Red Oaive clearly(a)ivegotyour.pw wrote: > On 2024-11-05 16:32, George Hartley via tor-relays wrote: > > > Also, please consider using a provider that is not overcrowded with > > Tor nodes already like OVH. > > > > I can recommend Wedos.cz ... https://wedos.cz/en/ > > They block access to their web site to Tor users. This doesn't bode well > for how Tor friendly they are. Their chatbot also claims tor is not > allowed: > > "Running Tor relays on a VPS from WEDOS is generally not allowed > due to the potential misuse of such services for attacks" > > Too bad becasue the price you quotes is attractive.

1 0

Re: Update: Tor relays source IPs spoofed to mass-scan port 22
by littlehoster.denote399＠passinbox.com 14 Nov '24

14 Nov '24

Hi, I had very similar reports to [tor-operator_urdn.co](https://forum.torproject.org/u/tor-operator_urdn.co): DateTime Action AttackClass SourceIP Srcport Protocol DestinationIP DestPort 0 30-Oct-2024 14:06:13 BLOCKED attempted-recon 92.51.45.21 0 202.91.162.47 22 1 30-Oct-2024 14:43:35 BLOCKED attempted-recon 92.51.45.21 0 202.91.162.24 22 2 30-Oct-2024 15:11:40 BLOCKED attempted-recon 92.51.45.21 0 202.91.162.24 22 3 30-Oct-2024 15:19:05 DENIED 92.51.45.21 64006 TCP 202.91.162.172 22 4 30-Oct-2024 15:19:20 BLOCKED attempted-recon 92.51.45.21 0 202.91.162.24 225 30-Oct-2024 15:44:49 DENIED 92.51.45.21 18054 TCP 202.91.161.94 22 The report is from the same IP-range.

1 0