Hi All, this is my first post on this list so warm welcome to every one a specialy to Tor developers. On my servers I`m running paralllel prod servers with tor relays on the separate IP. I`m supporting tor network for free with high speed tor relays but I need to customize the time when my server will share 100% of its resources for tor and when traffic will be limited. Is it possible to schedule the time when bandwith will looks as follow: 8:00 - 18:00 - Tor relay bandwith 250kb/s 18:00 - 8:00 - Tor relay bandwith 10 000kb/s How may I schedule this in tor relay ? Is it possible to limit traffic on the client or I need to do it on my firewall ? Thanks in advance for any feedback.
Hey, the easiest solution that comes to mind is a cronjob/systemd timer/whatever that modifies the config file and sends a SIGHUP to tor to trigger a config reload. I'm not very familiar with the codebase, so I can't guarantee that reloading the config file applies new (Relay)BandwithRate settings, but from the glances I took at the code it does seem like it should do it. Please someone verify or falsify this claim. ajs124 On Sun, 6 Dec 2015 21:38:05 +0100 Zalezny Niezalezny <zalezny.niezalezny@gmail.com> wrote:
Hi All,
this is my first post on this list so warm welcome to every one a specialy to Tor developers.
On my servers I`m running paralllel prod servers with tor relays on the separate IP. I`m supporting tor network for free with high speed tor relays but I need to customize the time when my server will share 100% of its resources for tor and when traffic will be limited.
Is it possible to schedule the time when bandwith will looks as follow:
8:00 - 18:00 - Tor relay bandwith 250kb/s
18:00 - 8:00 - Tor relay bandwith 10 000kb/s
How may I schedule this in tor relay ? Is it possible to limit traffic on the client or I need to do it on my firewall ?
Thanks in advance for any feedback.
On 7 Dec 2015, at 09:39, ajs124 <tor@ajs124.de> wrote:
Hey,
the easiest solution that comes to mind is a cronjob/systemd timer/whatever that modifies the config file and sends a SIGHUP to tor to trigger a config reload.
I'm not very familiar with the codebase, so I can't guarantee that reloading the config file applies new (Relay)BandwithRate settings, but from the glances I took at the code it does seem like it should do it. Please someone verify or falsify this claim.
Reloading the config file changes all the settings. For the few settings where it doesn't, tor will warn you, or refuse to reload the config.
ajs124
On Sun, 6 Dec 2015 21:38:05 +0100 Zalezny Niezalezny <zalezny.niezalezny@gmail.com> wrote:
Hi All,
this is my first post on this list so warm welcome to every one a specialy to Tor developers.
On my servers I`m running paralllel prod servers with tor relays on the separate IP. I`m supporting tor network for free with high speed tor relays but I need to customize the time when my server will share 100% of its resources for tor and when traffic will be limited.
Is it possible to schedule the time when bandwith will looks as follow:
8:00 - 18:00 - Tor relay bandwith 250kb/s
18:00 - 8:00 - Tor relay bandwith 10 000kb/s
How may I schedule this in tor relay ? Is it possible to limit traffic on the client or I need to do it on my firewall ?
Thanks in advance for any feedback.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
Hi!
Hi All Is it possible to schedule the time when bandwith will looks as follow:
8:00 - 18:00 - Tor relay bandwith 250kb/s
18:00 - 8:00 - Tor relay bandwith 10 000kb/s
How may I schedule this in tor relay ? Is it possible to limit traffic on the client or I need to do it on my firewall ?
I do see 3 viable ways, just run the relay from 18 to 8 a clock and stop it (via cron?) from 8 to 18. Or create 2 different tor configurations one limiting the bandwith to 250 kb/s and the other one to 10000 kb/s and reload tor with the according configuration (via cron) last but not least you could setup some fancy traffic shaping like in https://svn.torproject.org/svn/tor/tags/tor-0_2_0_20_rc/contrib/linux-tor-pr... where you limit the bandwith with tc and not tor itself. Greets
On Mon, 7 Dec 2015 21:42:11 +0100 "tor-relay@b4ckbone.de" <tor-relay@b4ckbone.de> wrote:
Hi!
Hi All Is it possible to schedule the time when bandwith will looks as follow:
8:00 - 18:00 - Tor relay bandwith 250kb/s
18:00 - 8:00 - Tor relay bandwith 10 000kb/s
How may I schedule this in tor relay ? Is it possible to limit traffic on the client or I need to do it on my firewall ?
I do see 3 viable ways, just run the relay from 18 to 8 a clock and stop it (via cron?) from 8 to 18. Or create 2 different tor configurations one limiting the bandwith to 250 kb/s and the other one to 10000 kb/s and reload tor with the according configuration (via cron) last but not least you could setup some fancy traffic shaping like in https://svn.torproject.org/svn/tor/tags/tor-0_2_0_20_rc/contrib/linux-tor-pr... where you limit the bandwith with tc and not tor itself.
Yeah but any of these are very likely to wreck your consensus weight situation, and as a result you'll be hard pressed to use the full potential of the 10000 KB/sec cap. The first option will also "ensure" you'll never get the Stable flag. Sure if "that's what you have to work with" then there's no any better options remaining, and of these listed personally I'd suggest the reloading configs one. -- With respect, Roman
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I think I will write a script which will change bandwidth base on the number of incomin connections to my varnish server. Then there is a big chance to keep stable flag on. Thank U for all that ideas ;))) Zalezny Dnia 7 grudnia 2015 22:23:21 CET, Roman Mamedov <rm@romanrm.net> napisał(a):
On Mon, 7 Dec 2015 21:42:11 +0100 "tor-relay@b4ckbone.de" <tor-relay@b4ckbone.de> wrote:
Hi!
Hi All Is it possible to schedule the time when bandwith will looks as follow:
8:00 - 18:00 - Tor relay bandwith 250kb/s
18:00 - 8:00 - Tor relay bandwith 10 000kb/s
How may I schedule this in tor relay ? Is it possible to limit traffic on the client or I need to do it on my firewall ?
I do see 3 viable ways, just run the relay from 18 to 8 a clock and stop it (via cron?) from 8 to 18. Or create 2 different tor configurations one limiting the bandwith to 250 kb/s and the other one to 10000 kb/s and reload tor with the according configuration (via cron) last but not least you could setup some fancy traffic shaping like in
https://svn.torproject.org/svn/tor/tags/tor-0_2_0_20_rc/contrib/linux-tor-pr...
where you limit the bandwith with tc and not tor itself.
Yeah but any of these are very likely to wreck your consensus weight situation, and as a result you'll be hard pressed to use the full potential of the 10000 KB/sec cap. The first option will also "ensure" you'll never get the Stable flag.
Sure if "that's what you have to work with" then there's no any better options remaining, and of these listed personally I'd suggest the reloading configs one.
-- With respect, Roman
------------------------------------------------------------------------
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
- -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQJEBAEBCgAuBQJWZgS7JxxaYWxlem55IDx6YWxlem55Lm5pZXphbGV6bnlAZ21h aWwuY29tPgAKCRDiQxB1lp0KmnZJD/oCtkRXmnqYobwurX4Tts/j1ekQdVbMHJlu KR0GQrPIDii/lrJwozeKmqpG7O5VMsOOOftrFLX3n3roQXirLXffXwnkIBZZvC3V iHTfBRzXB3VrMiWhzthJSgie1qMQWXKyq+zcoXygq6t39pzBsilkjh97BOsQpqq1 EttTUVL+HTF5Uw6TD5KfQN330L1kWan7F1ILjB6qO7GRX7jz/gStibKaSc4j5O19 G3Z8S8FAGY+rGPI3f8qfXGNAd55i664Ah7fjK4HopE8ruf2u00Fs89oqc141n4Cq cpR0TpDOGCdWKrDmmcX5cGKXV+YpRB+HlxfLnZI66Xu+Ern9V0Ue2tQ5ihG+to7Q kJBqjACvVuS9WcND1aNNFbfwVLwC1FXcxrVwdEv/sx25NgsulD7175pwHDsuDuj1 cEteWrdLse850hRf5P/5q906xiILjBcW+XOw8h5FxgAmEQT2ehIhnQDx8AUxU0qh ogqCLm+moy7tEYP5CKmszyqDhLshKhx04VKUrRtpE4xCoojcsYUEHsLwIszTmepb tnpPu+82FaNa7+HKlQRaAoSFcuKU2CJ+f1dudrPFpF3EIYr0jRpQfGnE4p9Zr9dI 3T0+TarvTf4UftYkn63iSl8sLOn8iutWZ+yIT9Jm57q8g1ckSTKYM1EpZbjhcUNs lsbQJgcvRg== =bs0+ -----END PGP SIGNATURE-----
On 8 Dec 2015, at 12:11, Green Dream <greendream848@gmail.com> wrote:
any of these are very likely to wreck your consensus weight situation
From a Tor user's perspective, if a relay is periodically dropping to 250 Kb/s, a low consensus weight for that relay is probably a good thing.
Two other possibilities: * always run the relay at 250kbps * run a bridge instead (I don't know if 250kbps is still considered enough for a bridge) Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
participants (6)
-
ajs124 -
Green Dream -
Roman Mamedov -
Tim Wilson-Brown - teor -
tor-relay＠b4ckbone.de -
Zalezny Niezalezny