Hello! I'm running a non-exit relay on my VPS with small amount of traffic/month. That means my advertised bandwidth is ~500 KB/s. I got a new VPS where I want to let a relay run with several MB/s - My question now is: should I let the slower relay run (aka do 500 KB/s positively contribute to the TOR network?) or move my relay key to the new server and run this one only?
Thanks in advance!
On Sat, Oct 1, 2016, at 04:54, Sheesh wrote:
Hello! I'm running a non-exit relay on my VPS with small amount of traffic/month. That means my advertised bandwidth is ~500 KB/s. I got a new VPS where I want to let a relay run with several MB/s - My question now is: should I let the slower relay run (aka do 500 KB/s positively contribute to the TOR network?) or move my relay key to the new server and run this one only?
To me, if the old relay is on a provider/network that isn't already over-populated, more is better and it's a net good. If that provider is already well covered, it's less useful.
Your mileage and opinions may vary.
Thanks for your answer. It's a NL server from a smaller provider, but Serverius DC after all.
I guess there're already quite a lot of relays in NL/Serverius... so not really useful then?
On 02.10.2016 00:15, Dave Warren wrote:
On Sat, Oct 1, 2016, at 04:54, Sheesh wrote:
Hello! I'm running a non-exit relay on my VPS with small amount of traffic/month. That means my advertised bandwidth is ~500 KB/s. I got a new VPS where I want to let a relay run with several MB/s - My question now is: should I let the slower relay run (aka do 500 KB/s positively contribute to the TOR network?) or move my relay key to the new server and run this one only?
To me, if the old relay is on a provider/network that isn't already over-populated, more is better and it's a net good. If that provider is already well covered, it's less useful.
Your mileage and opinions may vary.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thanks for your answer. It's a NL server from a smaller provider, but Serverius DC after all.
I guess there're already quite a lot of relays in NL/Serverius... so not really useful then?
I'd say, it is still better to have one relay in an already "crowded" country than to not having it at all.
You could also turn the old relay into a bridge. I've read that low bandwidth machines are often better serving the network as bridges, although I don't know what the cutoff value for "low bandwidth" is in this case.
On 10/3/2016 12:00 AM, Green Dream wrote:
You could also turn the old relay into a bridge. I've read that low bandwidth machines are often better serving the network as bridges, although I don't know what the cutoff value for "low bandwidth" is in this case.
I recommend, if you decide to setup a bridge (which is very useful) make sure you include the latest pluggable transport and better make the new server with a fresh IP address a bridge, one which was never a Tor relay, because turning the older relay into a bridge might not be so effective -- the IP could be blacklisted due to be known as a Tor relay (part of the public consensus) and be impossible to reach by users behind restrictive firewalls / censored internet.
Thanks for everybody's input. I decided to move the relay keys to the new server but I'm not entirely sure if I start another slow (500KB/s) one or just seed some Linux distros or do something else helpful.
Also I do have a question about IPv6: If I read right I just have to add ORPort [IPv6]:Port DirPort [IPv6]:Port is this correct? Can I specify the same ports I use for IPv4 (443 and 80)?
Also since I have a couple of IPv6 available but a non-exit relay is it still necessary to set OutboundBindAddress?
On 2 Oct 2016, at 17:17, Sheesh sheesh@ip-static.eu wrote:
Thanks for everybody's input. I decided to move the relay keys to the new server but I'm not entirely sure if I start another slow (500KB/s) one or just seed some Linux distros or do something else helpful.
Also I do have a question about IPv6: If I read right I just have to add ORPort [IPv6]:Port DirPort [IPv6]:Port
You only need the ORPort, the IPv6 DirPort isn't needed any more. (It was used by a few of the 0.2.8 alpha series, but removed before the stable release.)
is this correct? Can I specify the same ports I use for IPv4 (443 and 80)?
Yes, this should work on most OSs, if it doesn't, please file a bug.
Also since I have a couple of IPv6 available but a non-exit relay is it still necessary to set OutboundBindAddress?
OutboundBindAddress can be used twice, once with an IPv4 address and once with an IPv6 address. Outbound traffic on a non-exit relay is all IPv4, and it will use the routing table if you don't use OutboundBindAddress.
Unless you have multiple IPv4 addresses, it won't make any difference.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Thank you! Two last questions, though (hope it's okay): Do I need to put ExitPolicy reject6 *:* in my torrc or is this covered by ExitPolicy reject *:*?
Also why do I always have 4 or 8 circuits open? At least that's what tor-arm shows me.
On 03.10.2016 03:34, teor wrote:
On 2 Oct 2016, at 17:17, Sheesh sheesh@ip-static.eu wrote:
Thanks for everybody's input. I decided to move the relay keys to the new server but I'm not entirely sure if I start another slow (500KB/s) one or just seed some Linux distros or do something else helpful.
Also I do have a question about IPv6: If I read right I just have to add ORPort [IPv6]:Port DirPort [IPv6]:Port
You only need the ORPort, the IPv6 DirPort isn't needed any more. (It was used by a few of the 0.2.8 alpha series, but removed before the stable release.)
is this correct? Can I specify the same ports I use for IPv4 (443 and 80)?
Yes, this should work on most OSs, if it doesn't, please file a bug.
Also since I have a couple of IPv6 available but a non-exit relay is it still necessary to set OutboundBindAddress?
OutboundBindAddress can be used twice, once with an IPv4 address and once with an IPv6 address. Outbound traffic on a non-exit relay is all IPv4, and it will use the routing table if you don't use OutboundBindAddress.
Unless you have multiple IPv4 addresses, it won't make any difference.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 2 Oct 2016, at 18:59, Sheesh sheesh@ip-static.eu wrote:
Thank you! Two last questions, though (hope it's okay): Do I need to put ExitPolicy reject6 *:* in my torrc or is this covered by ExitPolicy reject *:*?
ExitPolicy reject *:* applies to both IPv4 and IPv6. And your relay won't exit on IPv4 unless you set ExitRelay to 1, and won't exit on IPv6 unless you set IPv6Exit and ExitRelay to 1.
Also why do I always have 4 or 8 circuits open? At least that's what tor-arm shows me.
Because tor preemptively builds circuits for you to use when you need them. When your relay publishes a descriptor, it will make more circuits as needed to relay client traffic.
Tim
On 03.10.2016 03:34, teor wrote:
On 2 Oct 2016, at 17:17, Sheesh sheesh@ip-static.eu wrote:
Thanks for everybody's input. I decided to move the relay keys to the new server but I'm not entirely sure if I start another slow (500KB/s) one or just seed some Linux distros or do something else helpful.
Also I do have a question about IPv6: If I read right I just have to add ORPort [IPv6]:Port DirPort [IPv6]:Port
You only need the ORPort, the IPv6 DirPort isn't needed any more. (It was used by a few of the 0.2.8 alpha series, but removed before the stable release.)
is this correct? Can I specify the same ports I use for IPv4 (443 and 80)?
Yes, this should work on most OSs, if it doesn't, please file a bug.
Also since I have a couple of IPv6 available but a non-exit relay is it still necessary to set OutboundBindAddress?
OutboundBindAddress can be used twice, once with an IPv4 address and once with an IPv6 address. Outbound traffic on a non-exit relay is all IPv4, and it will use the routing table if you don't use OutboundBindAddress.
Unless you have multiple IPv4 addresses, it won't make any difference.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
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
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Um, yes it will. I don't have ExitRelay in my torrc file at all, and it exits just fine.
On Sun, Oct 2, 2016 at 9:03 PM, teor teor2345@gmail.com wrote:
And your relay won't exit on IPv4 unless you set ExitRelay to 1
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 2 Oct 2016, at 19:10, Tristan supersluether@gmail.com wrote:
Um, yes it will. I don't have ExitRelay in my torrc file at all, and it exits just fine.
Yes, you're right, ExitRelay is auto by default, which means Exit, but warn.
Tim
On Sun, Oct 2, 2016 at 9:03 PM, teor teor2345@gmail.com wrote:
And your relay won't exit on IPv4 unless you set ExitRelay to 1
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Finding information, passing it along. ～SuperSluether _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Alright, thank you!
I'm just wondering why I have only a few connections (14 inbound, 1 outbound) right now. But I guess that's because the relay lost its stable and fast flag due to server move and several restarts and now needs some time to reestablish?
On 03.10.2016 04:03, teor wrote:
On 2 Oct 2016, at 18:59, Sheesh sheesh@ip-static.eu wrote:
Thank you! Two last questions, though (hope it's okay): Do I need to put ExitPolicy reject6 *:* in my torrc or is this covered by ExitPolicy reject *:*?
ExitPolicy reject *:* applies to both IPv4 and IPv6. And your relay won't exit on IPv4 unless you set ExitRelay to 1, and won't exit on IPv6 unless you set IPv6Exit and ExitRelay to 1.
Also why do I always have 4 or 8 circuits open? At least that's what tor-arm shows me.
Because tor preemptively builds circuits for you to use when you need them. When your relay publishes a descriptor, it will make more circuits as needed to relay client traffic.
Tim
On 03.10.2016 03:34, teor wrote:
On 2 Oct 2016, at 17:17, Sheesh sheesh@ip-static.eu wrote:
Thanks for everybody's input. I decided to move the relay keys to the new server but I'm not entirely sure if I start another slow (500KB/s) one or just seed some Linux distros or do something else helpful.
Also I do have a question about IPv6: If I read right I just have to add ORPort [IPv6]:Port DirPort [IPv6]:Port
You only need the ORPort, the IPv6 DirPort isn't needed any more. (It was used by a few of the 0.2.8 alpha series, but removed before the stable release.)
is this correct? Can I specify the same ports I use for IPv4 (443 and 80)?
Yes, this should work on most OSs, if it doesn't, please file a bug.
Also since I have a couple of IPv6 available but a non-exit relay is it still necessary to set OutboundBindAddress?
OutboundBindAddress can be used twice, once with an IPv4 address and once with an IPv6 address. Outbound traffic on a non-exit relay is all IPv4, and it will use the routing table if you don't use OutboundBindAddress.
Unless you have multiple IPv4 addresses, it won't make any difference.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
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
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Nevermind. It got its flags back and is now working a expected. :)
Thanks for everybody's help!
On 03.10.2016 05:45, Sheesh wrote:
Alright, thank you!
I'm just wondering why I have only a few connections (14 inbound, 1 outbound) right now. But I guess that's because the relay lost its stable and fast flag due to server move and several restarts and now needs some time to reestablish?
On 03.10.2016 04:03, teor wrote:
On 2 Oct 2016, at 18:59, Sheesh sheesh@ip-static.eu wrote:
Thank you! Two last questions, though (hope it's okay): Do I need to put ExitPolicy reject6 *:* in my torrc or is this covered by ExitPolicy reject *:*?
ExitPolicy reject *:* applies to both IPv4 and IPv6. And your relay won't exit on IPv4 unless you set ExitRelay to 1, and won't exit on IPv6 unless you set IPv6Exit and ExitRelay to 1.
Also why do I always have 4 or 8 circuits open? At least that's what tor-arm shows me.
Because tor preemptively builds circuits for you to use when you need them. When your relay publishes a descriptor, it will make more circuits as needed to relay client traffic.
Tim
On 03.10.2016 03:34, teor wrote:
On 2 Oct 2016, at 17:17, Sheesh sheesh@ip-static.eu wrote:
Thanks for everybody's input. I decided to move the relay keys to the new server but I'm not entirely sure if I start another slow (500KB/s) one or just seed some Linux distros or do something else helpful.
Also I do have a question about IPv6: If I read right I just have to add ORPort [IPv6]:Port DirPort [IPv6]:Port
You only need the ORPort, the IPv6 DirPort isn't needed any more. (It was used by a few of the 0.2.8 alpha series, but removed before the stable release.)
is this correct? Can I specify the same ports I use for IPv4 (443 and 80)?
Yes, this should work on most OSs, if it doesn't, please file a bug.
Also since I have a couple of IPv6 available but a non-exit relay is it still necessary to set OutboundBindAddress?
OutboundBindAddress can be used twice, once with an IPv4 address and once with an IPv6 address. Outbound traffic on a non-exit relay is all IPv4, and it will use the routing table if you don't use OutboundBindAddress.
Unless you have multiple IPv4 addresses, it won't make any difference.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
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
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
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@lists.torproject.org
-
Dave Warren -
Green Dream -
nusenu -
s7r -
Sheesh -
teor -
Tristan