[tor-relays] New Tor node operator hibernation question
Hello, I am a new Tor relay operator, and have setup my first relay. It's been running as a Tor middle relay for about 10 days now, and it's been running solid. It has the stable, guard, fast, running, and valid flags. I have my AccountingMax quota set to start at the first of each month at midnight. However, just past midnight on 07-01 Tor said it was going to hibernate until 07-05. This had me confused as I was only about half way through my monthly quota setup in AccountingMax for June, and my hosting provider reset the data on the first at midnight. I read the manual page about AccountingMax again, and it appears this may have been normal behavior. However before I read the manual page, I forced my relay to wake up out of that hibernation. It appears to be operating normally right now. However, I am wondering if this will cause any issues this month, or in future months? Also, can someone explain if the hibernation of 5 days was normal behavior to begin with. Thank you___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] One IPv4 address, 1Gbit connection
Tom, Why not run multiple tor relays on different ports on the same IPv4 address? For example, you could run 6 relays on 6 different ports on your IPv4 address (6 x 180 Mpbs 1 Gbps). This would also utilise your 4 cores much more efficiently than running 2 relays (each relay will only ever use 1 core for most operations). Tim Mon, 30 Jun 2014 14:48:59 +0200 Christian Dietrich christian.d.dietr...@gmail.com: Hi there, You will never be able to utilize the whole gigabit connection, at least with the current tor version. I'm also running 2 tor nodes (000myTOR) on a single machine (3rd gen Core i, Quad Core /w AES-NI) on an single IP, reaching ~1.3 Gbit/s on an 1000 Base-T FD connection. Since you do not use hardware accelerated crypto, your transfer speed should be much lower. Anway my relays are also cpu limited due to the fact that tor isn't really utilizing much more than one cpu core. - Christian 2014-06-30 13:05 GMT+02:00 Tom van der Woerdt i...@tvdw.eu: Hi, I'm running a Tor exit node on a 1gbit connection. Currently it's maxing at about 180Mbit/s (both ways, so 360Mbit/s) per instance, and I'm running two instances. That's not really using the connection well. The box has 4 cores (no AES-NI) and I'm looking for ways to utilize the other 640Mbit/s. Sadly it's not possible to get more IPv4 addresses on this box. I do however have access to a big range of IPv6 addresses. Can I somehow run more Tor instances on this box by utilizing those IPv6 addresses? Or are there other ways to optimize the throughput and get closer to that 1Gbit? Tom ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] One IPv4 address, 1Gbit connection
My apologies - I wasn't aware of the 2 relays per IP restriction. Is it for security reasons? On 1 Jul 2014, at 23:48 , Roman Mamedov r...@romanrm.net wrote: On Tue, 01 Jul 2014 22:36:10 +1000 Tim t_e...@icloud.com wrote: Tom, Why not run multiple tor relays on different ports on the same IPv4 address? For example, you could run 6 relays on 6 different ports on your IPv4 address (6 x 180 Mpbs 1 Gbps). This would also utilise your 4 cores much more efficiently than running 2 relays (each relay will only ever use 1 core for most operations). Because more than two relays per IPv4 address is ignored by the network; and that was the whole point of the question. I suggested some time ago that with the scarcity of IPv4 *and* abundance of multi-core CPUs that the Tor developers should really consider raising the relays-per-IP limit from 2 to at least 3 or 4. Sure one can use IPv6, but I doubt there's any serious amounts of traffic on IPv6 via Tor, so it will not help with the original request to do something which would help better utilize the full available bandwidth. -- With respect, Roman ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] optimize performance of a relay running on a VM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/1/2014 10:07 PM, Random Tor Node Operator wrote: On 07/01/2014 08:46 PM, s7r wrote: I have multiple relays running on the following systems: - vmware vsphere virtualization technology - 100 mbps port - 1GB dedicated RAM - 2.6 Ghz 1 core CPU dedicated - OS: FreeBSD 10.0 Release amd64 or Debian Stable - DO NOT KNOW IF I HAVE AES-NI SUPPORT OR HOW TO ACTIVATE IT (?) $ cat /proc/cpuinfo | grep aes It does not return anything. I have the proc folder, but there is no cpuinfo file in it. Here: root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No such file or directory If it returns a string of instruction sets, your CPU has the AES-NI instruction set. If it returns nothing, it doesn't. Currently atlas shows 3-4-5 MB/s advertised bandwidth for these relays. Arm shows between 600 and 1200 concurrent circuits (total of inbound, outbound and exit) and average traffic consumption is 5-6 TB per month (total both download and upload). I think this can be improved, but how? What does the CPU usage of the tor process look like? PID USERNAMETHR PRI NICE SIZERES STATETIMEWCPU COMMAND 675 _tor 2 200 130M 126M sbwait 567:31 7.96% tor Uses maximum 10-12% of the available CPU. Uses maximum 150 - 160 MB of RAM. (~15%) How long have your relays been running? It takes a while until a relay reaches a steady state. [1] Little over 2 months if I recall correct. Exit, Guard, Stable and Fast. Can you tell us the fingerprints of your relays? here is one I am freebie hired to maintain: 6C36F9ACBA57AC9C10DBC39D330CFA337522E72B At least in terms of your hardware, you should be able to roughly saturate your 100 Mbit/s line. [1] https://blog.torproject.org/blog/lifecycle-of-a-new-relay ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Thank you for prompt reply and looking forward for your help. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJTswsDAAoJEIN/pSyBJlsRws0IAItoJ1gQxlfKwmBIuUHgsAyJ FA2F1s/N4tU4zrC8oLQEayI8nKNRyRK8armLRRm1fDOR5ZomRov/ThnJA55boZv/ RF8p4aMNSAehOJAGgRbUwFmjL4NTuvZBEeC8TOHrDSKX6SB2R210RhyucBpRID3C l2D7nITPnqGVM3zeZ3d79LMWGo9MQ6CBYHosE4MmmVCwYPI3abRDXNLWEdii7AvR 1qt24HQeartxf1AIiJRph05/PlZRbh0RkdATz+lYeAhwz0ryRkncYbU8SRkK5jnf s5VwqDqOuUDp1k7Grn7f7SERwCzlNKWhg1kLfxKWevBL4Q8WX47Xvjaw827dPUg= =mYES -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] optimize performance of a relay running on a VM
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No such file or directory According to a stackoverflow page [2], you can look for hints indicating the existence of AES-NI support in sysctl hw and /var/run/dmesg.boot PID USERNAMETHR PRI NICE SIZERES STATETIMEWCPU COMMAND 675 _tor 2 200 130M 126M sbwait 567:31 7.96% tor Uses maximum 10-12% of the available CPU. Uses maximum 150 - 160 MB of RAM. (~15%) okay, so CPU doesn't seem to be a bottleneck, as expected. You could try downloading a large (some 100 MBs) file from a fast server via wget to see whether you can saturate your downstream. here is one I am freebie hired to maintain: 6C36F9ACBA57AC9C10DBC39D330CFA337522E72B It is an Exit relay. I am not sure, maybe Tor is designed in a way that Exits are strongly preferred for Exit connections, so they get less traffic for HSDir/V2Dir requests or for being a Rendezvous Point or Introduction Point for Hidden Services. That is mostly speculation on my part though. I never had any Exit relays on my own. Probably the Tor Path Specification [3] has the answer to that question. Your relay seems to be the only one in that /16 subnet, so that wouldn't be a reason for less-than-normal traffic. [2] http://stackoverflow.com/questions/4083848/what-is-the-equivalent-of-proc-cpuinfo-on-freebsd-v8-1 [3] https://gitweb.torproject.org/torspec.git?a=blob_plain;hb=HEAD;f=path-spec.txt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTsxYkAAoJEJe61A/xrcOQ1WUQAKzb4xSA8Wz0u3T4sCn2Q41g URTA4Q9OGDxRvYpO2I9cXOuu4pj2g+jWsxOH1uX8g1O6uY7u6n5cYj0FYczbDSJm wn9ySxIo8wJAZCTStJmXQhgm9oceq7EDgiVsRQAXQilkv3i2JnfToNLMH80vMuKH x6Wj6lfzEWs2/8NG/WxNmJuv4O7w/mPJ1LeCqLsuL8O3ni03Ql0iPnohyhbQrJCo vAbKaj1ix65eSNahLqcH53MF3x+FkkG0ULTgWebjCg731kqVFOzsrRQQY4oZXo+k +fx+7kodjqQdQ7xSRpaTBe/15NE8Xk8hT9Ib9jVQ9Zyo19EcP6NIxnYC+zJD2G++ xQtcpur6N5XZCruuC+GoUsdYB/6lrLJHJ+SaqXachhEfqcXm1DaIH0wJb7Zre2Jf 4eS/H/Fp0+msKFHq3ElL7TcnxpMOMUkoAp4d7jbi8v/0u5DHuMRQDVTlIfpSX3fJ HMBQo9K1jf1iInCx7vpLFe7f+m5tH+PRTME8ZBTJ6PnAUbrrQW4khBF8P3J6gqm9 1DTH16BF+B2zNhQhyKI9c8T6CFIxXdnTwUAYFwHA8GQII6qP2M2ykK9ELpN1y/o8 dFTOMe017L4jM+73yhoNIddbGoCqBlIGu+1vv/OK/uk+s5Lmh3fveajOsECAcBpq HzlYGmmOy6UuWsClZL+X =fnHk -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bandwidth usage for an established relay node
Hi Kali, It depends on your network speed. Expect it to use roughly 80% of your maximum speed on average, so if you have a 50Mbit/s up/down connection you will be uploading 13TB and downloading 13TB. For high speed relays this might differ a bit if your bottleneck becomes the CPU. Tom Kali Tor schreef op 01/07/14 23:16: Hi all, Curious as to how much bandwidth a stable, well established relay node will chew through in a month on an average? Anyone has any figures? -kali- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays smime.p7s Description: S/MIME-cryptografische ondertekening ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] Bandwidth usage for an established relay node
Hi all, Curious as to how much bandwidth a stable, well established relay node will chew through in a month on an average? Anyone has any figures? -kali- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Bandwidth usage for an established relay node
Phew.. I wish I can find a VPS that gives me that much bw to burn on a reasonable price... Currently running a 1.5TB (up+down) relay and wanting to do more. -kali- On Tuesday, July 1, 2014 9:27 PM, Tom van der Woerdt i...@tvdw.eu wrote: Hi Kali, It depends on your network speed. Expect it to use roughly 80% of your maximum speed on average, so if you have a 50Mbit/s up/down connection you will be uploading 13TB and downloading 13TB. For high speed relays this might differ a bit if your bottleneck becomes the CPU. Tom Kali Tor schreef op 01/07/14 23:16: Hi all, Curious as to how much bandwidth a stable, well established relay node will chew through in a month on an average? Anyone has any figures? -kali- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] optimize performance of a relay running on a VM
On Tue, Jul 1, 2014 at 3:24 PM, s7r s...@sky-ip.org wrote: dedicated RAM - 2.6 Ghz 1 core CPU dedicated - OS: FreeBSD 10.0 Release amd64 - DO NOT KNOW IF I HAVE AES-NI SUPPORT OR HOW TO ACTIVATE IT (?) It does not return anything. I have the proc folder, but there is no cpuinfo file in it. Here: root@tor:/ # cat /proc/cpuinfo | grep aes cat: /proc/cpuinfo: No such file or directory That's because FreeBSD is not Linux, its proc is limited to procfs(5) with non process info/knobs in sysctl(8), nor is it really necessary to mount proc. Also, 'aes' is presented in CAPS. That single core might be old enough to not have it. Check: /var/run/dmesg.boot http://svnweb.freebsd.org/ports/head/misc/cpuid/ [also available via ftp package] openssl speed aes ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
