- tor-relays - lists.torproject.org

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 30 Aug '19

30 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 28 Aug '19

28 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

Improving throughput on weak CPU?
by Jochen 27 Aug '19

27 Aug '19

Hi there, I'm the operator of the following two exit nodes: https://metrics.torproject.org/rs.html#search/family:94C268630BEDCB64E7F888… My CPU is an Intel C2750 (8 cores total), which supports hardware accelerated AES yet a single process still maxes out at only ~150mbit/s. To get the most out of the machine and my single IPv4 address, I simply ran another relay which works fine, and now I'm averaging at around ~315mbit/s. Is there anything else I can tweak to improve throughput without having to order more IP addresses? I'm running Arch with stock 5.2.9 linux kernel. That being said, true multi threading would be much appreciated and would help people like me a lot :-) Regards, Jochen

4 4

AvoidDiskWrites
by [REDACTED] 25 Aug '19

25 Aug '19

Hi Torproject, i think about enabling AvoidDiskWrites 1 on all my relays and not only on my Pi because the prices for the VPS are anyway cheap as f*ck so i think saving the provider a few disk writes is a nice deal. In the manual it is described as: *AvoidDiskWrites* *0*|*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) ... which is not a very informative description on how it changes the behavior of Tor. I didnt found any more explanation about it. I would like to understand what Tor is NOT writing to disk anymore if set to 1 or what Tor IS writing to disk if set to 0 and if changing that have any effect for Tor users. As a relay operator i couldnt really see any difference enabled or not. Kind regards

3 2

tor relay ipv6
by armik900＠gmail.com 22 Aug '19

22 Aug '19

hi.in relay stopped working ipv6.address is correct all pings, including tor to the servers, but relay does not work.before that it worked perfectly 2 months.

6 12

Tor Relay - RelayBandwidthRate vs. RelayBandwidthBurst
by petrarca＠protonmail.ch 22 Aug '19

22 Aug '19

I'm struggling a bit with the two config options for RelayBandwidthRate and RelayBandwidthBurst - what I currently have in my torrc config file is: > ... > RelayBandwidthRate 8 Mbit > RelayBandwidthBurst 12 Mbit > ... My assumption was that on average the Relay would consume 8 Mbps max. but over a shorter period of time also up to 12 Mbps in case needed. What I see (historical monitor data at 10 s intervals for the past 6 months) is that the bandwidth usage never exceeds 8 Mbps. I can also see the consumption to be levelled out at 8 Mbps for minutes or hours so it looks like there would be a need for more bandwidth. My question: why can't I see the bandwidth usage going above 8 Mbps and making use of the allowed burst? Btw, I'm typically using the latest stable tor, currently the relay is on 0.4.0.5. Any comment welcome!

2 2

Very high CPU Load and low Traffic since Sunday
by Tim Niemeyer 20 Aug '19

20 Aug '19

Hello I've noticed a reduction in tor traffic about 50% since Sunday. The cpu load stayed almost same. The amount of TCP Sessions increased from ~34k to ~65k. Also the abuse rated about network scans got increased since Sunday. Does anyone knows what's there going on? My guess is that since Sunday anyone uses Tor for extended network scans, which results in a very high packet rate. Personally I've no problem with some network scans, but this is a bit annoying and I asked myself if this is still a scan or more a DOS. https://metrics.torproject.org/rs.html#search/family:719FD0FA327F3CCBCDA0D4… Kind regards Tim

7 7

Emerald Onion's new relays
by Christopher Sheats 20 Aug '19

20 Aug '19

Hello, Beginning this Wednesday, 2019-Apr-03, Emerald Onion will be starting 40 new uncapped and unfiltered exit relays using HardenedBSD in Seattle. We will turn on 10 new relays per day and be monitoring performance. In tandem, we will be publishing our updated edge routing and Tor relay configurations on our Github. We'll also publish an updated transparency report (spoiler: zero new requests). This work is part of our efforts to saturate our new unmetered 10Gbps transit link in the Westin data center. There we peer with the Seattle Internet Exchange with a separate 10Gbps connection. We'll be using our existing IP scopes: 2620:18C::/36 23.129.64.0/24 We are in the process of creating an RPKI ROA for our prefixes, and we are still rebuilding our DNS resolver (thanks nusenu for the feedback). These things will be completed before we turn on the new relays. If you donated to Emerald Onion (a 501(c)(3)) nonprofit), thank you! We'll be naming the relays accordingly. We will still accept new donations for relay naming rights-- email me directly for more information. Lastly, and If you're unaware, I spoke about our work at DEFCON 26: https://www.youtube.com/watch?v=cs6a1i4Owic Cheers, -- Christopher Sheats Executive Director for Emerald Onion Email: yawnbox(a)emeraldonion.org Office (& Signal): +1-206-739-3390 Website: https://emeraldonion.org/

12 20

Tor Activities - CCCamp 2019
by gus 19 Aug '19

19 Aug '19

Dear relay operators, The Chaos Communication Camp is an international, five-day open-air event for hackers and associated life-forms. It provides a relaxed atmosphere for free exchange of technical, social, and political ideas. == Tor Activities == * 2019/08/21 18:00 - Tor Relay Operator Meetup, about:freedom Village If you're a Tor user, operate a Tor relay, want to operate a Tor relay, or simply have questions, come and join us in this session with Q&A about the tor network and Tor Project. * 2019/08/22 12:30 - OONI: Measuring internet censorship around the world, about:freedom Village * 2019/08/22 13:30 - 14:55 - Tor Project: running Tor trainings with human rights defenders in Global South, about:freedom Village * 2019/08/23 14:00 - Updates from the Onion - The Road to Mobile Tor and Improved Censorship Circumvention, Room Curie == During all camp == Visit the Tor Project booth and the OONI booth in the about:freedom Village. https://blog.torproject.org/events/cccamp-germany

1 0

Attack on Tor exit and back-up directory server
by potlatch 19 Aug '19

19 Aug '19

Hello All, I commented and questioned earlier about significant slowing of one of my Finnish exit relays [1] and potential DoS attack. I took the server off line and did the best job I could hardening it. The host does not have DoS protection and uses Xen OpenVZ as his VPS manager. I was getting "nf_contract: table full, dropping packet." errors by the 1000s. That's fixed and I'm back on the Tor net now. One question remains: At any time I look there are 20-150 Iranian IP addresses trying to access the Tor server. Their IP range is from 5.113.x.x to 5.126.x.x. None have hashed fingerprints. Is it okay to let these guys go? Can they harm or slow Tor? Should I ban them? I'd like to learn from this. -potlatch Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

removal from the Fallback Directory list
by contact-tor-turing＠g0b.eu 19 Aug '19

19 Aug '19

hello, I managed until now the relay tor-turing - 8456DFA94161CDD99E480C2A2992C366C6564410 - ip 62.210.254.132 for four years and it was in the list of Fallback Directory. However he did not answer for 2 weeks, the support of my hosting provider told me that the motherboard is out of order and data are irrecoverable, so it should remove it from the list of Fallback Directory. thank you.

2 1

Fwd: Emerald Onion's new relays
by teor 19 Aug '19

19 Aug '19

Hi, We didn't clear the moderation queue last week, and this message was dropped from the queue. We'll make sure someone is looking at the queue every 1-3 days in future. T Begin forwarded message: >> On Mon, Aug 12, 2019 at 09:02:58PM +0200, lists(a)for-privacy.net wrote: >>> On 12.08.2019 02:46, Christopher Sheats wrote: >>> >>> It is discouraging to see so many small and large network operators >>> not using IPv6. Why is this such a problem? Tor Project, please >>> increase your #IPv6 awareness/outreach similar to how ARIN and the >>> other RIRs try very hard to do. >>> >> +1 >> >> Twitter :-( Wish you're on Mastodon, too. > > EO's Shawn Webb is on Mastodon: @lattera@bsd.network > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 443-546-8752 > Tor+XMPP+OTR: lattera(a)is.a.hacker.sx > GPG Key ID: 0xFF2E67A277F8E1FA > GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2

1 0

Removal from fallback directory mirror list
by Augusto Cezar Amaral 12 Aug '19

12 Aug '19

Hi folks, I'll need to shut down relay KrigHaBandolo (46791D156C9B6C255C2665D4D8393EC7DBAA7798). Can someone here help me with removing it from the fallback directory mirror list? Thanks

2 2

DoS attack on Tor exit relay
by potlatch 08 Aug '19

08 Aug '19

Hello Tor users, Help me with a problem please. I have a small exit/backup & directory VPS in Finland [1]. This last week the server (and Tor) have been overwhelmed with non-Tor IP addresses. This may be a small version of a DoS attack. I took the server down for a few days but when I restarted it the attack was there before Tor users. Eventually, the load caused kernal crash. I noticed this last week, that my Consensus Weight had dropped from 5500 to 68. Does anyone have an efficient way to defeat this ongoing attack? --potlatch [1] 9B31F1F1C1554F9FFB3455911F82E818EF7C7883 TorExitFinland Sent with [ProtonMail](https://protonmail.com) Secure Email.

7 10

10 Years Torservers.net: Death or Future?
by Moritz Bartl 08 Aug '19

08 Aug '19

tl;dr: torservers.net needs a new home! I started torservers.net after a random chat at a local bar some time early 2010. I wore a Tor shirt, and the guy next to me asked if that was "The Onion", the satire magazine. He became pretty excited about Tor after I told him what it was about, opened his wallet and gave me a 100€ bill "to put towards the network". Eventually it turned out that he was an Oracle software developer, so it's kind of funny to think about this as "one of the few good things Oracle has ever done". I thought about it for a bit, and then decided to take the money, which cemented the idea that I have had for quite some time: to get a more beefy machine to "properly" run a Tor exit, sharing the costs with others. Only a few days after I announced this idea on or-talk [1] in May 2010, some crazy Swede wired me another 1000€ (Thanks!). So, bad luck, I really had to do this now! I am still surprised at how successful the fundraising was. In fact, when we finally created a legal envelope of protection around me by starting the Zwiebelfreunde association in 2011, it was already clear that we needed to find others to do the same, instead of growing larger ourselves. The network was a lot different then, and some people tell me we had 80% of the overall exit capacity for quite some time after Olaf shut down his fast Blutmagie exit. So I went on a tour to inspire others. So, here we are, almost 10 years later, with 23 partner organizations in 15 countries. [2] After I got a "real job" in 2013 (that quickly grew into "more than full-time"), and at the same time the first grant money for torservers.net, we tried in many different ways to "recruit" others to "take over". Looking back, of course a lot of things happened and it was a crazy (and fun!) time, but long story short, until now nobody stepped up to take over the core role of a "coordinator" of activities. There are many many offers for help, and even more ideas of what torservers.net could do and be, but all people involved heavily at the beginning (Thanks!) don't have time to coordinate all the wonderful help, and do a proper handover. We tried a couple of times, only to spend a lot of time "training" a poor person to get them somewhat up to speed, but eventually everyone decided they had better things to do than to become frustrated at trying to walk blindly without much guidance. This is not an easy role to step into. If we take the May 2010 announcement as "launch date", the 10 years anniversary will be on May 10th, 2020. My dream would be to celebrate this with a fresh board at Zwiebelfreunde that has taken over the association, and another group that coordinates the international platform that torservers.net was meant to be(come). Of course we will not simply give away the domains and the legal entity and all our exit relays to just anyone. But, hm, yeah, truth is, probably almost anyone! ;-) For some years now, we've talked about the idea of a "relaunch". The most promising idea is to organize a proper Tor Relay Operators Retreat, maybe 50 people or so, with all the great people who have dedicated their lives to this project at some point, and all the great new folks who are as excited as all of us were back then about contributing to the Tor network. It would likely to be possible to convince Open Technology Fund or some other money source to sponsor travel and venue. I've always imagined this to happen in a nice "holiday" setting. At some point, I *will* go with a group of people to this fine venue [3], as an example of how this could look like. So far, I've tried to talk to individuals about it in smaller groups, and never announced it to the broader community in the way I do now. However, I still believe that this can only really be moved forward _in person_. I will do my best to ignore all mails you write to me or in this thread. Please write, coordinate, do everything that you think would be good to do to move this forward, but I don't really have the capacity to lead a good discussion. The only capacity I can offer is that we *need* someone to step up, and grab me at some event in meatspace. Ideally at that point that person is willing to have the A record pointed at some new place under their control, and we can begin the transition. Otherwise we will probably simply kill it for the 10 years anniversary, and finally make room for something new altogether. This is a call for help! Thanks. :-) Moritz P.S.: I will at some point soon post another mail about what I was up to the past years, and what I will be up to in the next few years. Don't worry, I'll still be around. [1] http://archives.seul.org/or/talk/May-2010/msg00058.html [2] https://torservers.net/partners.html [3] For a real Tor Relay Retreat, we would need something larger, but I think this gives you a pretty good idea of how I imagine it to look like: https://www.homeaway.co.uk/p868562

10 20

Running gigabit relay
by Mitar 07 Aug '19

07 Aug '19

Hi! I have Sonic Fiber which offers gigabit symmetric connection. I am thinking of using it for gigabit Tor relay, but I wonder what would be good hardware to use for something like that. Information I have found [1] is from 2010 so I wonder if there are any updates? Is there any simple small box I could use? Like Intel NUC? Information here [2] says that one can get 400 Mbps with AES-NI. And so with two processes limit per my public IP this would be around 800 Mbps then. Is this still a reasonable expectation? Do I have to care about the network card to serve gigabit (besides its being nominally gigabit)? What would be memory requirements for such a device? [1] https://www.mail-archive.com/or-talk@freehaven.net/msg14159.html [2] https://www.torservers.net/wiki/setup/server Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m

11 21

Configuring SQM on nodes
by Mitar 07 Aug '19

07 Aug '19

Hi! Has anyone tested how does configuring SQM on Tor nodes influence the quality of circuits over the node? Throughput, latency? So given that circuits have 3 hops in serial I would assume that any buffering/latency issues on nodes combine in a bad way. So using some smart queue management (SQM) might improve things? https://www.bufferbloat.net/projects/bloat/wiki/More_about_Bufferbloat/#why… So besides bandwidth measurements of nodes, should we also measure latency contributions by nodes? I think this is the whole idea behind the Bufferbloat movement, that it does not matter for user experience the final throughput if you have bad latency. That what most users perceive as "fast" is in fact good latency experience. Tor have notions of sustained and burst bandwidth, but this to me looks like just simplified QoS configurations. Shouldn't a better configuration be "do not increase latency by more than X"? Then if you hit the bandwidth limit, you are obviously increasing the latency more because some packets are not getting through. But it also captures the behavior better than "bursting is allowed up to Y". Mitar -- http://mitar.tnode.com/ https://twitter.com/mitar_m

1 0

Tor server setup of keys
by potlatch 05 Aug '19

05 Aug '19

I have not installed a Tor relay since the gpg server change. I started a new relay today and found that the instructions for ubuntu Bionic did not work for me. Specifically, url https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E8… | gpg --import gave me an error message that --import is not an option of curl. Has anyone come across this and worked out the problem? -potlatch Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

New Fallbacks from June 2019
by teor 05 Aug '19

05 Aug '19

Dear Relay Operators, Thanks to everyone who opted-in their relays as fallback directory mirrors. We rebuilt the list of fallbacks in June 2019. [0] The new list will be released in Tor 0.4.1.4-alpha/rc. It was backported to all supported Tor releases. [1] The FallbackDir flags on Consensus Health [2] and Relay Search [3] might take a week or two to update. Don't worry if your relay missed out this time. It's still helping Tor users. And we will rebuild the fallback list again in 6-12 months time. We are tracking future fallback changes in this ticket [4]. To opt-in your relays, add a comment to the ticket [4], or reply to this thread. If you have multiple relays, you can opt-in as many as you like. (We picked up to 7 per operator this time, and we may pick more next time.) T [0]: See: https://gitweb.torproject.org/tor.git/tree/src/app/config/fallback_dirs.inc https://trac.torproject.org/projects/tor/ticket/28793 [1]: 0.2.9, 0.3.5, 0.4.0, and 0.4.1: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… [2]: https://consensus-health.torproject.org/graphs.html Which uses stem's cached fallback list at: https://gitweb.torproject.org/stem.git/log/stem/cached_fallbacks.cfg [3]: For example, this relay is a new fallback, but its flag isn't shown yet: https://metrics.torproject.org/rs.html#details/1211AC1BBB8A1AF7CBA86BCE8689… [4]: https://trac.torproject.org/projects/tor/ticket/30972

2 2

ORPort // DirPort
by Fabio De Sicot 05 Aug '19

05 Aug '19

Hello everyone I have a problem I wasn't able to fix until now. Could you help me whit this? ------------------------ - when I start tor I receive this error: [...........] Aug 03 09:48:29.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. Aug 03 09:48:40.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. [...........] Aug 03 10:07:09.000 [warn] Your server () has not managed to confirm that its ORPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. Aug 03 10:07:09.000 [warn] Your server () has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc. - I verified, and ports 9051, 9001 and 9030 were not filtered # firewall-cmd --get-active-zones internal interfaces: eth0 # firewall-cmd --zone=internal --list-allinternal (active) target: default icmp-block-inversion: no interfaces: eth0 sources: ports: 9051/tcp 9051/udp 9001/tcp 9001/udp 9030/tcp 9030/udp protocols: masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: - I checked my torrc file # cat /usr/local/etc/tor/torrcNickname xxxxxx ORPort 9001 <<<< ControlPort 9051 <<<< DirPort 9030 <<<< # # RunAsDaemon 0 ExitRelay 0 CookieAuthentication 1 ContactInfo xxxxxxx - I verified the internal ip # ifconfig eth0eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.8 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::1874:3d84:ac42:fa97 prefixlen 64 scopeid 0x20<link> ether b8:27:eb:90:a2:b8 txqueuelen 1000 (Ethernet) RX packets 1118761 bytes 398404534 (379.9 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1095304 bytes 428598871 (408.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 - and I verified that on my router the port forwarding was active # Port Forwarding Name Port Range Protocol IP Address Enable TOR 9051 TCP&UDP 192.168.0.8 x ORPORT 9001 TCP&UDP 192.168.0.8 x DIRPORT 9030 TCP&UDP 192.168.0.8 x ------------------------ Thanks in advance Regatds -- Fabio De Sicot # https://fosstodon.org/@jolek78 <https://fosstodon.org/@jolek78>

2 1

Tor relay has low consensus weight
by Piers 04 Aug '19

04 Aug '19

Hi, i have been running a tor relay (link: https://metrics.torproject.org/rs.html#details/858BEC79D7355EC0631E98D47CF1…) on a raspberry pi 2 for 15 days, however i think there might be a problem with it. My consensus weight is only 43 and thus the relay doesn't get used much. Please advise if there is an issue -- Many thanks, -Piers

3 2