tor-relays February 2017

tor-relays@lists.torproject.org

65 participants
37 discussions

ansible-relayor, how to ?
by Petrusko 01 Apr '18

01 Apr '18

Hey! I'm planning to try the "ansible-relayor" to deploy some Tor relay instances. If I'm not wrong, it's a main goal ? 2 instances / IP... (soooory for being really noob about this!!!) But I'm lost... not found a tutorial, step by step, you know the tutorial so loved by all noobs! For now, on a fresh Debian8 install, there are : - tor 0.2.9.8 (fresh install from depo, client is ok when opening log file) - ansible - ansible-galaxy install nusenu.relayor - git clone https://github.com/nusenu/ansible-relayor (the folder is stored in my /home...) Will it configure (automatically) many torrc file per instance ? +every key files /relay ? (I'm not too much lost!) Do have I to do this install on every server built ? Or relayor can manage few servers on different locations ? Command lines list use this tool if available ? Many thx for help !!! (and hard work for this tool :) -- Petrusko C0BF 2184 4A77 4A18 90E9 F72C B3CA E665 EBE2 3AE5

6 9

Monitoring multiple relays
by Xza 01 Nov '17

01 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello, I have a couple relays / exits running. Now my question is : how do you manage them is there any dashboard or CLI tools to manage them ( statistics, ect.. ) I know the cli tool specially for Tor "arm" Thanks alot. - -- PGP : 29A4CE52 -----BEGIN PGP SIGNATURE----- iQI4BAEBCgAiGxxEbyA8eWFuZGVyZXNvbkByaXNldXAubmV0PgUCV0SJlwAKCRBI of/XNyszSvv/D/9VtjI+bmiqK53v//StUbmpYjgQjYheYvwktFld+2XDURh52dmU sbk3lab2RS1eQJxjV0BVXMF9O2JUAlp4NA2UMpj8ZJlCk0h1S6p2o4/sAlsrHr8Z nb67HiaRIyEvi9cQiXFtDtK/onAkEuKskolyvh3ysJRRUubHSX1z8WuNJIc4xyGH ZpSLPGUOO6qI7mM8ztS0muEy1khmkHgtlyHi2l4K/NsW3I90cV3w6Db2AEnV6v1c tsfehqLExsHUdEo0U3hHU7yY1p2fzD5Z+C0tgVKTnP5Zus/Vr9OH/zFwxneo0E7a 5FHdnCZnNIG9W32uQgjDdmBEv/YFEd0um/vMWFGUehFANSt+DIps7E+AjwiJwm2i ov97JJurQkrSMX7ZchTEsy720Ju272olp2eDiHaXXTK2TkxcEq+d1gZfj7CXycPW 6mCrj6L6URJAZ34GJQfFFjv8QbFmKkAvGhxl/O8KXRbXxedbLH7PY73jmFjJcmxO +KnSeyqMe1KbzazYyFydP+VmgI2k1IlO89l8Jq1Gq9f2KOPY9UKFZjGDKLS0xGZW EnqU/KUINcrGejYFT8nYNxA+OFTd/ZGIX5qP4Vo5NsZ/pDLZjdxIcvHx1jjZbER+ 5Ku2bihm2KTNAGoYDqB3LGCm+QdEFG/p573xQCcXPk92GyhMJDi9EMPDgA== =mTa0 -----END PGP SIGNATURE-----

8 8

snaptor relays: MyFamily update required
by nusenu 08 Apr '17

08 Apr '17

Hi snaptorg, thanks for adding new relays, please do not forget to update your MyFamily. +---------------------+-----------------+---------------+------+ | first_seen | IP | MyFamilyCount | exit | +---------------------+-----------------+---------------+------+ | 2016-11-12 00:00:00 | 213.32.66.192 | 9.0000 | 0 | | 2016-11-26 23:00:00 | 193.70.90.199 | 9.0000 | 0 | | 2016-11-26 23:00:00 | 128.199.108.14 | 9.0000 | 0 | | 2016-11-27 00:00:00 | 139.59.46.211 | 9.0000 | 0 | | 2016-11-28 11:00:00 | 94.156.77.41 | 8.0000 | 1 | | 2016-11-28 14:00:00 | 142.4.206.241 | 9.0000 | 1 | | 2016-11-29 00:00:00 | 185.103.110.210 | 9.0000 | 1 | | 2016-12-03 23:00:00 | 144.217.90.138 | 9.0000 | 0 | | 2016-12-16 15:00:00 | 176.123.26.27 | 8.0000 | 1 | | 2016-12-16 23:00:00 | 193.70.22.86 | NULL | 0 | +---------------------+-----------------+---------------+------+ https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… regards, nusenu -- https://github.com/nusenu/ansible-relayor

3 9

why my exit is not being used?
by gustavo panizzo (gfa) 06 Apr '17

06 Apr '17

Hello I ran sorrentini [1] as a relay for a month or two and everything was fine. then 2-3 weeks ago i decided to allow exit, the traffic went down significantly, is that expected? it has recovered a bit but i feel the node is underutilized, is it stational? I've attached node's munin graphs [1] https://atlas.torproject.org/#details/5E762A58B1F7FF92E791A1EA4F18695CAC667… here is my torrc # general Nickname sorrentini Log notice syslog ControlPort 9051 HashedControlPassword XXXXXXXXX AccountingStart month 01 00:00 AccountingRule sum AccountingMax 1024GB ContactInfo 0x44BB1BA79F6C6333 <tor-admin AT zumbi dot com dot ar> MyFamily 82C92FBAF2196EC346670D12BB9650FE9FF55741,EFD2EEB91E5C5D8CB999B1EC68D89E51F8776AC7 SocksPort 0 SocksPolicy reject * ## IPv4 ORPort 128.199.76.145:443 DirPort 128.199.76.145:80 Address 128.199.76.145 OutboundBindAddress 128.199.76.145 ##IPv6 IPv6Exit 1 ORPort [2400:6180:0:d0::18a7:d001]:443 OutboundBindAddress [2400:6180:0:d0::18a7:d001] # Exit DirPortFrontPage /etc/tor/tor-exit-notice.html CellStatistics 1 DirReqStatistics 1 EntryStatistics 1 ExitPortStatistics 1 ExtraInfoStatistics 1 HiddenServiceStatistics 1 ExitRelay 1 ExitPolicy accept *:53 # DNS ExitPolicy accept *:80 # HTTP ExitPolicy accept *:110 # POP3 ExitPolicy accept *:143 # IMAP ExitPolicy accept *:220 # IMAP3 ExitPolicy accept *:443 # HTTPS ExitPolicy accept *:873 # rsync ExitPolicy accept *:989-990 # FTPS ExitPolicy accept *:991 # NAS Usenet ExitPolicy accept *:992 # TELNETS ExitPolicy accept *:993 # IMAPS ExitPolicy accept *:995 # POP3S ExitPolicy accept *:1194 # OpenVPN ExitPolicy accept *:1293 # IPSec ExitPolicy accept *:3690 # SVN Subversion ExitPolicy accept *:4321 # RWHOIS ExitPolicy accept *:5222-5223 # XMPP, XMPP SSL ExitPolicy accept *:5228 # Android Market ExitPolicy accept *:9418 # git ExitPolicy accept *:11371 # OpenPGP hkp ExitPolicy accept *:64738 # Mumble ExitPolicy reject *:* # nothing else is allowed -- 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333 keybase: https://keybase.io/gfa

7 22

CentOS Tor exit node broken after updating to 2.8.12
by Chris 16 Mar '17

16 Mar '17

Hello, I recently upgraded my tor version to 2.8.12 from 2.8.9(?) I think. Tor can now no longer bind to ports, as a regular user: /[warn] Could not bind to 0.0.0.0:43: Permission denied/ As root: /Feb 25 11:57:14.942 [notice] Opening OR listener on 0.0.0.0:43// //Feb 25 11:57:14.942 [notice] Opening Directory listener on 0.0.0.0:9030// //Feb 25 11:57:14.942 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050// //Feb 25 11:57:14.942 [notice] Closing partially-constructed Control listener on 127.0.0.1:9051// //Feb 25 11:57:14.942 [notice] Closing partially-constructed OR listener on 0.0.0.0:43// //Feb 25 11:57:14.942 [notice] Closing partially-constructed Directory listener on 0.0.0.0:9030// //Feb 25 11:57:14.942 [warn] Failed to parse/validate config: Failed to bind one of the listener ports.// / In the former case, I tried using eip to allow tor to bind to ports lower than 1024 but it made no difference. I suspect this an issue with the configuration of the server rather than tor. Where should I start? Best, Chris -- Protect your privacy: encrypt your communications GPG: CF7F98B2

2 2

dipulse.it relays: please specify 'MyFamily' in your torrc
by nusenu 05 Mar '17

05 Mar '17

Hi, thanks for adding more tor relays. Please do not forget to set the MyFamily parameter in your torrc configuration to tell clients your relays belong to a single operator, otherwise they might use your relays in multiple positions within a circuit, which is rather bad for their anonymity. If you need help with the MyFamily option let us know. thanks, nusenu https://github.com/nusenu/ansible-relayor https://raw.githubusercontent.com/ornetstats/stats/master/o/potentially_dan… ornetradar(a)riseup.net: > 2017-02-19 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | AS | CC | ORp | Dirp | OS | Version | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 | 12:53:10 | 163.172.189.100 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR15 | 1 > 1 | 0 | 12:49:39 | 163.172.181.240 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR16 | 1 > 1 | 0 | 12:45:42 | 163.172.187.152 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR14 | 1 > 1 | 0 | 12:51:17 | 163.172.183.161 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR18 | 1 > 1 | 0 | 12:42:14 | 163.172.160.239 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR13 | 1 > 1 | 0 | 12:52:08 | 163.172.183.220 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.2.8.12 | DipulseFR19 | 1 > 1 | 0 | 12:46:43 | 212.47.245.227 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR12 | 1 > 1 | 0 | 12:55:27 | 212.47.236.157 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR17 | 1 > 1 | 0 | 14:29:40 | 163.172.166.1 | Online S.a.s. | fr | 8443 | 8080 | Linux | 0.3.1.0-alpha-dev | DipulseFR11 | 1 > Fingerprints: > 5928164F3759E3710393E7DC1ED69FACB669BE82,0211F6543B8EB8BE2AAD17ABD05635BD135FFCF7,D3FA077CE59A2D13B6E6B8C62B04A2C03BAC784F,8D60E9C8DB03BE39159B8824680ACCBD642ACF62,AF59C8E3CBB0B2C34D2BDCBA55CD7282BAA22B22,B66760160753DD26A6FD1B4B87F9CB3D0EEACC2D,619B69FD8F3A4642E2E8E40B5E97D2875496C829,B5CFDBA1E8DAFE061C5D259BBC44BF994ACB8C26,EFDCB52BD37CDDEFDD38DEF3F6C7A60DCCF099EE >

1 2

Re: [tor-relays] [OrNetRadar] AS: "EDIS GmbH" - Linux (15)
by nusenu 04 Mar '17

04 Mar '17

If you added 15 relays on 2017-02-24 (yesterday) on AS38478, please consider setting ContactInfo and MyFamily in your torrc (and maybe a more recent tor version). thanks ornetradar(a)riseup.net: > 2017-02-24 > ----------------------------------------------------------------------------------------------------------------------- > Up|Ext|JoinTime| IP | CC | ORp | Dirp |Version | ContactInfo | Nickname | eFamlen > ----------------------------------------------------------------------------------------------------------------------- > 1 | 0 |15:31:23| 124.248.229.138 | hk | 9001 | 9051 |0.2.8.9 | None | coast | 1 > 1 | 0 |15:33:47| 124.248.229.140 | hk | 9001 | 9051 |0.2.8.9 | None | crop | 1 > 1 | 0 |15:35:17| 124.248.238.194 | hk | 9001 | 9051 |0.2.8.9 | None | beach | 1 > 1 | 0 |15:39:10| 124.248.238.197 | hk | 9001 | 9051 |0.2.8.9 | None | queen | 1 > 1 | 0 |15:51:44| 124.248.229.142 | hk | 9001 | 9051 |0.2.8.9 | None | castle | 1 > 1 | 0 |17:27:16| 103.44.66.2 | None | 9001 | 9051 |0.2.8.9 | None | tennis | 1 > 1 | 0 |17:39:25| 103.27.126.28 | hk | 9001 | 9051 |0.2.8.9 | None | court | 1 > 1 | 0 |17:48:57| 103.44.66.4 | None | 9001 | 9051 |0.2.8.9 | None | waterfall | 1 > 1 | 0 |17:58:26| 103.44.66.5 | None | 9001 | 9051 |0.2.8.9 | None | camp | 1 > 1 | 0 |18:06:15| 103.27.126.27 | hk | 9001 | 9051 |0.2.8.9 | None | fighter | 1 > 1 | 0 |18:25:53| 43.242.174.35 | hk | 9001 | 9051 |0.2.8.9 | None | burn | 1 > 1 | 0 |18:38:11| 43.242.174.36 | hk | 9001 | 9051 |0.2.8.9 | None | leisure | 1 > 1 | 0 |18:46:30| 43.242.174.37 | hk | 9001 | 9051 |0.2.8.9 | None | clerk | 1 > 1 | 0 |18:55:48| 150.107.44.3 | hk | 9001 | 9051 |0.2.8.9 | None | servant | 1 > 1 | 0 |19:00:45| 150.107.44.2 | hk | 9001 | 9051 |0.2.8.9 | None | mankind | 1 > Fingerprints: > 25214D40CD1747A06FA2E695E48AED0E988ABA61,25214D43D1FDAF97EBCB68C282D7AA247A1BC487,25214D43CF6621FD4FBEB6FC654A29702965094D,25214D42EC6083C31E1709D86CEBEFFCD4BE1958,7053866617EA5FD3AC0B5D4EB8CE6EC792F99AF5,AB559BE305A7A63962944D32A69AEB2AF9EAC7DC,AB559BE25926F720890BDAE88407E1A676883304,AB559BE2CA986C0EDEFBD78B48621DD36C349AD4,AB559BE02A323465AB8C3D0BB18EA04A1F13E32F,203281E1A349FAA241B6A66456A5AFD1C5B49410,203281E3EBC4E8AB7F040AD8A86B8767A5F6F849,203281E0784DE0DFB5C39C714BBBBA39E76AAA61,203281E37E44A5ABCEA7880DA47895197E92D546,203281E1226E3C1EEBA522409109C847AB14A2B9,203281E27627443DB6FE5E06250DDDB6D9718A0C >

5 14

I have an Alleged family member
by Arisbe 28 Feb '17

28 Feb '17

Hello all, I run a variety of Tor relays--most on VPS hosts. I recently added a small relay and updated my family members. Strangely, this last relay is tagged as an "alleged family member," even on itself [0]. It has been like this for over a month. I can't detect a typo. Any suggestions? [0] 04C095E0DAB8C28BC433677C4AE8F65CB7D7083C

4 5

Lost guard flag, IPv6 problem?
by Sebastian Niehaus 26 Feb '17

26 Feb '17

Hi, my relay lost its guard flag and I don't know what might be the reason. The flag was lost before the last reboot (due to kernel upgrade) https://atlas.torproject.org/#details/7A32C9519D80CA458FC8B034A28F5F6815649… Any ideas on that? What bothers me too is: there is no IPv6 "Dir Address" although I did not change configuration. Some days ago, I hat IPv6 connectivity issues but they are resolved. Any hints on this? I am not sure if those problems are related to each other ... Thanks, Sebastian

2 1

ansible relayor v0.2.1 released
by nusenu 26 Feb '17

26 Feb '17

Hi, relayor v0.2.1 has been released. blog post to get you started: https://medium.com/@nusenu/deploying-tor-relays-with-ansible-6612593fa34d GPG signing key fingerprint: pub 4096R/4D705DE9 2016-02-11 [expires: 2018-07-30] Key fingerprint = A7B5 DB91 CE04 C9E0 BE66 446B 8CBE 52BD 4D70 5DE9 regards, nusenu

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays February 2017