- tor-relays - lists.torproject.org

Monthly IRC operator meetup - March 7th
by Colin Childs 05 Mar '19

05 Mar '19

Hi everyone, This is a reminder that the next IRC relay operator meetup will be held on Thursday, March 7th at 02:00UTC. These meetups take place on irc.oftc.net <http://irc.oftc.net/>, in #tor-meeting. We are also working on adding additional meetups throughout the month to better accommodate operators in different timezones, I hope to have more news about this shortly. I hope you’re all having a great week! Where: irc.oftc.net <http://irc.oftc.net/> @ #tor-meeting When: Thursday, March 7th @ 02:00UTC Agenda pad: https://storm.torproject.org/shared/7aCxQSwglBMGqO2o49g-_Iby9lDJgiaw8KLPL21… <https://storm.torproject.org/shared/7aCxQSwglBMGqO2o49g-_Iby9lDJgiaw8KLPL21…> (please feel free to add discussion items)

1 0

Relay Installed, port forwarded, but not responding
by Doug Roberts 05 Mar '19

05 Mar '19

I've installed the relay application, forwarded the ports as I normally do, but when I go to canyouseeme.org and try port 9001 or 9030, none of them show responding. I also don't see my IP in https://metrics.torproject.org/rs.html#search <https://www.google.com/url?q=https%3A%2F%2Fmetrics.torproject.org%2Frs.html…> even though it's been 6+ hours. A look at the routers shows that there is some traffic flowing through the ports, but it's so minimal I'm not sure what it is: https://is.gd/4NkFix Any ideas?

2 1

Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".
by technonerd＠fea.st 02 Mar '19

02 Mar '19

I run one relay and another tor instance for hidden services and socksport. Haven't had a problem until 0.4.0.2_alpha. Ive had it crash twice so far. Maybe my configs aren't sane? [err] descriptor at 0x8a0acdb0830 begins with unexpected string "". Is another process running in our data directory? Exiting. First config User tor PIDFile /var/run/tor2/tor2.pid SOCKSPort 9052 ControlPort 9053 Log notice file /var/lib/tor2/notices.log RunAsDaemon 1 DataDirectory /var/lib/tor2/data CookieAuthentication 1 ClientUseIPv6 1 ClientPreferIPv6ORPort 1 ClientPreferIPv6DirPort 1 HiddenServiceDir /var/lib/tor2/ssh/ HiddenServicePort 22 127.0.0.1:22 HiddenServiceDir /var/lib/tor2/ssh-new/ HiddenServiceVersion 3 HiddenServicePort 22 127.0.0.1:22 HiddenServiceDir /var/lib/tor2/bitcoind/ HiddenServicePort 8333 127.0.0.1:8333 Second config User tor PIDFile /var/run/tor/tor.pid Log notice syslog Log notice file /var/log/tor/debug.log #Log notice debug file /var/lib/tor/data/tor.log DataDirectory /var/lib/tor/data ControlPort 9051 HashedControlPassword CookieAuthentication 1 ORPort 9001 ORPort []:9050 DirPort 9030 BandwidthRate 4 MBytes BandwidthBurst 5 MBytes Nickname PancakeWhore ContactInfo ExitPolicy reject *:* ExitPolicy reject6 *:*

5 8

Tor End-of-Life Reminder for tor 0.3.3
by nusenu 02 Mar '19

02 Mar '19

Hi, this is a reminder for everyone still running tor 0.3.3.x. This version reached end of life on 2019-02-28 https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… Please keep your relays updated to a version that is still supported. Here is a list affected operators (with cwfr >=0.01) sorted by consensus weight fraction +----------------------------------------------------+---------------------------------------------+------+ | contact | versions | cwfr | +----------------------------------------------------+---------------------------------------------+------+ | abuse(a)to-surf-and-protect.net | 0.3.3.9 | 3.19 | | Servbr Admin <servbr [AT] mail [DOT] md> | 0.3.3.7 | 0.29 | | tor terjan net | 0.3.2.10,0.3.3.7,0.3.3.9 | 0.18 | | florentin aatt rochet ddoott be; LTC: LhRqJZu6U87B | 0.3.3.9 | 0.14 | | Admin <tor(a)ngc292.space> | 0.3.1.9,0.3.2.9 | 0.13 | | tor[at]zeroday.rocks | 0.3.3.9 | 0.12 | | 4096R/61263264 tux3 <barrdetwix(a)gmail.com> | 0.3.3.5-rc | 0.11 | | abuse(a)to-surf-and-protect.de | 0.3.3.9 | 0.11 | | tesuji - 1FZWmNWLrnzGCPPturD3GSiRfHk7vSuSbM | 0.3.0.10 | 0.11 | | Thomas Steen Rasmussen / Tykling <thomas(a)gibfest.d | 0.3.3.7 | 0.11 | | hedonist.jane77(a)tutanota.com | 0.3.3.9 | 0.10 | | Boris Nagaev 19pZzECKDDMbSpaWEy8vGvELEfXM8GrkHS <b | 0.3.2.10 | 0.09 | | contact(a)paulbsd.com | 0.3.2.10 | 0.09 | | 1Q5fZnsG5BSizXmJbrq8FsACnd6kSTBju7 | 0.3.3.7 | 0.08 | | Zwiebel <zwiebel(a)kawo2.rwth-aachen.de> | 0.3.3.9 | 0.08 | | Peter Pan <peterpan(a)fscore.de> | 0.3.2.10 | 0.07 | | Stash Crypto <infrastructure AT stashcrypto dot co | 0.3.1.10 | 0.07 | | DFRI <tor AT dfri dot se> - 1Muz37TfXVBiJKRJkAqTNo | 0.3.3.9 | 0.06 | | Orkan G\u00FCndogdu <orkan95(a)gmail.com> | 0.3.2.10 | 0.06 | | Tor Relay Admin <tor-admin AT meurisse DOT fr> | 0.3.3.9 | 0.06 | | <Mr. Cha Cha> DoTheChaCha(a)protonmail.com | 0.3.3.9 | 0.05 | | drift(a)multinet.no - 1Geq8GGC7qTh7dfptneAYtpeARPAL8 | 0.3.3.9 | 0.05 | | Itzhak Daniel <itzhak+tor(a)itk98.net> | 0.3.1.10 | 0.05 | | Torchwood <contact [at] pakitow [dot] eu> | 0.3.2.10 | 0.05 | | 0x77A31D11 Tony Olagbaiye <frony0 AT gmail dot com | 0.3.0.10 | 0.04 | | 20EE126C6B5C53D48F9D3D21C582B6E15BF059B9 Roman rom | 0.3.3.7 | 0.04 | | 3583217664127336(at)gmail(dot)com [tor-relay.co] | 0.3.3.7 | 0.04 | | Brad Koehn <tor(a)koehn.com> | 0.3.3.8 | 0.04 | | kirtrib(a)gmail.com | 0.3.3.9 | 0.04 | | MaggiWuerze admin(a)maggiwuerze.de | 0.3.1.10 | 0.04 | | Random Person <nobody AT example dot com> | 0.2.5.16,0.3.0.9,0.3.3.7,0.3.3.9 | 0.04 | | seedelmann [you know what belongs here] edelmann [ | 0.3.3.9 | 0.04 | | tor at cybercyber dot wtf | 0.2.5.16 | 0.04 | | Tor Reactor <0d0[AT]protonmail.com> | u42omsvzmh7 | 0.3.3.9 | 0.04 | | tor(a)niij.io | 0.3.3.8 | 0.04 | | torrelay(a)brave.com | 0.3.3.7 | 0.04 | | [ben] <at> [benatherton] <dot> [com] | 0.3.3.9 | 0.04 | | 0x9F29C15D42A8B6F3 Nos oignons <adminsys@nos-oigno | 0.3.3.9 | 0.03 | | 0xA711D81A m_price-at-mit-dot-edu 12fymnTuJsMEgUeR | 0.3.3.9 | 0.03 | | 0xF85959ECB7238802 foertel <mehl(a)foertel.com> | 0.3.3.9 | 0.03 | | 0xFFFFFFFF Random Person <nobody AT example dot co | 0.2.4.29,0.3.2.10,0.3.3.9,0.4.1.0-alpha-dev | 0.03 | | 145tXZyQEfdmpYhmbFtYe84kjghB5ymPA4 swraysford at g | 0.3.3.9 | 0.03 | | 1EpHny(a)protonmail.com - 1EpHnyDUC66N9dMJCyb3Zsc7ws | 0.3.3.9 | 0.03 | | 4096R/0x4cf76925833e2e24 Knight <knight AT germanc | 0.3.3.9 | 0.03 | | 4096R/5819E33F Zhongfu Li <tor at zhongfu dot li> | 0.3.2.10 | 0.03 | | a b u s e. TAT r o t e z e l l e. TOT n e t | 0.3.3.7 | 0.03 | | Alex de Joode <usura(a)sabotage.org> | 0.3.2.9 | 0.03 | | Donate : 1BcGs8GAJwVQ6BpTN9BtRcKvGWzLnmcXwK (UVZCU | 0.3.3.9 | 0.03 | | jim(dot)r(at)outlook(dot)com | 0.3.3.9 | 0.03 | | jimmy(at)bulanik(dot)nl | 0.3.3.7 | 0.03 | | mward44(at)uwo(dot)ca | 0.3.3.9 | 0.03 | | Niccolo <none AT your dot biz> | 0.4.1.0-alpha-dev | 0.03 | | Nicholas Merrill <nick AT calyx dot com> BTC - 14w | 0.2.5.16 | 0.03 | | PhilibertAspert(at)obfuscated(dot)com [tor-relay.c | 0.3.3.6 | 0.03 | | Random Person caceyjones(a)gmail.com | 0.3.2.10 | 0.03 | | sykotik.org US tor node | 0.3.2.10 | 0.03 | | Tor Operator <tor(a)hezmatt.org> | 0.2.5.16 | 0.03 | | tor(at)0day.rocks | 0.3.2.10 | 0.03 | | tor-admin <tor(a)mnesys.org> | 0.3.3.7 | 0.03 | | Torservers.net <support .AT. torservers .DOT. net> | 0.3.2.10 | 0.03 | | 0xB83A02ED Randy Bush <randy AT psg dot com> | 0.3.3.9 | 0.02 | | 0xB9A02A3D Pavol Rusnak <stick+tor(a)gk2.sk> | 0.3.1.8 | 0.02 | | 0xF30A703B Ahh.si abuse <ahh.si+abuse[at]enowaves[ | 0.3.3.9 | 0.02 | | : | 0.3.2.10 | 0.02 | | <hostmaster at denetron dot com> | 0.3.3.9 | 0.02 | | <idabwells AT systemli dot org> | 0.3.3.6 | 0.02 | | <mknoszlig AT zeroton dot in> | 0.3.2.10 | 0.02 | | admin <arbuckletor AT gmail dot com> | 0.3.3.9 | 0.02 | | admin(a)notoriousbit.net | 0.3.3.9 | 0.02 | | Administrator <contact(a)tor-node.net> - BTC 15HkPq8 | 0.2.8.11 | 0.02 | | agata-relay AT jawnosc dot com | 0.3.2.10 | 0.02 | | Alexander Bernhard <alexanderbernhard80 AT gmail d | 0.3.2.10 | 0.02 | | ALEXANDR UVAROV <dbeelial MM gmail.com Nasse-Catte | 0.2.5.16 | 0.02 | | alexkovalev(dot)1990(at)mail(dot)ru [tor-relay.co] | 0.3.3.9 | 0.02 | | calgary2k17(at)gmail(dot)com | 0.3.3.9 | 0.02 | | hannesexner91+tor(a)googlemail.com | 0.2.5.16 | 0.02 | | hoFFy <sebastian @ machinewithoutbrain.de> | 0.3.3.9 | 0.02 | | horst(a)faust-home.de | 0.2.5.16,0.3.2.10 | 0.02 | | isorry(a)no.no | 0.3.2.10 | 0.02 | | Ivanushka Durachok <torstrasse dot leak at spamgou | 0.3.2.10 | 0.02 | | Jon Proulx <jon AT csail dot mit dot edu> GPG Key | 0.3.3.9 | 0.02 | | Kd8hln.com Jeffschefke(a)gmail.com | 0.3.1.9 | 0.02 | | kernelexpl0it(a)jabber.ru | 0.3.2.10 | 0.02 | | madnight madnight <danon(a)gmx.de> | 0.3.1.10 | 0.02 | | Marvin Moloczek <tor(a)moloczek.com> | 0.3.2.10 | 0.02 | | nino [dash] tor [at] ninov [dot] de (gpg B8D657E63 | 0.3.3.7 | 0.02 | | no6gaeda(a)gmail.com | 0.3.3.9 | 0.02 | | none | 0.3.2.10,0.3.3.9 | 0.02 | | Phillip <phillip(a)dangernoodle.de> | 0.3.2.10 | 0.02 | | potlatch protonmail com | 0.3.3.7,0.3.3.9 | 0.02 | | PrisnCell <PrisnCellTor AT tutamail dot com> | 0.3.3.7 | 0.02 | | r.team.hq(a)yandex.ru | 0.3.3.9 | 0.02 | | randm(a)tuta.io | 0.3.2.10 | 0.02 | | RARvolt <rarvolt(a)rarvolt.net> | 0.2.8.12 | 0.02 | | Scott Maxwell tor-contact-2017-beratna (at) scottm | 0.2.5.16 | 0.02 | | ss [aT] xcoin [d0t] ro BTC: bc1q49wsl94gdwpphngpp7 | 0.4.1.0-alpha-dev | 0.02 | | starfleet --at-- trash ..dot.. net | 0.3.3.9 | 0.02 | | suporte(a)wirelesspt.net | 0.3.3.8 | 0.02 | | theshadowghost(a)rambler.ru | 0.3.3.9 | 0.02 | | tor [at] skeeerus [dot] club [tor-relay.co] | 0.3.3.6 | 0.02 | | tor(a)argute.io | 0.3.3.9 | 0.02 | | tor(a)i19.se - 1KN4W7FpzUPURwRQrVGsQCptbR34Kb8n9x | 0.3.3.5-rc | 0.02 | | tormate(at)tuta(dot)io [tor-relay.co] | 0.3.1.9 | 0.02 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2Sezz3DEHDF | 0.3.3.3-alpha | 0.02 | | tor_relay(a)f00bar.wtf | 0.3.2.10 | 0.02 | | ${CONTACT_GPG_FINGERPRINT} ${CONTACT_NAME} ${CONTA | 0.3.1.10,0.3.1.9 | 0.01 | | 0x112CA89F scholzi100 <tor(a)scholzi100.de> 1436DgS4 | 0.3.3.7 | 0.01 | | 0x65714c2b6f3b74cb Thijs Houtenbos <info@thijshout | 0.3.3.9 | 0.01 | | 0xA5CBA13E <tor[AT]d0p1[dot]eu> - 19wzjCe4m6YiiAh | 0.3.2.10 | 0.01 | | 0xB3AC4F40BC396055 Stephan Henrichs <stiepen <twen | 0.3.3.9 | 0.01 | | 59FDAC19FBC4E692652F3EB0C7B7552BDF21283B Smith <qt | 0.3.3.7 | 0.01 | | <548af91b673e7d80d6c9> 9i2c2ranzbol13aif568 at x.o | 0.3.3.6 | 0.01 | | <ben + tor [at] graef . in> 128qLZCaGdoWhBTfaS7ryt | 0.3.3.9 | 0.01 | | <onions at mit dot edu> | 0.3.2.10 | 0.01 | | <pdestor(a)lelantos.org> | 0.3.3.7 | 0.01 | | <tor - chaoshosting . de> | 0.3.1.9 | 0.01 | | <tor AT geekariom dot com> | 0.3.3.9 | 0.01 | | @jbrps 0x588F6C31 <jonas(a)rz-k.de> | 0.3.3.9 | 0.01 | | Admin <admin AT tor-relay dot io> | 0.3.2.10 | 0.01 | | amuse <tor-amuse%foofus.com> | 0.3.2.10 | 0.01 | | Anonymous | 0.2.4.27,0.2.8.12,0.3.2.10 | 0.01 | | Anonymous Coward <anonymous AT nullhost dot net> | 0.3.1.9 | 0.01 | | Antonio Maia <antonio.maia(a)protonmail.com> | 0.3.2.10 | 0.01 | | christianbro <at> yandex <dot> ru - 1D1EjYEGHFPmc8 | 0.2.7.6 | 0.01 | | DeaVulTan <deavultan(a)tuta.io> | 0.2.4.27 | 0.01 | | edgar.tor.uk(a)gmail.com | 0.3.3.6 | 0.01 | | Fabian Schlenz tormaster(a)schle.nz | 0.3.3.7 | 0.01 | | FEC1 B783 BE51 F6E1 DD1B 86C5 A847 5092 E7C3 76AA | 0.3.3.7 | 0.01 | | g <g @ eryd DOT net> | 0.2.4.27 | 0.01 | | human(a)google.com | 0.3.2.10 | 0.01 | | ICOSADEV TOR <icosadev(a)gmail.com> | 0.3.0.9 | 0.01 | | Inbox: tor/sevenlayers/org | 0.3.2.10 | 0.01 | | inbox(a)wooodoka.ru | 0.2.6.10 | 0.01 | | Kristofer Hallin mail(a)krihal.se | 0.3.3.7 | 0.01 | | lagartobostero(a)hotmail.com | 0.3.3.7 | 0.01 | | Me <wiz.ard(a)gmx.net> | 0.3.3.7 | 0.01 | | Meet me on the balcony | 0.3.3.6 | 0.01 | | Micah Sherr <msherr(a)cs.georgetown.edu> | 0.3.2.9-dev | 0.01 | | mshepard2(a)maricopa.edu | 0.3.2.10 | 0.01 | | Nick Sheppard <nicksheppard03(a)gmail.com> | 0.2.7.6 | 0.01 | | ohello(a)tuta.io | 0.3.0.13 | 0.01 | | Person d(a)mdng.me | 0.2.5.12 | 0.01 | | PGK <tor at the-goober.net> | 0.3.3.9 | 0.01 | | Pierre <pierre+tor at ratni dot v4v dot be> | 0.3.3.7 | 0.01 | | Random Person <periplanetaamericanus AT gmail dot | 0.3.3.9 | 0.01 | | Random Person <tor at 1d4 dot us> - 1N7sBLKvekRD4E | 0.3.3.6 | 0.01 | | Random Person tort(a)pike.pl | 0.3.1.9 | 0.01 | | Ranlvor <tor AT starletp9 dot de> | 0.3.3.9 | 0.01 | | rhfred(a)disroot.org | 0.3.2.10 | 0.01 | | Rogemedic <admin(a)waltersnet.noip.us> | 0.3.2.10 | 0.01 | | shallot protonmail com | 0.3.3.3-alpha | 0.01 | | support @ TORdashRELAYdotUS | 0.3.2.10 | 0.01 | | Sysadmin of the Day Role Person <wbb aaaaattttt fa | 0.3.2.10 | 0.01 | | TC <thinkcolorful AT thinkcolorful dot org> | 0.3.3.9 | 0.01 | | Tobias Meggendorfer Mail:<tobias .AT. meggendorfer | 0.3.2.10 | 0.01 | | tor(a)alexdpsg.net | 0.3.3.9 | 0.01 | | tor(a)haltmayer.com | 0.3.3.9 | 0.01 | | tor(a)remus.be | 0.3.3.8 | 0.01 | | twink0r @ twitter | 0.3.3.7 | 0.01 | | was.small(a)was.info | 0.3.3.9 | 0.01 | | Wubim Foundation <services AT wubim DOT com> | 0.3.1.9 | 0.01 | | Wubim Foundation <services AT wubim.com> | 0.3.3.9 | 0.01 | +----------------------------------------------------+---------------------------------------------+------+ -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Debugging ipv6 conenctivity
by Charly Ghislain 25 Feb '19

25 Feb '19

Hi all, My tor relay has got the UnreachableIpv6 flag set once i mentionned an OrPort with my ipv6 address. >From what i can tell, my server is reachable over ipv6, and can contact the directory authorities through ipv6 (following the instructions found there: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Makesurerelaypo… ). The node is behind an haproxy that relays ipv6 traffic to natted ipv4 (with no logging for those concerned). It seems to work fine for web content over ipv6, and traffic on both ips (v4 and v6) goes through this channel. I can successfully telnet my node ORPort using my v6 address. The ports have been defined this way in torrc: ORPort 0.0.0.0:9001 NoAdvertise ORPort 91.121.79.188:9001 NoListen ORPort [2001:41d0:1:84bc::1]:9001 NoListen Is there a way to make a tor client connect to a specific relay to debug this kind of connectivity issues? Or any other mean? In the meantime ive removed the advertized ip6. Regards, Charly

4 6

Regarding linux-tor-prio.sh script
by rl1987＠sdf.lonestar.org 24 Feb '19

24 Feb '19

Hello, Tor repository contains the following script, that has not been updated much in last 10 years or so: https://gitweb.torproject.org/tor.git/tree/contrib/operator-tools/linux-tor… Do people still use? Is it safe to remove it from the repo? Regards

1 0

Memory Used dropped again with 0.3.5.8
by petrarca＠protonmail.ch 24 Feb '19

24 Feb '19

Just an fyi for those who might be interested... With upgrading to 0.3.5.8 the memory usage of my Tor relay dropped again to reasonable levels. It suddenly started to increase end of January causing my relay to crash twice before leveling around 45% (a week before I had an ISP outage). Now it's back to around 25%. The relay bandwidth consumed over all the time was pretty much stable. [Memory Used.png]

1 0

relayor v19.0.0 is released
by nusenu 23 Feb '19

23 Feb '19

Hi, relayor has been made for relay operators to help them install and manage tor relays with minimal effort. https://github.com/nusenu/ansible-relayor Changes since v18.1.1 ------------------------------ - torrc: enable tor's Sandbox feature by default on Ubuntu (where it was previously disabled as a workaround for #160 ) don't set tor RelayBandwidthBurst if the input field is empty - increase tor_alpha_version 0.3.4.x -> 0.4.0.x - increase min ansible version 2.6.2 -> 2.7.8 - add support for OpenBSD 6.4 - add support for FreeBSD 12 (drop 10.x) - README: mark CentOS/Fedora as currently broken due to upstream package issues #185 - test-kitchen: add OpenBSD support add guard-alpha test-suite kind regards, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

How To Add Reachable Ports To OBFS4 Bridge
by Keifer Bly 22 Feb '19

22 Feb '19

Hi all, So I am looking to add some reachable ports to my OBFS4 bridge at https://metrics.torproject.org/rs.html#details/148BD64BED9F2C27637D986DE032E CF14E5B9E9A As this list is public, I guess I should not provide the port numbers that tor and obfs4 are running on. However, would adding reachable ports like 80, 443, 8080 be doable? I know that these ports that might not bind very well as lots of other types of traffic use them, however I saw the ticket at https://trac.torproject.org/projects/tor/ticket/7875 And this raises a concern about bridges being reachable for users who are connecting from behind firewalls, etc (hence the reason why they need to use a bridge), it seems like a good idea to have bridges reachable on ports that aren't likely to be blocked by network administrators or ISPS. Let me know what you think. --Keifer

2 2

Relay operators meetup Lisbon (23.02.2019)
by Vasilis 22 Feb '19

22 Feb '19

Dear Tor friends and relay operators, Tomorrow (23.02.2019) a relay operators meetup will take place at Block cafe, Berlin. When: Saturday, February 23rd, 2019 Time: 15:00 / 3:00 PM Where: Block Cafe, Rua Latino Coelho 63, 1st floor, 1050-133, Lisbon, Portugal Event link: https://privacylx.org/en/events/tormeetup3/ Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

1 0

Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by Neel Chauhan 19 Feb '19

19 Feb '19

Hi tor-relays@ mailing list, I have a Tor relay "NeelTorRelay2": https://metrics.torproject.org/rs.html#details/D5B8C38539C509380767D4DE20DE… This relay is hosted on a 300 mbps Verizon FiOS (FTTH/GPON) connection. My server is a HPE ProLiant MicroServer Gen10 (quad-core AMD X3421 variant) running FreeBSD, and my router is a Linksys WRT1900AC running OpenWrt. For some reason, the Advertised Bandwidth is not going above ~19.5 MiB/s. If my relay is pushing 10MB/s (80mbps) at a given time, the CPU usage is around 20%, so I don't think its the CPU. My question is that is this lower Advertised Bandwidth speeds normal for a relay hosted on a connection behind a consumer level router and it's NAT table (even despite OpenWrt)? Could it be Verizon's DPI/QoS now that Net Neutrality is repealed? Would using a non-consumer router (like Ubiquiti or pfSense) help? Thank You, Neel Chauhan === https://www.neelc.org/

4 4

Re: [tor-relays] Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by starlight.2018q2＠binnacle.cx 18 Feb '19

18 Feb '19

Neel Chauhan neel at neelc.org at Mon Feb 18 18:05:47 UTC 2019 > >I feel it's my Linksys WRT1900AC because consumer routers aren't >designed for the traffic high-bandwidth Tor relays handle, even after >flashing things like OpenWrt. The router is probably dropping packets and is problem. Also consumer grade switches generally cannot handle FiOS without dropping tons of packets. A one TCP connection speedtest will not trigger overload the way a 7000 connection Tor router does. Dealt with this here by attaching the Linux server directly to FiOS and having it act as the outside router. The relay would run much better but I fried the mainboard with a PCIx NIC overload; swapped in an incredibly ancient system formerly collecting dust on a shelf. Too busy/lazy to put up the newer box waiting to take it's place.

1 0

Re: [tor-relays] Tor relay on Verizon FiOS/FTTH: Advertised Bandwidth capped at ~19.5MiB/s
by Roman Mamedov 18 Feb '19

18 Feb '19

On Mon, 18 Feb 2019 09:06:05 -0500 Neel Chauhan <neel(a)neelc.org> wrote: > Verizon gives both 300 mbps upload and download speeds. Uploads are more > heavily oversubscribed on FiOS, primarily because GPON gives 2.5gbps > downloads and 1.25gbps uploads. But then again the upload will be barely utilized by typical residential Internet users. Still my recommendation is to test your bandwidth in multiple ways first, be it speedtest.net, or (better yet) https://github.com/sivel/speedtest-cli, or iperf3 servers, if you can find any near your location. If tests show that you do get near 300 Mbit both directions, the next step would be to just set up two instances of Tor, as I suggested before in your thread[1]. Actually fun to see my prediction from back then coming true precisely (with regard to getting only 200 Mbit). [1] https://www.mail-archive.com/tor-relays@lists.torproject.org/msg15819.html Running two instances is the universal solution which should improve Tor's bandwidth utilization on almost any connection. -- With respect, Roman

2 2

IRC operator meeting - February 7th
by Colin Childs 13 Feb '19

13 Feb '19

Hi everyone, As previously discussed (https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html <https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html>) we are resuming our IRC relay operator meetings this Thursday, February 7th @ 2:00UTC. These meetings will be held in #tor-meeting on irc.oftc.net <http://irc.oftc.net/>. If you’d like to add to the agenda, please edit the pad at https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6D… <https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6D…> See you all there!

2 3

Re: [tor-relays] BadExit why?
by Olaf Grimm 12 Feb '19

12 Feb '19

Thank you for the answer. I try to get a new IP from the Trabia support. Olaf Am 12.02.19 um 21:51 schrieb David Goulet: > On 12 Feb (21:35:29), Olaf Grimm wrote: >> inet 178.175.148.15 > Thanks Olaf! > > That IP was flagged as rewritting bitcoin addresses on Jan 21st, 2019. > > It appears you re-used a malicious IP from I.C.S. Trabia-Network S.R.L. > > Do you have an easy way to request a new IP for that Exit node or it is kind > of a pain? > > Un-blacklisting a relay that is still not considered expired from our reject > rule set can be a laborious process because essentially, we have to make a > case to the directory authorities and they decide if they remove the rule or > not based on our arguments ;). > > So changing the IP would be definitely the easiest way else we can try to > convince the dirauth :). > > Sorry for the inconvenience! > David > >> Am 12.02.19 um 21:34 schrieb David Goulet: >>> On 12 Feb (21:30:10), Olaf Grimm wrote: >>>> Hello ! >>>> >>>> I provisioning a new exit since two hours. It is a totally new relay in >>>> a VM. My other relays at the same provider are ok. Why I see "BadExit" >>>> in Nyx??? Now my first bad experience with my 11 relays... >>>> >>>> fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD >>>> Nickname Hydra10 >>> This relay is not yet on Relay Search: >>> >>> http://rougmnvswfsmd4dq.onion/rs.html#search/CCDC4A28392C7448A34E98DF872213… >>> >>> I'm guessing it is quite new. >>> >>> That fingerprint is *not* set as a BadExit so this means you might have gotten >>> the IP address of an old BadExit. >>> >>> Can you share the address so I can look it up? >>> >>> Thanks! >>> David >>> >>>> At all exits I have the same firewall rules and torrc configs: >>>> >>>> ufw status >>>> Status: active >>>> >>>> To Action From >>>> -- ------ ---- >>>> 22/tcp ALLOW Anywhere >>>> 9001/tcp ALLOW Anywhere >>>> 9030/tcp ALLOW Anywhere >>>> 80/tcp ALLOW Anywhere >>>> 443/tcp ALLOW Anywhere >>>> 1194/tcp ALLOW Anywhere >>>> 53/tcp ALLOW Anywhere >>>> 53/udp ALLOW Anywhere >>>> 1194/udp ALLOW Anywhere >>>> 22/tcp (v6) ALLOW Anywhere (v6) >>>> 9001/tcp (v6) ALLOW Anywhere (v6) >>>> 9030/tcp (v6) ALLOW Anywhere (v6) >>>> 80/tcp (v6) ALLOW Anywhere (v6) >>>> 443/tcp (v6) ALLOW Anywhere (v6) >>>> 1194/tcp (v6) ALLOW Anywhere (v6) >>>> 53/tcp (v6) ALLOW Anywhere (v6) >>>> 53/udp (v6) ALLOW Anywhere (v6) >>>> 1194/udp (v6) ALLOW Anywhere (v6) >>>> >>>> Please take a look what happens. >>>> >>>> Olaf >>>> _______________________________________________ >>>> tor-relays mailing list >>>> tor-relays(a)lists.torproject.org >>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >>> _______________________________________________ >>> tor-relays mailing list >>> tor-relays(a)lists.torproject.org >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > >

2 1

BadExit why?
by Olaf Grimm 12 Feb '19

12 Feb '19

Hello ! I provisioning a new exit since two hours. It is a totally new relay in a VM. My other relays at the same provider are ok. Why I see "BadExit" in Nyx??? Now my first bad experience with my 11 relays... fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD Nickname Hydra10 At all exits I have the same firewall rules and torrc configs: ufw status Status: active To Action From -- ------ ---- 22/tcp ALLOW Anywhere 9001/tcp ALLOW Anywhere 9030/tcp ALLOW Anywhere 80/tcp ALLOW Anywhere 443/tcp ALLOW Anywhere 1194/tcp ALLOW Anywhere 53/tcp ALLOW Anywhere 53/udp ALLOW Anywhere 1194/udp ALLOW Anywhere 22/tcp (v6) ALLOW Anywhere (v6) 9001/tcp (v6) ALLOW Anywhere (v6) 9030/tcp (v6) ALLOW Anywhere (v6) 80/tcp (v6) ALLOW Anywhere (v6) 443/tcp (v6) ALLOW Anywhere (v6) 1194/tcp (v6) ALLOW Anywhere (v6) 53/tcp (v6) ALLOW Anywhere (v6) 53/udp (v6) ALLOW Anywhere (v6) 1194/udp (v6) ALLOW Anywhere (v6) Please take a look what happens. Olaf

3 2

plans to require ContactInfo to be non-empty
by nusenu 11 Feb '19

11 Feb '19

Hi, due to some recent and ongoing events related to a malicious entity running tor relays I'll start to pursue an idea that I had for some time: require non-empty ContactInfo (non-empty does not mean valid email address) This is primarily a non-technical policy discussion which will take place on tor-dev@. If you want to help right away and currently don't make use of the ContactInfo, please set it. If you think such a change would negatively affect you please let me know (off-list is also fine if you prefer). thanks, nusenu -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

9 12

2 ip addresses at the same device, works except for the DirPort
by Toralf Förster 07 Feb '19

07 Feb '19

I ordered a 2nd ip address for my server and put them in the first order in my network configuration. I do wonder, why this adapted torrcconfiguration: $> cat /etc/tor/torrc # torrc at tor-relay # PIDFile /var/run/tor/tor.pid DataDirectory /var/lib/tor/data Nickname zwiebeltoralf OutboundBindAddress 5.9.158.75 DirPort 80 ORPort 443 DirPort [2a01:4f8:190:514a::2]:80 NoAdvertise ORPort [2a01:4f8:190:514a::2]:443 ControlPort 9051 Log warn file /tmp/warn.log #Log notice file /tmp/notice.log #Log info file /tmp/info.log ExitRelay 0 IPv6Exit 0 works at the first glance (about 6,000 connection) but still give after a while in the log: Feb 06 19:59:08.000 [notice] Tor 0.4.0.1-alpha opening log file. Feb 06 20:19:26.000 [warn] Your server (<xx>:80) 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. (where <xx> is the new main ip address at my eth0 device) -- Toralf PGP C4EACDDE 0076E94E

2 2

Tor meetup @ Onionspace, Berlin
by Vasilis 03 Feb '19

03 Feb '19

Dear Tor friends and relay operators, Tomorrow (02.02.2019) a relay operators meetup will take place at Onionspace, Berlin. When: Saturday, February 2nd, 2019 Time: 16:00 / 4:00 PM Where: Gottschedstrasse 4, Entrance 4, 13357 Berlin (U Nauener Platz) Event link: https://blog.torproject.org/events/tor-meetup-berlin Hope to see many of you there! Cheers, ~Vasilis -- Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162 Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

3 2

note to Falback Directory operators: bandwidth wasting bot
by starlight.2018q2＠binnacle.cx 03 Feb '19

03 Feb '19

For the last year a bot of some kind has loaded Fallback Directory relays with excessive directory document requests. Some detail can be found in ticket #27921 at https://trac.torproject.org/projects/tor/ticket/27921. To determine if your relay is affected, look the relay up in https://metrics.torproject.org/rs.html, click the 6-Month history tab, and examine the graph for significantly higher "write bytes per second" relative to "read bytes per second". I find this annoying (since I pay for the wasted bandwidth) and came up with a one-line hack that mitigates the abuse without impairing the usefulness of the DIR service to normal relays and clients. If you compile your daemon from source and are interested contact me directly for the patch.

2 1

Re: [tor-relays] Tor RAM usage (DoS or memory leaks?) - Flood of circuits
by petrarca＠protonmail.ch 03 Feb '19

03 Feb '19

There is something really strange going on indeed. What I noticed is an increase of circuits and my device running out of memory until it stopped working so I had to reboot it on 31. Jan. Then again the memory usage increased until it leveled out at a rather unusual, high usage. The actual bandwidth usage is not unusual though (always around 2Mbps on my relay). Attached a screenshot of my memory usage the last few days (I hope attachments do work here; it's in fact Tor using that memory as could be checked with ps and htop). Heartbeat messages of the log are: Jan 31 10:57:56.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 447 circuits open. I've sent 2.66 GB and received 2.65 GB. Jan 31 16:57:56.000 [notice] Heartbeat: Tor's uptime is 12:00 hours, with 19764 circuits open. I've sent 9.59 GB and received 9.54 GB. Jan 31 22:57:56.000 [notice] Heartbeat: Tor's uptime is 18:00 hours, with 54178 circuits open. I've sent 12.36 GB and received 12.30 GB. Feb 01 04:57:56.000 [notice] Heartbeat: Tor's uptime is 23:50 hours, with 79333 circuits open. I've sent 14.89 GB and received 14.81 GB. Feb 01 10:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 5:50 hours, with 110815 circuits open. I've sent 19.55 GB and received 19.45 GB. Feb 01 16:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 11:50 hours, with 141724 circuits open. I've sent 24.03 GB and received 23.90 GB. Feb 01 22:57:56.000 [notice] Heartbeat: Tor's uptime is 1 day 17:50 hours, with 12829 circuits open. I've sent 29.96 GB and received 29.75 GB. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, 1. February 2019 23:50, Roman Mamedov <rm(a)romanrm.net> wrote: > Hello, > > There seems to be an issue with Tor's memory usage. > Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the > machine got 430 MB into swap, slowing down to a crawl from iowait on accessing > the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" > in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that > doesn't add up to exhausting the 1.5 GB, and there are no other heavy > processes on the machine running. I rebooted it without further investigation. > > And right now on another machine running 2.9.16 I see: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor > > But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up > recently. > > Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, > with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. > Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: > 11361/11361 TAP, 239752/239752 NTor. > Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 > connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; > and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, > and 8779474 v4 connections. > Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits > rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. > Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) > failed. > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > With respect, > Roman > > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

4 3

FOSDEM Relay Operator Meetup
by relaya relaya 02 Feb '19

02 Feb '19

Hello! I read there is a Relay Operator Meetup organized by Colin at. I'm surprised it has not been announced on this list yet. Where and when does it take place exactly? thank you!

2 3

AS: "I.C.S. Trabia-Network S.R.L."
by nusenu 02 Feb '19

02 Feb '19

Hello, if you are the operator of the relays listed bellow, please set MyFamily and contactInfo in your torrc to avoid getting rejected. ornetradar(a)riseup.net: > 2019-02-01 > > | Up | Ext | JoinTime | IP | CC | ORp | Dirp | Version | Contact | Nickname | eFamMembers | FP | > |------+-------+------------+-----------------+------+-------+--------+-----------+---------------------------+--------------+---------------+------------------------------------------| > | 1 | 1 | 13:41:51 | 178.175.132.211 | md | 9001 | 8080 | 0.3.5.7 | chatter | chatter | 1 | E0259C34CEDF2D7A15271336EF65E21171EDF0FE | > | 1 | 1 | 13:44:58 | 178.175.132.210 | md | 9001 | 8080 | 0.3.5.7 | rendon | rendon | 1 | 14678AB26ED87E843B232EAEDF2A7BB384652473 | > | 1 | 1 | 13:44:58 | 178.175.143.158 | md | 9001 | 8080 | 0.3.5.7 | lincoln | lincoln | 1 | 56F55271722E2F8FFC3A77CA3F7F955B703CB027 | > | 1 | 1 | 13:44:59 | 178.175.132.212 | md | 9001 | 8080 | 0.3.5.7 | dossier | dossier | 1 | 1B2E31990B0F0A51920F40D5AB7598D41B214A20 | > | 1 | 1 | 13:44:59 | 178.175.132.213 | md | 9001 | 8080 | 0.3.5.7 | lark | lark | 1 | 1C3EE6E25868F0A8B816B62D81534146F2616008 | > | 1 | 1 | 13:44:59 | 178.175.143.156 | md | 9001 | 8080 | 0.3.5.7 | cuban | cuban | 1 | 1F25B74EF811858112DE18220B456F3CF6EE642E | > | 1 | 1 | 13:44:59 | 178.175.143.157 | md | 9001 | 8080 | 0.3.5.7 | charly | charly | 1 | 3722EEBB445B4E91B1A10CED86CD2E32B3C92D41 | > | 1 | 1 | 13:44:59 | 178.175.132.209 | md | 9001 | 8080 | 0.3.5.7 | matador | matador | 1 | 3E48BE2E2AC257D20546B5547729F4A5096BE39F | > | 1 | 1 | 13:44:59 | 178.175.132.214 | md | 9001 | 8080 | 0.3.5.7 | azorian | azorian | 1 | 72193825EE4EE6F9EF3243D8A7B49DB9122ADF21 | > | 1 | 1 | 13:44:59 | 178.175.143.155 | md | 9001 | 8080 | 0.3.5.7 | contras | contras | 1 | A67EB8AA880ACC94B716E178576142CB25D63B8C | > > https://nusenu.github.io/OrNetRadar/2019/02/01/a1 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

1 0

Re: [tor-relays] Circuit storms
by starlight.2018q2＠binnacle.cx 02 Feb '19

02 Feb '19

Jan 26 Heartbeat: circuits 6666 sent 103gb received 100gb Jan 26 Heartbeat: circuits 5672 sent 101gb received 98gb Jan 26 Heartbeat: circuits 6156 sent 106gb received 103gb Jan 26 Heartbeat: circuits 5902 sent 92gb received 90gb Jan 27 Heartbeat: circuits 6171 sent 80gb received 78gb Jan 27 Heartbeat: circuits 5920 sent 85gb received 82gb Jan 27 Heartbeat: circuits 4841 sent 82gb received 79gb Jan 27 Heartbeat: circuits 5718 sent 77gb received 71gb Jan 28 Heartbeat: circuits 5676 sent 86gb received 80gb Jan 28 Heartbeat: circuits 5157 sent 84gb received 81gb Jan 28 Heartbeat: circuits 7548 sent 105gb received 102gb Jan 28 Heartbeat: circuits 16448 sent 88gb received 84gb Jan 29 Heartbeat: circuits 31521 sent 107gb received 97gb Jan 29 Heartbeat: circuits 6255 sent 90gb received 86gb Jan 29 Heartbeat: circuits 14920 sent 91gb received 89gb Jan 29 Heartbeat: circuits 21502 sent 75gb received 72gb Jan 30 Heartbeat: circuits 37649 sent 80gb received 76gb Jan 30 Heartbeat: circuits 69831 sent 84gb received 81gb Jan 30 Heartbeat: circuits 16740 sent 102gb received 99gb Jan 30 Heartbeat: circuits 59552 sent 105gb received 101gb Jan 31 Heartbeat: circuits 73727 sent 88gb received 84gb Jan 31 Heartbeat: circuits 12156 sent 74gb received 71gb Jan 31 Heartbeat: circuits 63624 sent 81gb received 79gb Jan 31 Heartbeat: circuits 89129 sent 77gb received 72gb Feb 1 Heartbeat: circuits 98432 sent 105gb received 80gb Feb 1 Heartbeat: circuits 97975 sent 69gb received 66gb Feb 1 Heartbeat: circuits 27443 sent 94gb received 91gb

1 0

Tor RAM usage (DoS or memory leaks?)
by Roman Mamedov 01 Feb '19

01 Feb '19

Hello, There seems to be an issue with Tor's memory usage. Earlier today, with Tor 3.5.7 and 1.5 GB of RAM running two Tor processes, the machine got 430 MB into swap, slowing down to a crawl from iowait on accessing the swapped out memory. Typically 1.5 GB is more than enough for these. "VIRT" in top was ~1GB each, and "RES" was ~512MB each. Which is weird because that doesn't add up to exhausting the 1.5 GB, and there are no other heavy processes on the machine running. I rebooted it without further investigation. And right now on another machine running 2.9.16 I see: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 22432 debian-+ 30 10 5806816 5.157g 10464 R 39.5 33.1 39464:19 tor But not sure if it just accumulated 5.1GB of RAM slowly over time, or shot up recently. Feb 01 17:00:49.000 [notice] Heartbeat: Tor's uptime is 82 days 23:59 hours, with 70705 circuits open. I've sent 66622.45 GB and received 65906.91 GB. Feb 01 17:00:49.000 [notice] Circuit handshake stats since last time: 11361/11361 TAP, 239752/239752 NTor. Feb 01 17:00:49.000 [notice] Since startup, we have initiated 0 v1 connections, 0 v2 connections, 10 v3 connections, and 3385644 v4 connections; and received 14 v1 connections, 78592 v2 connections, 822108 v3 connections, and 8779474 v4 connections. Feb 01 17:00:49.000 [notice] DoS mitigation since startup: 2899572 circuits rejected, 121 marked addresses. 561 connections closed. 21956 single hop clients refused. Feb 01 17:08:20.000 [warn] connection_edge_process_relay_cell (at origin) failed. -- With respect, Roman

1 0