Hello, I run a relay for almost 10 days. I wonder if my configuration is correct as I don't see the expected behavior from https://blog.torproject.org/blog/lifecycle-of-a-new-relay Indeed, my consensus weight and the number of connections dropped after 8 days, from 0.0040% to 0.0012% and from 2000 to 300 connections respectively. Since then, I've such messages in arm: [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. [4 duplicates hidden] [NOTICE] We tried for 15 seconds to connect to '[scrubbed]' using exit <fingerprint> at <ip>. Retrying on a new circuit. I was expecting to get a guard flag with an increasing consensus weight involving a drop of the number of connections. So far, I have the following flags: Fast, HSDir, Running, Stable, V2Dir, Valid. Is that an evidence something is not running properly? Best, Clèm
What's your connection speed? I've been running a relay for almost a month, but I highly doubt I'll get the guard flag because I can barely push 1Mbps. On Apr 7, 2016 10:32 AM, "Clément Février" <clement@forumanalogue.fr> wrote:
Hello,
I run a relay for almost 10 days. I wonder if my configuration is correct as I don't see the expected behavior from https://blog.torproject.org/blog/lifecycle-of-a-new-relay Indeed, my consensus weight and the number of connections dropped after 8 days, from 0.0040% to 0.0012% and from 2000 to 300 connections respectively. Since then, I've such messages in arm:
[NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. [4 duplicates hidden] [NOTICE] We tried for 15 seconds to connect to '[scrubbed]' using exit <fingerprint> at <ip>. Retrying on a new circuit.
I was expecting to get a guard flag with an increasing consensus weight involving a drop of the number of connections.
So far, I have the following flags: Fast, HSDir, Running, Stable, V2Dir, Valid.
Is that an evidence something is not running properly?
Best, Clèm
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
While I don't have any actual numbers, I'm pretty sure you won't be getting a guard flag with that kind of speed. Actually, I don't think you'll get much traffic at all with that slow of a relay, especially since the recommended upload speed is 2Mbps (1600kBytes/s). At any rate, you'll still get some traffic, and you can use the relay as a local proxy for your home network. On 04/07/2016 01:11 PM, Clément Février wrote:
On 07/04/2016 17:37, Tristan wrote:
What's your connection speed? I've been running a relay for almost a month, but I highly doubt I'll get the guard flag because I can barely push 1Mbps. I advertise 500kBytes/s with a "burst" at 750kB/s (my max upload limit).
Best, Clèm
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
While I don't have any actual numbers, I'm pretty sure you won't be getting a guard flag with that kind of speed. Actually, I don't think you'll get much traffic at all with that slow of a relay, especially since the recommended upload speed is 2Mbps (1600kBytes/s).
No, 2Mbps are 250KBps, 2 Megabit = 250 Kilobyte (as 8 Megabit are 1 Megabyte). Recommended minimum upload speed to run a relay is 100Kilobyte/s, so 1Mbps is already enough to run a relay. [1] To be a relay, your bandwidth has to be at least 250KB/s. [2] [1] https://blog.torproject.org/blog/lifecycle-of-a-new-relay#comment-34637 [2] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2140
Am 07.04.16 um 20:21 schrieb Michael Armbruster:
While I don't have any actual numbers, I'm pretty sure you won't be getting a guard flag with that kind of speed. Actually, I don't think you'll get much traffic at all with that slow of a relay, especially since the recommended upload speed is 2Mbps (1600kBytes/s).
No, 2Mbps are 250KBps, 2 Megabit = 250 Kilobyte (as 8 Megabit are 1 Megabyte). Recommended minimum upload speed to run a relay is 100Kilobyte/s, so 1Mbps is already enough to run a relay. [1]
To be a relay, your bandwidth has to be at least 250KB/s. [2]
I meant "to be a guard" here, sorry
[1] https://blog.torproject.org/blog/lifecycle-of-a-new-relay#comment-34637 [2] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2140
My mistake, 2Mbits does mean 250 KBytes. I get confused when converting bits/bytes. Sorry for that confusion. I found where my numbers came from: https://www.torproject.org/docs/tor-relay-debian.html.en "If you have at least 250 kilobytes/s each way, please help out Tor by configuring your Tor to be a relay too." This is where I understood 250KBytes to be a suggested minimum, which is still slightly confusing since 100KBytes is the minimum for a "fast" relay flag. On 04/07/2016 01:25 PM, Michael Armbruster wrote:
Am 07.04.16 um 20:21 schrieb Michael Armbruster:
While I don't have any actual numbers, I'm pretty sure you won't be getting a guard flag with that kind of speed. Actually, I don't think you'll get much traffic at all with that slow of a relay, especially since the recommended upload speed is 2Mbps (1600kBytes/s). No, 2Mbps are 250KBps, 2 Megabit = 250 Kilobyte (as 8 Megabit are 1 Megabyte). Recommended minimum upload speed to run a relay is 100Kilobyte/s, so 1Mbps is already enough to run a relay. [1]
To be a relay, your bandwidth has to be at least 250KB/s. [2] I meant "to be a guard" here, sorry
[1] https://blog.torproject.org/blog/lifecycle-of-a-new-relay#comment-34637 [2] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2140
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
As a CCNP R&S and Security: STOP using bytes in networking. Networking is measured in bits for fluffys sake. 2016-04-07 20:32 GMT+02:00 SuperSluether <supersluether@gmail.com>:
My mistake, 2Mbits does mean 250 KBytes. I get confused when converting bits/bytes. Sorry for that confusion.
Why not, but people using their computer usually see bytes and octets... When they are downloading a file, the speed is Mo/Ko, so... Yes it can be confusing ! Le 08/04/2016 01:43, Markus Koch a écrit :
As a CCNP R&S and Security: STOP using bytes in networking. Networking is measured in bits for fluffys sake.
2016-04-07 20:32 GMT+02:00 SuperSluether <supersluether@gmail.com>:
My mistake, 2Mbits does mean 250 KBytes. I get confused when converting bits/bytes. Sorry for that confusion.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Its in bytes because it is a file. You do have a 100/1000 mBIT ethernetcard and a 7/16 mBIT adsl/cable/whatever internet connection while surfing over your 52 mBIT wlan router. 2016-04-08 8:27 GMT+02:00 Pierre L. <petrus@miosweb.mooo.com>:
Why not, but people using their computer usually see bytes and octets... When they are downloading a file, the speed is Mo/Ko, so... Yes it can be confusing !
Le 08/04/2016 01:43, Markus Koch a écrit :
As a CCNP R&S and Security: STOP using bytes in networking. Networking is measured in bits for fluffys sake.
2016-04-07 20:32 GMT+02:00 SuperSluether <supersluether@gmail.com>:
My mistake, 2Mbits does mean 250 KBytes. I get confused when converting bits/bytes. Sorry for that confusion.
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
Using vnstat on the linux box to show bandwidth used, For example, for 1 day, it shows : rx tx total avg. rate 56.64 GiB 57.79 GiB 114.44 GiB 1.36MiB/s So, to understand easily by a fun and cool example... It's possible to win the famous Tor TShirt if your relay has a bandwidth average >=500KBytes/s during 2 months. So with those 1.36MiB/s running for 2 months, will it be ok to claim the "precious" ? I'm right, it can be confusing, mo, Mo, MiO, Mio Le 08/04/2016 09:06, Markus Koch a écrit :
Its in bytes because it is a file. You do have a 100/1000 mBIT ethernetcard and a 7/16 mBIT adsl/cable/whatever internet connection while surfing over your 52 mBIT wlan router.
2016-04-08 8:27 GMT+02:00 Pierre L. <petrus@miosweb.mooo.com>:
Why not, but people using their computer usually see bytes and octets... When they are downloading a file, the speed is Mo/Ko, so... Yes it can be confusing !
Le 08/04/2016 01:43, Markus Koch a écrit :
As a CCNP R&S and Security: STOP using bytes in networking. Networking is measured in bits for fluffys sake.
2016-04-07 20:32 GMT+02:00 SuperSluether <supersluether@gmail.com>:
My mistake, 2Mbits does mean 250 KBytes. I get confused when converting bits/bytes. Sorry for that confusion.
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
On Thu, Apr 07, 2016 at 08:21:55PM +0200, Michael Armbruster wrote:
To be a relay, your bandwidth has to be at least 250KB/s. [2]
[2] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2140
Thanks! That is a bug in the dir-spec. It looks like it never got updated when we merged the changes in https://trac.torproject.org/projects/tor/ticket/12690 See https://lists.torproject.org/pipermail/tor-commits/2014-July/077778.html for what changed in the code (this went into 0.2.5.6-alpha). I've opened a ticket and we can follow it there: https://trac.torproject.org/projects/tor/ticket/18756 Thanks! --Roger
In my opinion, Tor should update the "fast" flag as well. 100KBytes/s isn't very fast by today's standards. On 04/07/2016 01:39 PM, Roger Dingledine wrote:
On Thu, Apr 07, 2016 at 08:21:55PM +0200, Michael Armbruster wrote:
To be a relay, your bandwidth has to be at least 250KB/s. [2]
[2] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2140 Thanks! That is a bug in the dir-spec. It looks like it never got updated when we merged the changes in https://trac.torproject.org/projects/tor/ticket/12690 See https://lists.torproject.org/pipermail/tor-commits/2014-July/077778.html for what changed in the code (this went into 0.2.5.6-alpha).
I've opened a ticket and we can follow it there: https://trac.torproject.org/projects/tor/ticket/18756
Thanks! --Roger
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Thu, Apr 07, 2016 at 01:15:45PM -0500, SuperSluether wrote:
especially since the recommended upload speed is 2Mbps (1600kBytes/s).
On https://www.torproject.org/docs/tor-relay-debian.html I wrote "at least 250 kilobytes/s each way". So that's 2 megabits per second. Your above confusion is why nobody should ever write "b" or "B" in this day and age. And to add more content to this mail, here are moria1's cutoffs at this moment for flag assignment: Apr 07 13:50:01.387 [info] dirserv_compute_performance_thresholds(): Cutoffs: For Stable, 1463591 sec uptime, 557597 sec MTBF. For Fast: 102 kilobytes/sec. For Guard: WFU 98.000%, time-known 691200 sec, and bandwidth 5250 or 4510 kilobytes/sec. We have enough stability data. That log line is misleading a bit, because the units of weight in the consensus are not really kilobytes/sec anymore. But what it means is that moria1 doesn't vote the Guard flag for you unless the measured consensus weight it's voting for you is 5250 or 4510 (that number depends on whether exit capacity is scarce in the network at this moment -- I haven't checked if that's the case right now). Hope that helps, --Roger
On 4/7/16, Roger Dingledine <arma@mit.edu> wrote:
Your above confusion is why nobody should ever write "b" or "B" in this day and age.
Re confusion... as said before with reference links to official standards... These days, formally... "b" bit and "B" byte are well defined context. "k" is 1000, and "Ki" is 1024, and "K" is nothing at all. Further, network speeds should not be in binary because that is not the underlying native decimal accounting of commercial router/switch/isp/etc network hardware and line speeds which they ultimately are billed upstream [and bill downstream] by whether represented otherwise or not. There are also unambiguous locale-free date and time representations. https://en.wikipedia.org/wiki/IEC_80000-13 https://en.wikipedia.org/wiki/IEEE_1541-2002 https://en.wikipedia.org/wiki/Binary_prefix https://en.wikipedia.org/wiki/ISO_8601 Use appropriately.
participants (9)
-
Clément Février -
grarpamp -
Markus Koch -
Michael Armbruster -
Pierre L. -
Roger Dingledine -
SuperSluether -
Thomas Braun -
Tristan