Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Should I run multiple relays on the same machine/IP ?
Thanks !
How long since you put the node online? Den 11 okt 2014 08:05 skrev "Blaise Gagnon" quebecfibe@gmail.com:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Should I run multiple relays on the same machine/IP ?
Thanks !
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
July 18th 2014
2014-10-11 2:09 GMT-04:00 Joakim Bülow joakim.bulow@gmail.com:
How long since you put the node online? Den 11 okt 2014 08:05 skrev "Blaise Gagnon" quebecfibe@gmail.com:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Should I run multiple relays on the same machine/IP ?
Thanks !
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 Sat, Oct 11, 2014 at 02:05:24AM -0400, Blaise Gagnon wrote:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Hi Blaise,
Thanks for running a relay!
It looks like you're currently peaking at a little over 2MB (with a mean of ~1MB)[0][1].
I also see that the relay is currently hibernating. This will certainly impact the amount of bandwidth you use. Did you configure MaxAdvertisedBandwidth?
Below is what the network knows about your relay (with some irrelevant details removed).
$ curl https://onionoo.torproject.org/details?fingerprint=5EF740BB88C75915F8316DFEC... { "version":"1.1", "relays_published":"2014-10-11 05:00:00", "relays":[ { "nickname":"QuebecFibe", "fingerprint":"5EF740BB88C75915F8316DFEC8F1C8631FF26F12", [...] "last_seen":"2014-10-11 06:00:00", "last_changed_address_or_port":"2014-10-07 07:00:00", "first_seen":"2014-07-17 17:00:00", "running":true, "flags":["Fast","Running","V2Dir","Valid"], [...] "consensus_weight":5950, "host_name":"69.159.127.80", "last_restarted":"2014-10-08 06:31:26", "bandwidth_rate":26214400, "bandwidth_burst":26214400, "observed_bandwidth":3512594, "advertised_bandwidth":3512594, "exit_policy":["reject *:*"], "exit_policy_summary":{"reject":["1-65535"]}, [...] "advertised_bandwidth_fraction":2.777751E-4, "consensus_weight_fraction":2.4263727E-4, "guard_probability":0.0, "middle_probability":7.2791905E-4, "exit_probability":0.0, "recommended_version":true, "hibernating":true} ], [...] ]}
[0] https://globe.torproject.org/#/relay/5EF740BB88C75915F8316DFEC8F1C8631FF26F1... [1] https://atlas.torproject.org/#details/5EF740BB88C75915F8316DFEC8F1C8631FF26F...
Should I run multiple relays on the same machine/IP ?
You can, and it may help, but there may be a simpler problem that can be fixed here.
- Matt
OK I've set MaxAdvertisedBandwidth, but I did set it in the past, with no results ....
Anything else beside running multiple relays ?
Many many thanks again !
2014-10-11 2:48 GMT-04:00 Matthew Finkel matthew.finkel@gmail.com:
On Sat, Oct 11, 2014 at 02:05:24AM -0400, Blaise Gagnon wrote:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Hi Blaise,
Thanks for running a relay!
It looks like you're currently peaking at a little over 2MB (with a mean of ~1MB)[0][1].
I also see that the relay is currently hibernating. This will certainly impact the amount of bandwidth you use. Did you configure MaxAdvertisedBandwidth?
Below is what the network knows about your relay (with some irrelevant details removed).
$ curl https://onionoo.torproject.org/details?fingerprint=5EF740BB88C75915F8316DFEC... { "version":"1.1", "relays_published":"2014-10-11 05:00:00", "relays":[ { "nickname":"QuebecFibe", "fingerprint":"5EF740BB88C75915F8316DFEC8F1C8631FF26F12", [...] "last_seen":"2014-10-11 06:00:00", "last_changed_address_or_port":"2014-10-07 07:00:00", "first_seen":"2014-07-17 17:00:00", "running":true, "flags":["Fast","Running","V2Dir","Valid"], [...] "consensus_weight":5950, "host_name":"69.159.127.80", "last_restarted":"2014-10-08 06:31:26", "bandwidth_rate":26214400, "bandwidth_burst":26214400, "observed_bandwidth":3512594, "advertised_bandwidth":3512594, "exit_policy":["reject *:*"], "exit_policy_summary":{"reject":["1-65535"]}, [...] "advertised_bandwidth_fraction":2.777751E-4, "consensus_weight_fraction":2.4263727E-4, "guard_probability":0.0, "middle_probability":7.2791905E-4, "exit_probability":0.0, "recommended_version":true, "hibernating":true} ], [...] ]}
[0] https://globe.torproject.org/#/relay/5EF740BB88C75915F8316DFEC8F1C8631FF26F1... [1] https://atlas.torproject.org/#details/5EF740BB88C75915F8316DFEC8F1C8631FF26F...
Should I run multiple relays on the same machine/IP ?
You can, and it may help, but there may be a simpler problem that can be fixed here.
- Matt
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
and ... what is "hibernating" ?
2014-10-11 2:55 GMT-04:00 Blaise Gagnon quebecfibe@gmail.com:
OK I've set MaxAdvertisedBandwidth, but I did set it in the past, with no results ....
Anything else beside running multiple relays ?
Many many thanks again !
2014-10-11 2:48 GMT-04:00 Matthew Finkel matthew.finkel@gmail.com:
On Sat, Oct 11, 2014 at 02:05:24AM -0400, Blaise Gagnon wrote:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Hi Blaise,
Thanks for running a relay!
It looks like you're currently peaking at a little over 2MB (with a mean of ~1MB)[0][1].
I also see that the relay is currently hibernating. This will certainly impact the amount of bandwidth you use. Did you configure MaxAdvertisedBandwidth?
Below is what the network knows about your relay (with some irrelevant details removed).
$ curl https://onionoo.torproject.org/details?fingerprint=5EF740BB88C75915F8316DFEC... { "version":"1.1", "relays_published":"2014-10-11 05:00:00", "relays":[ { "nickname":"QuebecFibe", "fingerprint":"5EF740BB88C75915F8316DFEC8F1C8631FF26F12", [...] "last_seen":"2014-10-11 06:00:00", "last_changed_address_or_port":"2014-10-07 07:00:00", "first_seen":"2014-07-17 17:00:00", "running":true, "flags":["Fast","Running","V2Dir","Valid"], [...] "consensus_weight":5950, "host_name":"69.159.127.80", "last_restarted":"2014-10-08 06:31:26", "bandwidth_rate":26214400, "bandwidth_burst":26214400, "observed_bandwidth":3512594, "advertised_bandwidth":3512594, "exit_policy":["reject *:*"], "exit_policy_summary":{"reject":["1-65535"]}, [...] "advertised_bandwidth_fraction":2.777751E-4, "consensus_weight_fraction":2.4263727E-4, "guard_probability":0.0, "middle_probability":7.2791905E-4, "exit_probability":0.0, "recommended_version":true, "hibernating":true} ], [...] ]}
[0] https://globe.torproject.org/#/relay/5EF740BB88C75915F8316DFEC8F1C8631FF26F1... [1] https://atlas.torproject.org/#details/5EF740BB88C75915F8316DFEC8F1C8631FF26F...
Should I run multiple relays on the same machine/IP ?
You can, and it may help, but there may be a simpler problem that can be fixed here.
- Matt
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar lunar@torproject.org:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".-- Lunar lunar@torproject.org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon quebecfibe@gmail.com:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar lunar@torproject.org:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".-- Lunar lunar@torproject.org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can you please copy/paste your entire torrc to a pastebin and provide us the link?
It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server.
On 10/11/2014 4:54 PM, Blaise Gagnon wrote:
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon <quebecfibe@gmail.com mailto:quebecfibe@gmail.com>:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar <lunar@torproject.org mailto:lunar@torproject.org>:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
-- Lunar <lunar@torproject.org mailto:lunar@torproject.org>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto: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
2014-10-11 10:06 GMT-04:00 s7r s7r@sky-ip.org:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Can you please copy/paste your entire torrc to a pastebin and provide us the link?
It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server.
On 10/11/2014 4:54 PM, Blaise Gagnon wrote:
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon <quebecfibe@gmail.com mailto:quebecfibe@gmail.com>:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar <lunar@torproject.org mailto:lunar@torproject.org>:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
-- Lunar <lunar@torproject.org mailto:lunar@torproject.org>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto: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
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUOTlTAAoJEIN/pSyBJlsRC0AIAKHjgRlZKXGBC2SoxjKMk+WJ l7LOVuwp3L7wQJ1L7hHUyJTRAfRZ7OzXlgK3gurg/Bxdhb8BO8W0r+Yk8yVjr4zV /rLDnibYxO7XCU7wUUdVClhLkDeCzwpu9I+t7bBDsif6T8PkjqjE4pPxwFHcm1T4 oCYvavpWS/K4wNs4PbrbBJBmxXYgzScAwGs00Xr5oBbl9B0aJ2RLfdwEu2blqyHb XkfSLkdhes4kRnCc5DQhT4BBDPrtCCqe66cOWXSGrH2ji0J29WGnniG3+lbvv0eo csEioxV7Cn8/ptvkapH4qjYQsHHb1jTG31y/ZOJZhtMHx8hYR+1nxvmlaZKgvYQ= =rzUm -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
RelayBandwidthBurst 15 MBytes RelayBandwidthRate 3 MBytes ContactInfo QuebecFibe@gmail.com - 200Mb dedicated relay ControlPort 9052 CookieAuthentication 1 DataDirectory /home/blaise/.arm/tor_data DirPort 9030 DisableDebuggerAttachment 0 ExitPolicy reject *:* Log notice file /home/blaise/.arm/tor_log Nickname QuebecFibe ORPort 27645 RunAsDaemon 1
Use this. You are using the latest Tor?
On 10/11/2014 5:11 PM, Blaise Gagnon wrote:
2014-10-11 10:06 GMT-04:00 s7r <s7r@sky-ip.org mailto:s7r@sky-ip.org>:
Can you please copy/paste your entire torrc to a pastebin and provide us the link?
It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server.
On 10/11/2014 4:54 PM, Blaise Gagnon wrote:
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon <quebecfibe@gmail.com mailto:quebecfibe@gmail.com <mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com>>:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar <lunar@torproject.org mailto:lunar@torproject.org <mailto:lunar@torproject.org mailto:lunar@torproject.org>>:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
-- Lunar <lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto: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
- -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 PGP Pubkey: http://www.sky-ip.org/s7r@sky-ip.org.asc
0.2.5.8-rc yup I'm trying this torrc and will get back to you.
Thanks s7r !
2014-10-11 10:21 GMT-04:00 s7r s7r@sky-ip.org:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
RelayBandwidthBurst 15 MBytes RelayBandwidthRate 3 MBytes ContactInfo QuebecFibe@gmail.com - 200Mb dedicated relay ControlPort 9052 CookieAuthentication 1 DataDirectory /home/blaise/.arm/tor_data DirPort 9030 DisableDebuggerAttachment 0 ExitPolicy reject *:* Log notice file /home/blaise/.arm/tor_log Nickname QuebecFibe ORPort 27645 RunAsDaemon 1Use this. You are using the latest Tor?
On 10/11/2014 5:11 PM, Blaise Gagnon wrote:
2014-10-11 10:06 GMT-04:00 s7r <s7r@sky-ip.org mailto:s7r@sky-ip.org>:
Can you please copy/paste your entire torrc to a pastebin and provide us the link?
It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server.
On 10/11/2014 4:54 PM, Blaise Gagnon wrote:
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon <quebecfibe@gmail.com mailto:quebecfibe@gmail.com <mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com>>:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar <lunar@torproject.org mailto:lunar@torproject.org <mailto:lunar@torproject.org mailto:lunar@torproject.org>>:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
-- Lunar <lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto: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
s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 PGP Pubkey: http://www.sky-ip.org/s7r@sky-ip.org.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUOTz/AAoJEIN/pSyBJlsR47sH/22x8Fycj/JUaYi+D6NIuGJX cQO0DRXDsXKt25x9dN85kTmJdTYwnMGAmrGo2jd7ICMM6maANHmd7Ns3QpeTevDH Gr30xc9QScCYNyDwK1h783gIaZ4dhh87SA0ClakCBie5SQKyars2PiNlFRW5QcWn fgIVSyEvy8Ld4wzdobJTVd6UpLTjqSJjm4EzItbn79f8UKPoJKW+1BAyebFBcbFM QAWujcgLcAmmnWTdu5Cci7g8RUMWpnKJKmX3nENPV7CbaeGkgy5u//A42XswL5mV aox5OqHl3xqQJk4BZwYXEdfYjXq/j8TXTugttuFA6OdSn0eCjsxvXAIGCoH4LxE= =X1E2 -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If you don't want to rate-limit, remove RelayBandwidthBurst and RelayBandwidthRate lines.
On 10/11/2014 5:24 PM, Blaise Gagnon wrote:
0.2.5.8-rc yup I'm trying this torrc and will get back to you.
Thanks s7r !
2014-10-11 10:21 GMT-04:00 s7r <s7r@sky-ip.org mailto:s7r@sky-ip.org>:
RelayBandwidthBurst 15 MBytes RelayBandwidthRate 3 MBytes ContactInfo QuebecFibe@gmail.com mailto:QuebecFibe@gmail.com - 200Mb dedicated relay ControlPort 9052 CookieAuthentication 1 DataDirectory /home/blaise/.arm/tor_data DirPort 9030 DisableDebuggerAttachment 0 ExitPolicy reject *:* Log notice file /home/blaise/.arm/tor_log Nickname QuebecFibe ORPort 27645 RunAsDaemon 1
Use this. You are using the latest Tor?
On 10/11/2014 5:11 PM, Blaise Gagnon wrote:
2014-10-11 10:06 GMT-04:00 s7r <s7r@sky-ip.org mailto:s7r@sky-ip.org <mailto:s7r@sky-ip.org mailto:s7r@sky-ip.org>>:
Can you please copy/paste your entire torrc to a pastebin and provide us the link?
It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server.
On 10/11/2014 4:54 PM, Blaise Gagnon wrote:
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon <quebecfibe@gmail.com mailto:quebecfibe@gmail.com <mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com>
<mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com
<mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com>>>:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar <lunar@torproject.org mailto:lunar@torproject.org <mailto:lunar@torproject.org mailto:lunar@torproject.org>
<mailto:lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>>>:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
-- Lunar <lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>
<mailto:lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>>>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
<mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org
<mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto: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
as this is fully dedicated 200Mbits, I'm deleting these lines.
2014-10-11 10:28 GMT-04:00 s7r s7r@sky-ip.org:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
If you don't want to rate-limit, remove RelayBandwidthBurst and RelayBandwidthRate lines.
On 10/11/2014 5:24 PM, Blaise Gagnon wrote:
0.2.5.8-rc yup I'm trying this torrc and will get back to you.
Thanks s7r !
2014-10-11 10:21 GMT-04:00 s7r <s7r@sky-ip.org mailto:s7r@sky-ip.org>:
RelayBandwidthBurst 15 MBytes RelayBandwidthRate 3 MBytes ContactInfo QuebecFibe@gmail.com mailto:QuebecFibe@gmail.com - 200Mb dedicated relay ControlPort 9052 CookieAuthentication 1 DataDirectory /home/blaise/.arm/tor_data DirPort 9030 DisableDebuggerAttachment 0 ExitPolicy reject *:* Log notice file /home/blaise/.arm/tor_log Nickname QuebecFibe ORPort 27645 RunAsDaemon 1
Use this. You are using the latest Tor?
On 10/11/2014 5:11 PM, Blaise Gagnon wrote:
2014-10-11 10:06 GMT-04:00 s7r <s7r@sky-ip.org mailto:s7r@sky-ip.org <mailto:s7r@sky-ip.org mailto:s7r@sky-ip.org>>:
Can you please copy/paste your entire torrc to a pastebin and provide us the link?
It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server.
On 10/11/2014 4:54 PM, Blaise Gagnon wrote:
after a few hours, still hibernating, and still wondering why I lost Stable, Guard and Named all at the same time (see atlas graph)... weird.
2014-10-11 6:03 GMT-04:00 Blaise Gagnon <quebecfibe@gmail.com mailto:quebecfibe@gmail.com <mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com>
<mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com
<mailto:quebecfibe@gmail.com mailto:quebecfibe@gmail.com>>>:
no reason for my node to be hibernating, no caps...
2014-10-11 3:31 GMT-04:00 Lunar <lunar@torproject.org mailto:lunar@torproject.org <mailto:lunar@torproject.org mailto:lunar@torproject.org>
<mailto:lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>>>:
Blaise Gagnon:
and ... what is "hibernating" ?
See AccountingMax and related options in tor manpage:
AccountingMax N bytes|KBytes|MBytes|GBytes|KBits|MBits|GBits|TBytes Never send more than the specified number of bytes in a given accounting period, or receive more than that number in the period. For example, with AccountingMax set to 1 GByte, a server could send 900 MBytes and receive 800 MBytes and continue running. It will only hibernate once one of the two reaches 1 GByte. When the number of bytes gets low, Tor will stop accepting new connections and circuits. When the number of bytes is exhausted, Tor will hibernate until some time in the next accounting period. To prevent all servers from waking at the same time, Tor will also wait until a random point in each period before waking up. If you have bandwidth cost issues, enabling hibernation is preferable to setting a low bandwidth, since it provides users with a collection of fast servers that are up some of the time, which is more useful than a set of slow servers that are always "available".
-- Lunar <lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>
<mailto:lunar@torproject.org mailto:lunar@torproject.org
<mailto:lunar@torproject.org mailto:lunar@torproject.org>>>
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
<mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org
<mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org
mailto:tor-relays@lists.torproject.org>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org mailto: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
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUOT6KAAoJEIN/pSyBJlsRk7UIANOdx2BzlshZLXuubzMmsofx 6df2t+8WHYJqnj6mIM9PSFCfS5hdi+hMfd8/+upcaav83t52C/ocLOOK2z8oQeRz sDwpzvXbAdbV0wwlpw2eBluVdsPew+jjpZH6eIOI/bAoVa2CtnXQyrKvpW0IpxrA 8/zxsyL49bwP/3nKaYlcWrEMLkIv9hJMekjBJIEXVyDNhDevtOZRCUvAYCSa30tW AK4G81Bdy8axmlJkoeDCANceb0J1EzZm8cau1jqtkTsNI03YIKZwCo31mhkhKomA VyXbYiXupRIw7zMxI5kM6vF4Gi08j10ZaAsKoE58c0RNtHo+X9ktiLrSdDUPiTU= =INaj -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
still "hibernating", BUT ... bandwidth went up like crazy !
2014-10-11 2:57 GMT-04:00 Blaise Gagnon quebecfibe@gmail.com:
and ... what is "hibernating" ?
2014-10-11 2:55 GMT-04:00 Blaise Gagnon quebecfibe@gmail.com:
OK I've set MaxAdvertisedBandwidth, but I did set it in the past, with no
results ....
Anything else beside running multiple relays ?
Many many thanks again !
2014-10-11 2:48 GMT-04:00 Matthew Finkel matthew.finkel@gmail.com:
On Sat, Oct 11, 2014 at 02:05:24AM -0400, Blaise Gagnon wrote:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a
dedicated
quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12
Hi Blaise,
Thanks for running a relay!
It looks like you're currently peaking at a little over 2MB (with a mean of ~1MB)[0][1].
I also see that the relay is currently hibernating. This will certainly impact the amount of bandwidth you use. Did you configure MaxAdvertisedBandwidth?
Below is what the network knows about your relay (with some irrelevant details removed).
$ curl https://onionoo.torproject.org/details?fingerprint=5EF740BB88C75915F8316DFEC... { "version":"1.1", "relays_published":"2014-10-11 05:00:00", "relays":[ { "nickname":"QuebecFibe", "fingerprint":"5EF740BB88C75915F8316DFEC8F1C8631FF26F12", [...] "last_seen":"2014-10-11 06:00:00", "last_changed_address_or_port":"2014-10-07 07:00:00", "first_seen":"2014-07-17 17:00:00", "running":true, "flags":["Fast","Running","V2Dir","Valid"], [...] "consensus_weight":5950, "host_name":"69.159.127.80", "last_restarted":"2014-10-08 06:31:26", "bandwidth_rate":26214400, "bandwidth_burst":26214400, "observed_bandwidth":3512594, "advertised_bandwidth":3512594, "exit_policy":["reject *:*"], "exit_policy_summary":{"reject":["1-65535"]}, [...] "advertised_bandwidth_fraction":2.777751E-4, "consensus_weight_fraction":2.4263727E-4, "guard_probability":0.0, "middle_probability":7.2791905E-4, "exit_probability":0.0, "recommended_version":true, "hibernating":true} ], [...] ]}
[0] https://globe.torproject.org/#/relay/5EF740BB88C75915F8316DFEC8F1C8631FF26F1... [1] https://atlas.torproject.org/#details/5EF740BB88C75915F8316DFEC8F1C8631FF26F...
Should I run multiple relays on the same machine/IP ?
You can, and it may help, but there may be a simpler problem that can be fixed here.
- Matt
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 10/11/2014 08:05 AM, Blaise Gagnon wrote:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
You do not have the stable flag currently, which might influence the bandwidth.
I do have a traffic limit of 10 TB/month, for that the following config options in torrc works :
# 10 TB/month == 4008 KB/sec, rate is measured in Bytes # 4008: $> echo "10 * 1024^4 / 31 / 24 / 60 / 60 / 1024" | bc # BandwidthRate 4 MB BandwidthBurst 10 MB
Currently about 50% of my advertised bandwidth rate is really used. That matches to https://metrics.torproject.org/bandwidth.html
I had Stable and Named, until I got Guard for a day or so, then those 3 flags never came back again !!!! , while ago, check graphs
2014-10-11 4:59 GMT-04:00 Toralf Förster toralf.foerster@gmx.de:
On 10/11/2014 08:05 AM, Blaise Gagnon wrote:
Hi and many thanks for developping this project !
I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet.
You do not have the stable flag currently, which might influence the bandwidth.
I do have a traffic limit of 10 TB/month, for that the following config options in torrc works :
# 10 TB/month == 4008 KB/sec, rate is measured in Bytes # 4008: $> echo "10 * 1024^4 / 31 / 24 / 60 / 60 / 1024" | bc # BandwidthRate 4 MB BandwidthBurst 10 MB
Currently about 50% of my advertised bandwidth rate is really used. That matches to https://metrics.torproject.org/bandwidth.html
-- Toralf pgp key: 0076 E94E
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Blaise Gagnon -
Joakim Bülow -
Lunar -
Matthew Finkel -
s7r -
Toralf Förster