Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
If your relay is on the current list, you don't need to do anything.
If you're asking:
Q: What's a fallback directory mirror?
Fallback directory mirrors help Tor clients connect to the network. For more details, see [1].
Q: Is my relay on the current list?
Search [2] and [3] for your relay fingerprint or IP address and port:
[2] is the current list of fallbacks in Tor. [3] is used to create the next list of fallbacks.
Q: What do I need to do if my relay is on the list?
Keep the same IP address, keys, and ports. Email tor-relays if the relay's details change.
Q: Can my relay be on the list next time?
We need fast relays that will be on the same IP address and port for 2 years. Reply to this email to get on the list, or to update the details of your relay.
Once or twice a year, we run a script to choose about 150-200 relays from the potential list [3] for the list in Tor [2].
Q: Why didn't my relay get on the list last time?
We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time.
It's good to have some new relays on the list every release. That helps tor clients, because blocking a changing list is harder.
Q. I already have a relay in the fallback list, can I add another?
We will pick up to 7 relays per operator to be in the fallback list. Please send any relays that you would like considered for the fallback list.
Thanks for considering and/or being a fallback directory mirror!
[1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [3]: https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [4]: https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2... https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log
924B24AFA7F075D059E8EEB284CC400B33D3D036
Will be stable for the foreseeable future and is available as a fallback if needed.
On Tue, Jun 26, 2018, 12:41 Colin Childs colin@torproject.org wrote:
Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
If your relay is on the current list, you don't need to do anything.
If you're asking:
Q: What's a fallback directory mirror?
Fallback directory mirrors help Tor clients connect to the network. For more details, see [1].
Q: Is my relay on the current list?
Search [2] and [3] for your relay fingerprint or IP address and port:
[2] is the current list of fallbacks in Tor. [3] is used to create the next list of fallbacks.
Q: What do I need to do if my relay is on the list?
Keep the same IP address, keys, and ports. Email tor-relays if the relay's details change.
Q: Can my relay be on the list next time?
We need fast relays that will be on the same IP address and port for 2 years. Reply to this email to get on the list, or to update the details of your relay.
Once or twice a year, we run a script to choose about 150-200 relays from the potential list [3] for the list in Tor [2].
Q: Why didn't my relay get on the list last time?
We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time.
It's good to have some new relays on the list every release. That helps tor clients, because blocking a changing list is harder.
Q. I already have a relay in the fallback list, can I add another?
We will pick up to 7 relays per operator to be in the fallback list. Please send any relays that you would like considered for the fallback list.
Thanks for considering and/or being a fallback directory mirror!
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Colin Childs dijo [Tue, Jun 26, 2018 at 11:40:42AM -0500]:
Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
You didn't specify whether the answer should go to the list or just to you. I hope I'm not needlessly spamming the world!
4661DE96D3F8E923994B05218F23760C8D7935A4
Greetings,
Hi Gunnar,
Either is alright!
Thank you for getting in contact and offering your relay as a fallback directory mirror!
On Jun 27, 2018, at 10:42 AM, Gunnar Wolf gwolf@debian.org wrote:
Colin Childs dijo [Tue, Jun 26, 2018 at 11:40:42AM -0500]:
Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
You didn't specify whether the answer should go to the list or just to you. I hope I'm not needlessly spamming the world!
4661DE96D3F8E923994B05218F23760C8D7935A4
Greetings, _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi,
you can include the following two relays for sure, as they are guaranteed to not change their ip / port:
- 1E01B887F7FB61BEFC34FA8D9EA98E4268A8275F (rofltor02) - 41A3C16269C7B63DB6EB741DBDDB4E1F586B1592 (rofltor03)
Currently rofltor03 has a traffic cap. I can change it to a long running and bandwidth (instead of traffic) capped relay tho, if that is wanted.
The following relays can keep their ip / port, if you want to include them:
- 8101421BEFCCF4C271D5483C5AABCAAD245BBB9D (rofltor01) - F741E5124CB12700DA946B78C9B2DD175D6CD2A1 (rofltor06) - 15BE17C99FACE24470D40AF782D6A9C692AB36D6 (rofltor07) - 90A5D1355C4B5840E950EB61E673863A6AE3ACA1 (rofltor09) - 3CB4193EF4E239FCEDC4DC43468E0B0D6B67ACC3 (rofltor10)
Best regards, Matthias
On 06/26/2018 06:40 PM, Colin Childs wrote:
Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
If your relay is on the current list, you don't need to do anything.
If you're asking:
Q: What's a fallback directory mirror?
Fallback directory mirrors help Tor clients connect to the network. For more details, see [1].
Q: Is my relay on the current list?
Search [2] and [3] for your relay fingerprint or IP address and port:
[2] is the current list of fallbacks in Tor. [3] is used to create the next list of fallbacks.
Q: What do I need to do if my relay is on the list?
Keep the same IP address, keys, and ports. Email tor-relays if the relay's details change.
Q: Can my relay be on the list next time?
We need fast relays that will be on the same IP address and port for 2 years. Reply to this email to get on the list, or to update the details of your relay.
Once or twice a year, we run a script to choose about 150-200 relays from the potential list [3] for the list in Tor [2].
Q: Why didn't my relay get on the list last time?
We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time.
It's good to have some new relays on the list every release. That helps tor clients, because blocking a changing list is harder.
Q. I already have a relay in the fallback list, can I add another?
We will pick up to 7 relays per operator to be in the fallback list. Please send any relays that you would like considered for the fallback list.
Thanks for considering and/or being a fallback directory mirror!
[1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [3]: https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [4]: https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 29 Jun 2018, at 07:39, Matthias Fetzer tor@rofl.cat wrote:
Currently rofltor03 has a traffic cap. I can change it to a long running and bandwidth (instead of traffic) capped relay tho, if that is wanted.
How often does the relay reach its traffic cap? Becoming a fallback adds about 10 kilobytes per second of bandwidth. So it's not a good role for relays that have limited traffic or bandwidth. (We'd rather use those relays for user traffic.)
T
Hi,
How often does the relay reach its traffic cap?
Every month. Rofltor03 is capped at ~10TB of incoming traffic. I can probably spare another 5TB, but I don't think this will change things much.
So it's not a good role for relays that have limited traffic or bandwidth. (We'd rather use those relays for user traffic.)
Alright. I will then just leave it running, as is. You can use my other relays as fallbacks tho.
Best regards, Matthias
Hi,
D405FCCF06ADEDF898DF2F29C9348DCB623031BA
Am 26.06.2018 18:40 schrieb Colin Childs:
Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
If your relay is on the current list, you don't need to do anything.
If you're asking:
Q: What's a fallback directory mirror?
Fallback directory mirrors help Tor clients connect to the network. For more details, see [1].
Q: Is my relay on the current list?
Search [2] and [3] for your relay fingerprint or IP address and port:
[2] is the current list of fallbacks in Tor. [3] is used to create the next list of fallbacks.
Q: What do I need to do if my relay is on the list?
Keep the same IP address, keys, and ports. Email tor-relays if the relay's details change.
Q: Can my relay be on the list next time?
We need fast relays that will be on the same IP address and port for 2 years. Reply to this email to get on the list, or to update the details of your relay.
Once or twice a year, we run a script to choose about 150-200 relays from the potential list [3] for the list in Tor [2].
Q: Why didn't my relay get on the list last time?
We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might be down when we check. That's ok, we will check it again next time.
It's good to have some new relays on the list every release. That helps tor clients, because blocking a changing list is harder.
Q. I already have a relay in the fallback list, can I add another?
We will pick up to 7 relays per operator to be in the fallback list. Please send any relays that you would like considered for the fallback list.
Thanks for considering and/or being a fallback directory mirror!
[1] [2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [2] [3]: https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [3] [4]: https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2... [4]
Links:
[1] https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2] https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [3] https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [4] https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 6/26/18 6:40 PM, Colin Childs wrote:
Hello Tor Relay Operators,
Do you want your relay to be a Tor fallback directory mirror? Will it have the same address and port for the next 2 years? Just reply to this email with your relay's fingerprint.
Due to a recent hardware change I switched to offline keys too. Therefore plesase remove these 2 relays, they are gone:
1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA D11D11877769B9E617537B4B46BFB92B443DE33D
Please add these two exits instead, I do plan to run both for at least the next 2 years or so:
zwiebeltoralf 63BF46A63F9C21FD315CD061B3EAA3EB05283A0A zwiebeltoralf2 509EAB4C5D10C9A9A24B4EA0CE402C047A2D64E6
tor-relays@lists.torproject.org
-
Colin Childs -
Gunnar Wolf -
Kenneth Freeman -
Matthew Glennon -
Matthias Fetzer -
raltullou＠posteo.org -
teor -
Toralf Förster