tor-relays

tor-relays@lists.torproject.org

36 participants
4815 discussions

Disable CellStatistics to reduce RAM usage
by teor 09 Feb '18

09 Feb '18

Hi, If your relay is using too much RAM, please disable CellStatistics. (It's not on by default.) For more details, please see: https://trac.torproject.org/projects/tor/ticket/25141 https://trac.torproject.org/projects/tor/ticket/24806#comment:13 T

3 3

High processor usage - just curious
by Gary Smith 08 Feb '18

08 Feb '18

Hi, I have noticed that after a few minutes of becoming online, and randomly perhaps a couple of times every hour (??) tor uses 100 % processor on all cores for about 40/50 seconds. I am curious what is tor doing internally to need so much power? There is normally isn't more than 4 mbits going through my relay, I noticed this a while back on htop before the December load increase and on previous versions so this has got to be an "internal thing". There is no log entry when this happens. I do not think it is a bug I am just curious why it needs this much computational power, Thanks.

3 5

Exit Relay Up
by Conrad Rockenhaus 05 Feb '18

05 Feb '18

Hello All, I just brought up my third relay, ConradsOVHRelay03, as an exit. I appreciate the feedback that everyone provided me with before and I hope that this relay is configured perfectly. I’m glad to add more bandwidth to the cause. Thanks, Conrad

2 1

relayor v0.3.1 is released
by nusenu 05 Feb '18

05 Feb '18

Hi, relayor v0.3.1 has been released. https://github.com/nusenu/ansible-relayor Whether you run a single or many relays, relayor helps you with running relays with minimal effort (automate everything). Introduction to get you started: https://medium.com/@nusenu/deploying-tor-relays-with-ansible-6612593fa34d Main benefits for a tor relay operator ====================================== * automation - no more manual setup tasks * security: offline Ed25519 master keys every tor instance is run with a distinct user * automatically makes use of IPv6 IPs (if available) * automatic tor instance generation (two by default - configurable) * enables tor's Sandbox feature by default on Debian-based systems * easily choose between alpha/non-alpha releases * easily restore a relay setup * easily choose between exit relay/non-exit relay mode * automatic deployment of a tor exit notice html page via tor's DirPort * automatic MyFamily management Supported Operating Systems ---------------------------- Debian 8, 9 and Debian Testing OpenBSD 6.2 FreeBSD 10.4, 11.1 HardenedBSD 11.1 Ubuntu 16.04 CentOS 7 Fedora 27 Changes since v0.3.0: ------------------------------ - support custom tor-exit-notice.html files (fixes #140) - increase tor_alpha_version: 0.3.2.x -> 0.3.3.x - Debian/Ubuntu: add support for tor nightly builds - implement per-instance ExitRelay settings (fixes #146) - make tor package state configurable (latest vs. present) regards, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

1 0

Relays not in cached consensus
by Tyler Durden 05 Feb '18

05 Feb '18

Hi Just ~3 weeks before the 34C3, two of our newer Exits were thrown out of the consensus weight and since than never came back in. I'm talking about: geri (geri.enn.lu) 93FAB6F91C2EF33D0ACEEF7448177FCA2CEB99A0 freki (freki.enn.lu) C8AB1B2AF0CBAAE3611A814B4C7D38DCE0CBFEB4 We tried to purge the Tor installation, generate completely new keys, switched to alpha versions, switched back to stable, waited for weeks but it's always the same result. Only the authority servers moria1, longc. and dizum seem to "recognise" our exits. The logs say the same for every authority server except the 3 ones mentioned above: [info] handle_response_fetch_desc(): Received http status code 404 ("Servers unavailable") from server '154.35.175.225:80' while fetching "/tor/server/d/[__redacted__] I'll try again soon. Any ideas how to fix this? Greetings -- Frënn vun der Ënn A.S.B.L. (NGO) e. virii(a)enn.lu (GPG: 0xce8c12f32a2cf11b) t. +352-27-40-20-30-4 w. https://enn.lu/

2 2

looking for a contact possibility to reach frecy's operator
by nusenu 05 Feb '18

05 Feb '18

if you are the operator of this relay please drop me an email https://atlas.torproject.org/#details/28AB7201E1036C3B8AC7CE2E99945F8A49887… -- https://mastodon.social/@nusenu twitter: @nusenu_

1 0

chutney debugging: (Sandbox) Caught a bad syscall attempt (syscall kill)
by tor7 04 Feb '18

04 Feb '18

I'm trying chutney to measure my CPU, but it does not appear to work: chutney/tools/test-network.sh --flavour basic-min --data-bytes 104857600 test-network.sh: using CHUTNEY_DNS_CONF '/dev/null' test-network.sh: no $TOR_DIR, chutney will use $PATH for tor binaries test-network.sh: $CHUTNEY_PATH not valid, using this script's location Using Python 2.7.14 Sending SIGINT to nodes Waiting for nodes to finish. Removing stale lock file for test000a ... Removing stale lock file for test001a ... bootstrap-network.sh: bootstrapping network: basic-min Using Python 2.7.14 NOTE: creating '/home/user/chutney/tools/../net/nodes.1517749361', linking to '/home/user/chutney/tools/../net/nodes' Creating identity key /home/user/chutney/net/nodes/000a/keys/authority_identity_key for test000a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/user/chutney/net/nodes/000a/keys/authority_identity_key -s /home/user/chutney/net/nodes/000a/keys/authority_signing_key -c /home/user/chutney/net/nodes/000a/keys/authority_certificate -m 12 -a 127.0.0.1:7000 Creating identity key /home/user/chutney/net/nodes/001a/keys/authority_identity_key for test001a with tor-gencert --create-identity-key --passphrase-fd 0 -i /home/user/chutney/net/nodes/001a/keys/authority_identity_key -s /home/user/chutney/net/nodes/001a/keys/authority_signing_key -c /home/user/chutney/net/nodes/001a/keys/authority_certificate -m 12 -a 127.0.0.1:7001 Using Python 2.7.14 Starting nodes Using Python 2.7.14 test000a is running with PID 1001 test001a is running with PID 1004 test002r is running with PID 1007 test003c is running with PID 1010 4/4 nodes are running Waiting 20 seconds for a consensus containing relays to be generated... Running 1 verify rounds... Using Python 2.7.14 Verifying data transmission: (retrying for up to 60 seconds) Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Connecting: Exit to 127.0.0.1:4747 via client localhost:9003 Transmitting Data: Transmission: Failure Set CHUTNEY_DEBUG to diagnose. Completed 1 of 1 verify rounds. Using Python 2.7.14 Sending SIGINT to nodes Waiting for nodes to finish. Removing stale lock file for test000a ... Removing stale lock file for test001a ... Removing stale lock file for test002r ... Removing stale lock file for test003c ... Summary: nodes Detail: chutney/tools/warnings.sh /home/user/chutney/tools/../net/nodes.1517749361 Warning: OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1010007f: OpenSSL 1.1.0g 2 Nov 2017; running with 1010007f: OpenSSL 1.1.0g-fips 2 Nov 2017). Number: 4 ------------------------ open tor listener (after starting chutney) tcp 0 0 0.0.0.0:7000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:7001 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:7002 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8001 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8002 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5002 0.0.0.0:* LISTEN there is no tor on tcp port 9003, should there be one? grep 9003 chutney/net/nodes/*/torrc chutney/net/nodes/003c/torrc:SocksPort 9003 manually starting that torrc file (after setting RunAsDaemon to 0) gives: tor -f /home/user/chutney/net/nodes/003c/torrc --Log "info stdout" (Sandbox) Caught a bad syscall attempt (syscall kill) tor(+0x1853fa)[0x6141342b23fa] /lib64/libc.so.6(kill+0x7)[0x75008527ace7] /lib64/libc.so.6(kill+0x7)[0x75008527ace7] tor(+0x1c3bab)[0x6141342f0bab] /lib64/libevent-2.0.so.5(event_base_loop+0x7a9)[0x7500863853f9] tor(do_main_loop+0x29d)[0x61413417b78d] tor(tor_main+0xe25)[0x61413417e5a5] tor(main+0x19)[0x614134177009] /lib64/libc.so.6(__libc_start_main+0xea)[0x75008526488a] tor(_start+0x2a)[0x61413417705a] Tor version 0.3.1.9 upgrading to 0.3.2.9 solves the issue. https://trac.torproject.org/projects/tor/ticket/24198

2 1

nyx question on info on top right side, present on CentOS, missing on Debian.
by Stijn Jonker 04 Feb '18

04 Feb '18

Hi All, I initially went to the nyx website to find the right forum to ask questions. I understood this is the one :-), if not apologies. So I'm running two relays, one is running on CentOS7, the other Debian Stretch. On both I have nyx (2.0.4) installed. The "Debian" one is missing the CPU, Exit policy etc info. It's not tor version specific, as I recently upgraded the tor software on the nodes regularly. So on the CentOS node I see this on the top at the right; cpu: 61.3% tor, 5.0% nyx mem: 371 MB (12.4%) pid: 1279 uptime: 02:59:09 fingerprint: 328E54981C6DDD7D89B89E418724A4A7881E3192 exit policy: reject *:* On the Debian node it's simply not printing any of these three lines. I can't find in the (debug) logging whether an utility or library is missing. It's nothing major, but annoying. Especially with the new alpha releases it's nice to keep an eye out on mem/cpu. Does anyone have an idea what the trick is to get it to work on debian? -- CentOS info: [user@tornode ~]$ tor --version Tor version 0.3.3.1-alpha (git-de8bc9eed6eaadfc). [user@tornode ~]$ nyx --version nyx version 2.0.4 (released November 5, 2017) [user@tornode ~]$ uname -a Linux tornode.sjc.nl 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- Debian info: [maint@tornode2 ~]$ tor --version Tor version 0.3.3.1-alpha-dev (git-9e48338a12fd1fef+0f23e7e96). [user@tornode2 ~]$ nyx --version nyx version 2.0.4 (released November 5, 2017) [user@tornode2 ~]$ uname -a Linux tornode2 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux [user@tornode2 ~]$ lsb_release -c Codename: stretch Thx, Stijn

3 5

Re: [tor-relays] atlas.torproject.org: missing updated information for relays
by nusenu 04 Feb '18

04 Feb '18

it is back now. -- https://mastodon.social/@nusenu twitter: @nusenu_

1 0

tor cpu / MBit/s benchmarks
by tor7 04 Feb '18

04 Feb '18

Hello! I'd like to collect some samples for how many MBit/s on a single tor daemon are possible on given CPU model before it is limited by the CPU. If your single tor daemon routes more than 350 MBit/s in each direction and you are running on bare metal it would be awesome if you could share your - CPU model (ideally a link to ark.intel.com if it is an intel cpu) - avg. daily CPU usage (ie. from munin graphs) - actual traffic (MBit/s) - optional: relay fingerprint thank you! tor7

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays