- tor-relays - lists.torproject.org

Low-bandwidth relay
by John Williams 04 Sep '19

04 Sep '19

I've been running tor on my openwrt-based home router (along the lines of 'anonabox'), and I configured it as a non-exit relay, because I thought why not - every little helps, right? I set a very low bandwidth limit, but it was using most of the configured bandwidth, so I figured it was helping. A few days ago I got an email saying my tor version was EOL, so I upgraded from version 0.3.2.10 to 0.4.1.5 (which required upgrading openwrt). Now tor is still working fine for me, but I don't see any network traffic when I'm not using it, so it is evidently not routing any third-party traffic any more. I don't see any errors in the log. Is this (a) expected behaviour because the previous traffic was just a bug in the old version of tor, or (b) an indication that there is something wrong with my upgraded installation? Any suggestions about where I should look would be welcome. I'm considering reconfiguring my system to be a bridge instead of a router, but I would prefer to sort out any possible problems with what I've got now, before making further changes.

2 1

end-of-life relays will be removed from the network eventually
by nusenu 03 Sep '19

03 Sep '19

Patches [1] are being prepared to remove Tor relays running end-of-life versions of Tor eventually. Affected relays as of 2019-09-03 16:00 UTC #relays 1276 CW Fraction 13.25 % Guard 16.91 % Exit 2.19 % Want to know if your relay is affected? Here is a list of affected relays (updated daily): https://nusenu.github.io/OrNetStats/eolrelays The Tor Relay Guide has instructions to help you stay on maintained Tor releases. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… [1] https://trac.torproject.org/projects/tor/ticket/31549 Tor people are sending out emails (cc'ing network-health): https://lists.torproject.org/cgi-bin/mailman/listinfo/network-health -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 1

Re: [tor-relays] Status of "new" defect #30767 Custom obfs4 bridge does not work on Tor Browser for Android
by nottryingtobelame＠protonmail.com 02 Sep '19

02 Sep '19

Ah, thank you for the reply. Well, I will continue to donate to and support the tor project whenever I can.

1 0

Status of "new" defect #30767 Custom obfs4 bridge does not work on Tor Browser for Android
by nottryingtobelame＠protonmail.com 02 Sep '19

02 Sep '19

I hate to be that guy, but I was wondering if there is any progress on resolving this defect? I'm sure it's not a front burner type of problem, but it would be nice to be able to use the Android app as intended. Using Orbot/Orfox as a backup feels like a poor workaround when there's an official Tor browser app. If I'm being impatient, just let me know - I'm not familiar with what's normal during this process. Thanks in advance.

3 2

Fast flag - wrong speed in dir-spec.txt?
by [REDACTED] 30 Aug '19

30 Aug '19

Hi Torproject, as far as i can see my relay currently can advertise 560 KiB/s. That are 573,44 KB/s. 43C7BC2E17FB26B204EC0BD9AA784E4736979087 Following your dir-specs it should get the "Fast" flag if it can provide more than 100KB/s. https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2595 At my other relay i already saw it providing 562 KiB/s and it got the "Fast" flag. A9DB853547A6459AB5190E62BF2F7B8F068FEB0A It seems the limit is above 560 KiB/s? If i remember it right then i already read somewhere that the requirements are now higher than 100 KB/s so i guess your documentation is wrong? Am i missing something why my relay with 560 KiB/s dont get the "Fast" flag?

3 3

Please test bandwidth and resiliency of greyponyitnyc002
by Conrad Rockenhaus 29 Aug '19

29 Aug '19

Hello, I was wondering if Rob would be willing to perform speed measurements on this node, it’s. 20 vcpu running CentOS 7 with manually compiled Tor against OpenSSL 1.1.1 on a 30Gbit link. I know it’s not going to see all of that bandwidth, it’s meant as a high powered VM platform because my intention is to start giving VMs back to the guys on my old infrastructure, and hopefully setup a “Torservers” type arrangement down the road, since this is hosted on unique ASN and addresses. Thanks, Conrad Rock Rockenhaus Greypony IT Consulting (254) 292-3350

1 0

3 questions
by niftybunny 29 Aug '19

29 Aug '19

Hi there, 1. anyone with any new news about the Darknet law in Germany or where you could ask for information? 2. Whats up with Torflow, still linked from Tor Atlas. As far as I can see it was last updated over 3,5 years ago? 3. So what happened to the new measurement? I can see a big spike https://metrics.torproject.org/bandwidth.html <https://metrics.torproject.org/bandwidth.html> and now its back to normal? Same with a lot of my relays, traffic doubled/tripled and now its the same or worse. niftybunny

2 2

Why is my Tor bridge relay not getting any traffic?
by Hikari 29 Aug '19

29 Aug '19

Hello everybody! I used to run a Tor bridge on Windows at home, where I have a 300/150 Mbps ISP. This Windows has memory leak and crashes after some hours, ad I believe that was making my bridge never get traffic. A few weeks ago I moved it to a Ubuntu server, also at home. I use uptimerobot.com to monitor if its port is reachable from outside and healthchecks.io to monitor if traffic entering from its local SOCKS port is reaching check.torproject.org. It's always up and reachable. But nyx reports it's rarely getting any traffic, and its bandwidth never surpasses 1KB/s. Its log heartbeat reports very little download and upload and always claims to has seen 0 unique clients. But how come, if my healthchecks.io monitor's curl call uses it every few minutes? metrics.torproject.org reports correct dates and uptime. Advertised Bandwidth is 58KB/s, way above what nyx reports. Flags are Fast, Running, V2Dir, Valid. What might be wrong? Or is it normal for a Tor bridge relay be this idle? This is my torrc removing identifiable data. |## Configuration file for a typical Tor user ## Last updated 9 October 2013 for Tor 0.2.5.2-alpha. ## (may or may not work for much older or much newer versions of Tor.) ## A handle for your relay, so people don't have to refer to it by key. Nickname MyNick ContactInfo mycontact ## Entry policies to allow/deny SOCKS requests based on IP address. SocksPort 9031 #SocksPort ::9031 #SocksPort 0.0.0.0:80 #SOCKSPolicy accept 192.168.* ## Send all messages of level 'notice' or higher to /var/log/tor/notices.log Log notice file /var/log/tor/notices.log ## Send every possible message to /var/log/tor/debug.log #Log debug file /var/log/tor/debug.log ## Use the system log instead of Tor's logfiles #Log notice syslog ## Uncomment this to start the process in the background... or use RunAsDaemon 1 ## The directory for keeping all the keys/etc. By default, we store ## things in $HOME/.tor on Unix, and in Application Data\tor on Windows. DataDirectory /var/lib/tor ## The port on which Tor will listen for local connections from Tor ## controller applications, as documented in control-spec.txt. ControlPort 9051 ## If you enable the controlport, be sure to enable one of these ## authentication methods, to prevent attackers from accessing it. CookieAuthentication 1 ################ This section is just for relays ##################### # ## See https://www.torproject.org/docs/tor-doc-relay for details. ## The IP address or full DNS name for incoming connections to your ## relay. Leave commented out and Tor will guess. Address hikari.mydomain.com ## Required: what port to advertise for incoming Tor connections. ORPort 80 ## Uncomment this to mirror directory information for others. Please do ## if you have enough bandwidth. DirPort 9030 # what port to advertise for directory connections ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy #ExtORPort 0.0.0.0:8000 ExtORPort 9041 ## Uncomment to return an arbitrary blob of html on your DirPort. Now you ## can explain what Tor is if anybody wonders why your IP address is ## contacting them. See contrib/tor-exit-notice.html in Tor's source ## distribution for a sample. #DirPortFrontPage /etc/tor/tor-exit-notice.html ExitPolicy reject *:* # don't run as an exit node BridgeRelay 1 # bridge PublishServerDescriptor 1 # published on bridge directory DB BridgeRecordUsageByCountry 1 # it's nice to see the country codes of users you are assisting #BandwidthRate 512000 #RelayBandwidthBurst 512000 #RelayBandwidthRate 512000 CellStatistics 1 PaddingStatistics 1 DirReqStatistics 1 EntryStatistics 1 ExitPortStatistics 1 ConnDirectionStatistics 1 HiddenServiceStatistics 1 ExtraInfoStatistics 1 #If non-zero, try to write to disk less frequently than we would otherwise. This is useful when running on flash memory or other media that support only a limited number of writes. (Default: 0) AvoidDiskWrites 0|

6 9

attack on my Finland exit/backup directory [9B31F1F1C1554F9FFB3455911F82E818EF7C7883]
by potlatch 28 Aug '19

28 Aug '19

I still haven't been able to rid myself of the Iranian servers revealed on the NYX connections page. I don't know their purpose but they slow the relay by about 85%. I have dropped them in the iptable input chain, restarted the VPS, but they show up after a day or two in spite. Today there were 121 of them with a large range of IPs. There have been as many as 1400 in a single day. None have identifiable hashed fingerprints. I've enclosed a couple attachments of my input table (partial) and the NYX connection page (also partial). Can anyone enlighten me regarding this situation? I will probably dump the exit relay if I can't fix this intrusion. Thanks people!! -potlatch Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Re: [tor-relays] Why is my Tor bridge relay not getting any traffic?
by Hikari 27 Aug '19

27 Aug '19

Thanks. It's been a few weeks I moved my relay to Ubuntu. I changed my Nickname and ContactInfo when I did that, so my fingerprint is new. Why is it on email bucket? Am I able to move it to bridges.torproject.org? On 27/08/2019 08:14 PM, Philipp Winter wrote: > On Tue, Aug 27, 2019 at 03:03:37PM -0300, Hikari wrote: >> Hello. Here's my fingerprint ------------ > > Your bridge is in the email bucket. It may not be requested as often as > over moat, but give it some time and you'll eventually see users. > > Cheers, > Philipp >

1 0