Just wanted to tell I could set up a new relay with fingerprint Akbash 7C5032CF2545636FEECCE1065A25944FF49C09F7 The relay is been running for more than a day and gathered the Exit, Fast, Running, V2Dir and Valid flags. However this hardworking relay would not continue its earnest efforts unless it could find a wealthy and amenable sponsor. Livak Sent with [ProtonMail](https://protonmail.com) Secure Email.
Just a joke, but it would be nice to find financial help to make the tor network grow faster. Livak Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, September 16, 2018 11:21 AM, I <beatthebastards@inbox.com> wrote:
Do you mean you paid for a day and now want to be helped to pay for every other day?
-----Original Message----- From: livak@protonmail.com Sent: Sun, 16 Sep 2018 11:01:14 +0000 To: tor-relays@lists.torproject.org Subject: [tor-relays] New exit node Just wanted to tell I could set up a new relay with fingerprint
Akbash 7C5032CF2545636FEECCE1065A25944FF49C09F7
The relay is been running for more than a day and gathered the Exit, Fast, Running, V2Dir and Valid flags.
However this hardworking relay would not continue its earnest efforts unless it could find a wealthy and amenable sponsor.
Livak
Sent with [ProtonMail](https://protonmail.com) Secure Email.
On Sun, 16 Sep 2018 13:40:50 +0000 livak <livak@protonmail.com> wrote:
it would be nice to find financial help to make the tor network grow faster.
You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay: - at OVH, which is oversaturated with relays by any measure; - only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server; - IPv4-only, while OVH does provide IPv6; To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up. It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top. Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting. [1] https://www.kimsufi.com/fr/serveurs.xml --
Roman Mamedov:
some would say adding more relays at OVH does more harm than good
please include references -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
On Sun, 16 Sep 2018 15:18:00 +0000 nusenu <nusenu-lists@riseup.net> wrote:
Roman Mamedov:
some would say adding more relays at OVH does more harm than good
please include references
Just the opinion that I remember seeing sometimes. For example: "Do you realize how useless and counterproductive for the Tor network is to keep adding more and more nodes in the same network and in a country with a worrying amount of surveillance?" https://www.lowendtalk.com/discussion/comment/1725285/#Comment_1725285 They call it "useless and counterproductive" which to me seems to suggest that from their view it's better to not add nodes at all, than to add ones at OVH. As for whether or not I agree with that, probably not, and I do run a few relays at OVH myself. "The Tor documentation suggests not placing more than 10 nodes per network. [...] At this moment, Tor is fast enough to prefer network diversity (very important issue) over bandwidth (hasn't been a problem for years)." https://www.lowendtalk.com/discussion/comment/1727727/#Comment_1727727 -- With respect, Roman
Roman, ignore this people. Do you have an intention for a relay in APAC? I looking for a provider in Asia with unlimited bandwith / traffic. I've found nothing, Or other recommendations? Maximum of 15$ is desired. Or South America. or Africa. Outside of Tor-overloaded areas. Want to reach my goal of 10 relays... Olaf Am 16.09.2018 um 17:03 schrieb Roman Mamedov:
On Sun, 16 Sep 2018 13:40:50 +0000 livak <livak@protonmail.com> wrote:
it would be nice to find financial help to make the tor network grow faster. You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay:
- at OVH, which is oversaturated with relays by any measure;
- only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server;
- IPv4-only, while OVH does provide IPv6;
To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up.
It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top.
Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting.
Hello Olaf, OVH, DigitalOcean and Vultr have servers in Singapore. While this would probably add to geographic diversity, I am unsure if it's a good idea to run more relays in those AS. On the other hand, I run several OVH-Relays at different geographi locations. Best regards, Matthias On 09/16/2018 05:18 PM, Olaf Grimm wrote:
Roman, ignore this people.
Do you have an intention for a relay in APAC? I looking for a provider in Asia with unlimited bandwith / traffic. I've found nothing, Or other recommendations? Maximum of 15$ is desired. Or South America. or Africa. Outside of Tor-overloaded areas. Want to reach my goal of 10 relays...
Olaf
Am 16.09.2018 um 17:03 schrieb Roman Mamedov:
On Sun, 16 Sep 2018 13:40:50 +0000 livak <livak@protonmail.com> wrote:
it would be nice to find financial help to make the tor network grow faster. You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay:
- at OVH, which is oversaturated with relays by any measure;
- only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server;
- IPv4-only, while OVH does provide IPv6;
To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up.
It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top.
Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
DigitalOcean and Vultr have traffic limits. 1 TB sounds great, but is nothing over a month. Not sure about OVH. I tried to run relays in Japan and Singapore some years ago. It was bad, you are more than 10000 km away from the rest of the crowd so expect delay and jitter :(
On 16. Sep 2018, at 19:16, Matthias Fetzer <tor@rofl.cat> wrote:
Hello Olaf,
OVH, DigitalOcean and Vultr have servers in Singapore. While this would probably add to geographic diversity, I am unsure if it's a good idea to run more relays in those AS.
On the other hand, I run several OVH-Relays at different geographi locations.
Best regards, Matthias
On 09/16/2018 05:18 PM, Olaf Grimm wrote:
Roman, ignore this people.
Do you have an intention for a relay in APAC? I looking for a provider in Asia with unlimited bandwith / traffic. I've found nothing, Or other recommendations? Maximum of 15$ is desired. Or South America. or Africa. Outside of Tor-overloaded areas. Want to reach my goal of 10 relays...
Olaf
Am 16.09.2018 um 17:03 schrieb Roman Mamedov:
On Sun, 16 Sep 2018 13:40:50 +0000 livak <livak@protonmail.com> wrote:
it would be nice to find financial help to make the tor network grow faster. You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay:
- at OVH, which is oversaturated with relays by any measure;
- only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server;
- IPv4-only, while OVH does provide IPv6;
To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up.
It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top.
Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting.
_______________________________________________ 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
Hi, OVH also has some traffic limits, that get cut down to 10 Mbps (depending on the plan). So you could probably have a fast relay until the limit is reached and then keep doing 10 Mbps. If the goal is to have better geographic diversity, I think a slower (or a bursting) relay might still be a good choice. Having relays do hundrets of Mbps is nice - but not the only way to have a useful relay. Best regards, Matthias On 09/16/2018 08:18 PM, niftybunny wrote:
DigitalOcean and Vultr have traffic limits. 1 TB sounds great, but is nothing over a month. Not sure about OVH.
I tried to run relays in Japan and Singapore some years ago. It was bad, you are more than 10000 km away from the rest of the crowd so expect delay and jitter :(
On 16. Sep 2018, at 19:16, Matthias Fetzer <tor@rofl.cat> wrote:
Hello Olaf,
OVH, DigitalOcean and Vultr have servers in Singapore. While this would probably add to geographic diversity, I am unsure if it's a good idea to run more relays in those AS.
On the other hand, I run several OVH-Relays at different geographi locations.
Best regards, Matthias
On 09/16/2018 05:18 PM, Olaf Grimm wrote:
Roman, ignore this people.
Do you have an intention for a relay in APAC? I looking for a provider in Asia with unlimited bandwith / traffic. I've found nothing, Or other recommendations? Maximum of 15$ is desired. Or South America. or Africa. Outside of Tor-overloaded areas. Want to reach my goal of 10 relays...
Olaf
Am 16.09.2018 um 17:03 schrieb Roman Mamedov:
On Sun, 16 Sep 2018 13:40:50 +0000 livak <livak@protonmail.com> wrote:
it would be nice to find financial help to make the tor network grow faster. You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay:
- at OVH, which is oversaturated with relays by any measure;
- only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server;
- IPv4-only, while OVH does provide IPv6;
To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up.
It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top.
Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting.
_______________________________________________ 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
https://metrics.torproject.org/userstats-relay-table.html <https://metrics.torproject.org/userstats-relay-table.html> A lot of countries are near, that wouldn’t help much if the first hop is in Japan, the second is in Europe and the Exit is in the greatest country on earth. https://www.techwalla.com/articles/network-latency-milliseconds-per-mile <https://www.techwalla.com/articles/network-latency-milliseconds-per-mile> And with moving packets around the world you pass a lot of ASs and will be switched and routed a lot + extra delay with the tor relays which route in software. Yes, Layer 3 switching should be line speed and routing is slowly dying. Its still very very slow. Don’t believe me. Try it for yourself.
On 16. Sep 2018, at 23:36, I <beatthebastards@inbox.com> wrote:
niftybunny wrote
I tried to run relays in Japan and Singapore some years ago. It was bad, you are more than 10000 km away from the rest of the crowd so expect delay and jitter :(
Aren't Russia, China, North Korea and Malaysia somewhere near?
Robert
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
DigitalOzean and Vultr is new for me and I check these offers. I want diversity. My Problem now are the languages of the provider homepages in South America. Not all of them are easy to translate with google translator. And what I can do in case of an abuse case? How to reply? Pages in Asia have an English translation. Thanks for the recommendations. I try it. A bridge with less traffic on the Philippines? Low traffic should work... Hm. Think, think... Later. Olaf Am 16.09.2018 um 19:16 schrieb Matthias Fetzer:
Hello Olaf,
OVH, DigitalOcean and Vultr have servers in Singapore. While this would probably add to geographic diversity, I am unsure if it's a good idea to run more relays in those AS.
On the other hand, I run several OVH-Relays at different geographi locations.
Best regards, Matthias
On 09/16/2018 05:18 PM, Olaf Grimm wrote:
Roman, ignore this people.
Do you have an intention for a relay in APAC? I looking for a provider in Asia with unlimited bandwith / traffic. I've found nothing, Or other recommendations? Maximum of 15$ is desired. Or South America. or Africa. Outside of Tor-overloaded areas. Want to reach my goal of 10 relays...
Olaf
Am 16.09.2018 um 17:03 schrieb Roman Mamedov:
On Sun, 16 Sep 2018 13:40:50 +0000 livak <livak@protonmail.com> wrote:
it would be nice to find financial help to make the tor network grow faster. You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay:
- at OVH, which is oversaturated with relays by any measure;
- only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server;
- IPv4-only, while OVH does provide IPv6;
To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up.
It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top.
Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting.
_______________________________________________ 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
Olaf “which you can use for your own purposes (with only 10% of the bandwidth given to Tor) Not worth the risk. I did do that. I had a server with our email and old business web pages, so I wondered what should I do with the spare capacity? Hand 50% over to Tor. Felt good. Alas you cannot run an exit that way, as just as risky in many ways as running it from home. It will look as your own data is coming from a Tox exit. The ISP can kill your server at any time, and take your stuff with it. So you have to run it from a second IP on your server, but that costs, still risky of ISP closing it all down. I got away with it for a few years, but just last week, after an automated abuse complaint and idiotic IT team, I lost my nerve and moved that exit to another server, which was nowadays costs only a little more than second IP address. Gerry From: tor-relays <tor-relays-bounces@lists.torproject.org> On Behalf Of Olaf Grimm Sent: 16 September 2018 21:58 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] New exit node DigitalOzean and Vultr is new for me and I check these offers. I want diversity. My Problem now are the languages of the provider homepages in South America. Not all of them are easy to translate with google translator. And what I can do in case of an abuse case? How to reply? Pages in Asia have an English translation. Thanks for the recommendations. I try it. A bridge with less traffic on the Philippines? Low traffic should work... Hm. Think, think... Later. Olaf Am 16.09.2018 um 19:16 schrieb Matthias Fetzer: Hello Olaf, OVH, DigitalOcean and Vultr have servers in Singapore. While this would probably add to geographic diversity, I am unsure if it's a good idea to run more relays in those AS. On the other hand, I run several OVH-Relays at different geographi locations. Best regards, Matthias On 09/16/2018 05:18 PM, Olaf Grimm wrote: Roman, ignore this people. Do you have an intention for a relay in APAC? I looking for a provider in Asia with unlimited bandwith / traffic. I've found nothing, Or other recommendations? Maximum of 15$ is desired. Or South America. or Africa. Outside of Tor-overloaded areas. Want to reach my goal of 10 relays... Olaf Am 16.09.2018 um 17:03 schrieb Roman Mamedov: On Sun, 16 Sep 2018 13:40:50 +0000 livak <mailto:livak@protonmail.com> <livak@protonmail.com> wrote: it would be nice to find financial help to make the tor network grow faster. You need to put things in perspective, and then consider how your request looks to an outside observer. What you have is a relay: - at OVH, which is oversaturated with relays by any measure; - only 10 Mbit (seems hard-capped), even though you get unmetered 100 Mbit on your server; - IPv4-only, while OVH does provide IPv6; To summarize, this is the worst location to start a new relay (some would say adding more relays at OVH does more harm than good), the bandwidth is capped ridiculously low, and you didn't even put much thought into setting it up. It seems that you think you found a way to set up a tiny relay on the side, exploit gullible people to pay you for it, and enjoy not only a paid-off server (after all the fee is as low as 4 EUR per month[1]) which you can use for your own purposes (with only 10% of the bandwidth given to Tor), but also some free money on top. Considering that many of us pay for multiple relays out of our own pocket -- actual fast ones with hundreds megabits at non-trivial locations -- and don't run the first thing to the mailing list begging for money, your behavior is nothing but disgusting. [1] https://www.kimsufi.com/fr/serveurs.xml _______________________________________________ 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
Hello livak Am 16.09.2018 um 13:01 schrieb livak:
Just wanted to tell I could set up a new relay with fingerprint
Akbash 7C5032CF2545636FEECCE1065A25944FF49C09F7
The relay is been running for more than a day and gathered the Exit, Fast, Running, V2Dir and Valid flags.
...
Livak
Thanks for engaging and doing. Did you consider to reduce your exit policy a bit like: https://www.torproject.org/docs/faq.html.en#DefaultExitPorts or what you can find in the history of this list? -- Cheers, Felix
Felix, thanks for your help. The relay is now running with the option ExitRelay 1 which should trigger the default exit policy, if I didn't understand. The default front page, /usr/share/doc/tor/tor-exit-notice.html should also be displayed. Livak Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, September 16, 2018 3:38 PM, Felix <zwiebel@quantentunnel.de> wrote:
Hello livak
Am 16.09.2018 um 13:01 schrieb livak:
Just wanted to tell I could set up a new relay with fingerprint Akbash 7C5032CF2545636FEECCE1065A25944FF49C09F7 The relay is been running for more than a day and gathered the Exit, Fast, Running, V2Dir and Valid flags.
...
Livak
Thanks for engaging and doing.
Did you consider to reduce your exit policy a bit like: https://www.torproject.org/docs/faq.html.en#DefaultExitPorts or what you can find in the history of this list?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Cheers, Felix
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
The relay is now running with the option
ExitRelay 1
which should trigger the default exit policy, if I didn't understand.
your exit policy is: reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* reject 10.0.0.0/8:* reject 172.16.0.0/12:* reject 142.44.232.119:* accept *:* which I assume is not what you want because it allows SMTP (tcp/25). You might want to consider the reduced exit policy https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy you might also want to enable IPv6 exiting if you have IPv6 connectivity to make your exit more useful https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#IPv6
The default front page, should also be displayed.
if you want to make it easy to see that HTML page, you might want to change your DirPort to 80 since people are unlikely to enter http://142.44.232.119:9030/ into their URL bar -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
Thanks nusenu, The relay is configured with the exit reduced policy. The ORPort is 443 and the DirPort is 80. Since exit policy uses "*" as the IP address, IPv6 should be allowed. Does "nyx" does nyx deal with IPv6 ? Livak Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, September 16, 2018 5:12 PM, nusenu <nusenu-lists@riseup.net> wrote:
The relay is now running with the option ExitRelay 1 which should trigger the default exit policy, if I didn't understand.
your exit policy is: reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* reject 10.0.0.0/8:* reject 172.16.0.0/12:* reject 142.44.232.119:* accept :
which I assume is not what you want because it allows SMTP (tcp/25).
You might want to consider the reduced exit policy https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy
you might also want to enable IPv6 exiting if you have IPv6 connectivity to make your exit more useful https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#IPv6
The default front page, should also be displayed.
if you want to make it easy to see that HTML page, you might want to change your DirPort to 80 since people are unlikely to enter
into their URL bar
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This may be a little above my head - I'm a bit of an amateur in this area. I used the script from: https://github.com/mricon/tor-relay-bootstrap-rpi/blob/master/README.md to set it up initially, which, after enabling upnp, seemed to work perfectly. Then, at some point in the middle of the night it went offline. Could it be a problem with my ISP? I thought nyx was for more recent versions of TOR. I had been using ARM to monitor it. Thanks for your help everyone I really do appreciate it! On Mon, Sep 17, 2018, 09:45 livak <livak@protonmail.com> wrote:
Thanks nusenu,
The relay is configured with the exit reduced policy. The ORPort is 443 and the DirPort is 80.
Since exit policy uses "*" as the IP address, IPv6 should be allowed.
Does "nyx" does nyx deal with IPv6 ?
Livak
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, September 16, 2018 5:12 PM, nusenu <nusenu-lists@riseup.net> wrote:
The relay is now running with the option ExitRelay 1 which should trigger the default exit policy, if I didn't understand.
your exit policy is: reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* reject 10.0.0.0/8:* reject 172.16.0.0/12:* reject 142.44.232.119:* accept :
which I assume is not what you want because it allows SMTP (tcp/25).
You might want to consider the reduced exit policy https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy
you might also want to enable IPv6 exiting if you have IPv6 connectivity to make your exit more useful https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#IPv6
The default front page, should also be displayed.
if you want to make it easy to see that HTML page, you might want to change your DirPort to 80 since people are unlikely to enter
into their URL bar
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 17 Sep 2018, at 23:44, livak <livak@protonmail.com> wrote:
Thanks nusenu,
The relay is configured with the exit reduced policy. The ORPort is 443 and the DirPort is 80.
Since exit policy uses "*" as the IP address, IPv6 should be allowed.
Your relay's IPv6 Exit policy is: reject 1-65535 Which is the port summary for: reject *6:* You need to set IPv6Exit 1 to exit via IPv6. (The default is 0.) https://www.torproject.org/docs/tor-manual.html.en If you want your relay to accept client connections via IPv6, you also need to set: ORPort [Your IPv6 Address]:Port For example: ORPort [2001:610:510:115:192:42:115:102]:9004 You need to add the IPv6 ORPort to your existing IPv4 ORPort, which looks like: Address 192.42.115.102 ORPort 192.42.115.102:9004
Does "nyx" does nyx deal with IPv6 ?
nyx is a relay monitor. It will tell you if your relay uses IPv6. But it doesn't configure your relay for you.
On 18 Sep 2018, at 00:00, Kyle Levy <levyrkyle@gmail.com> wrote:
I used the script from: https://github.com/mricon/tor-relay-bootstrap-rpi/blob/master/README.md to set it up initially, which, after enabling upnp, seemed to work perfectly. Then, at some point in the middle of the night it went offline. Could it be a problem with my ISP?
Possibly. But it's more likely a problem with your upnp or router connection limits. Our experience is that upnp is unreliable. You're better to configure a port mapping manually on your router. Tor relays need about 7000 connections to work, more for exits. Many home routers work badly when they have over 1000 connections.
I thought nyx was for more recent versions of TOR. I had been using ARM to monitor it.
nyx works with all supported versions of Tor (0.2.9 and later). arm is no longer supported. T
Thanks teor,
Your relay's IPv6 Exit policy is: reject 1-65535 Which is the port summary for: reject *6:*
IPv6 is now enabled on the exit relay and its exit policy updated. I set the maximum open descriptors to 10,000 with ulimit -n 10000 Are there any other system limits I should consider ? Livak Sent with [ProtonMail](https://protonmail.com) Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, September 17, 2018 3:51 PM, teor <teor@riseup.net> wrote:
On 17 Sep 2018, at 23:44, livak <livak@protonmail.com> wrote:
Thanks nusenu,
The relay is configured with the exit reduced policy. The ORPort is 443 and the DirPort is 80.
Since exit policy uses "*" as the IP address, IPv6 should be allowed.
Your relay's IPv6 Exit policy is: reject 1-65535 Which is the port summary for: reject *6:*
You need to set IPv6Exit 1 to exit via IPv6. (The default is 0.) https://www.torproject.org/docs/tor-manual.html.en
If you want your relay to accept client connections via IPv6, you also need to set:
ORPort [Your IPv6 Address]:Port
For example:
ORPort [2001:610:510:115:192:42:115:102]:9004
You need to add the IPv6 ORPort to your existing IPv4 ORPort, which looks like:
Address 192.42.115.102 ORPort 192.42.115.102:9004
Does "nyx" does nyx deal with IPv6 ?
nyx is a relay monitor. It will tell you if your relay uses IPv6. But it doesn't configure your relay for you.
On 18 Sep 2018, at 00:00, Kyle Levy <levyrkyle@gmail.com> wrote:
I used the script from: https://github.com/mricon/tor-relay-bootstrap-rpi/blob/master/README.md to set it up initially, which, after enabling upnp, seemed to work perfectly. Then, at some point in the middle of the night it went offline. Could it be a problem with my ISP?
Possibly. But it's more likely a problem with your upnp or router connection limits.
Our experience is that upnp is unreliable. You're better to configure a port mapping manually on your router.
Tor relays need about 7000 connections to work, more for exits. Many home routers work badly when they have over 1000 connections.
I thought nyx was for more recent versions of TOR. I had been using ARM to monitor it.
nyx works with all supported versions of Tor (0.2.9 and later).
arm is no longer supported.
T
participants (12)
-
Felix -
gerard＠bulger.co.uk -
I -
Kyle Levy -
livak -
Matthias Fetzer -
niftybunny -
nusenu -
Olaf Grimm -
Paul Templeton -
Roman Mamedov -
teor