yl1
February 16, 2022, 12:45pm
1
Hello all,
The following line in the top of all the ExitPolicy lines in torrc seems not to work.
What is the order I needed here, first "reject" and then accept or the other way around?
Reduced Exit policy like here:
Webtropia was a bit unhappy lately when UCEprotect listed the whole /24 for some reason I still don't understand.
But then I thought, why not disable IPv4 exit traffic, there is so many IPv6 resources that a IPv6 only Exit should still be fine.
Thanks
···
_______________________________________________https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
2 Likes
lists
February 18, 2022, 3:13pm
2
how can I used a reduced exit policy and don't allow any IPv4 exit traffic?
I don't think IPv6 only works. AFAIK, exits must have at least port 80,443 and
The following line in the top of all the ExitPolicy lines in torrc seems
What are you putting them for? All private addresses are rejected by default.
What is the order I needed here, first "reject" and then accept or the
No, as always, first come first served.
Reduced Exit policy like here:ReducedExitPolicy · Wiki · Legacy / Trac · GitLab
You can also take it like this. I would also delete port 22, then there would
Before changing exit policies, read 'man torrc' carefully. SERVER OPTIONS
But then I thought, why not disable IPv4 exit traffic, there is so many
Unfortunately, the IPv6 traffic on my relays is often close to 0 for months.
···
On Wednesday, February 16, 2022 1:45:51 PM CET yl wrote:
--
Debian GNU/Linux
It's free software and it gives you freedom!
martln
February 17, 2022, 8:20pm
3
Hi ,
I would try the following:
ExitPolicy accept [::]:20-21 # FTP, SSH, telnet
I would recommend that you block outgoing email ports instead of trying to block out all IPv4 traffic. I've never had any problems with ISPs and I ban outgoing email and SSH.
···
On 2/16/22 13:45, yl wrote:
Hello all,
The following line in the top of all the ExitPolicy lines in torrc seems not to work.
What is the order I needed here, first "reject" and then accept or the other way around?
Reduced Exit policy like here:ReducedExitPolicy · Wiki · Legacy / Trac · GitLab
Webtropia was a bit unhappy lately when UCEprotect listed the whole /24 for some reason I still don't understand.
But then I thought, why not disable IPv4 exit traffic, there is so many IPv6 resources that a IPv6 only Exit should still be fine.
Thankstor-relays Info Page
1 Like
Afaik this is not possible. To get the exit flag you need both IPv4 and IPv6 or only IPv4, but IPv6 only relays are not possible.
Greetings
···
On 16.02.2022 13:45, yl wrote:
Hello all,
The following line in the top of all the ExitPolicy lines in torrc
What is the order I needed here, first "reject" and then accept or the
Reduced Exit policy like here:ReducedExitPolicy · Wiki · Legacy / Trac · GitLab
Webtropia was a bit unhappy lately when UCEprotect listed the whole
But then I thought, why not disable IPv4 exit traffic, there is so
Thankstor-relays Info Page
_______________________________________________https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
nusenu
February 18, 2022, 11:06pm
6
how can I used a reduced exit policy and don't allow any IPv4 exit traffic?
tor's man page has the information on how to specify any IPv4:
*4 to denote all IPv4 addresses, and *6 to denote all IPv6 addresses.
I don't think IPv6 only works. AFAIK, exits must have at least port 80,443 and
You can run a relay that does allow exiting to IPv6 and not IPv4 but it will
kind regards,
···
On Wednesday, February 16, 2022 1:45:51 PM CET yl wrote:
--https://nusenu.github.io https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
1 Like
yl1
February 21, 2022, 8:12am
7
Hello
ExitPolicy accept [::]:20-21 # FTP, SSH, telnet
Oh yes, I will try that. Now that you write it here I could also keep some other IPv4 ports open that way. I need to check this out. Also need to test it by choosing "my" exit I guess.
I would recommend that you block outgoing email ports instead of trying to block out all IPv4 traffic. I've never had any problems with ISPs and I ban outgoing email and SSH.
E-Mail is banned, I think the reason for my problems was forum spam, so some spam done via 80/443.
yl
···
On 2/17/22 21:20, Martin Gebhardt wrote:https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
yl1
February 21, 2022, 8:16am
8
ah, there is is buried. I didn't know that there is man torrc, I always looked that up online in the 2019 documentation, or before that in the standard doc. online.
I will try what happens if I apply a config with IPv6 exit only, I guess it could work now.
yl
···
On 2/18/22 16:13, lists@for-privacy.net wrote:
Before changing exit policies, read 'man torrc' carefully. SERVER OPTIONS
_______________________________________________https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
yl1
February 21, 2022, 8:17am
9
Which means what? Will it be use for exit at all?
Would be sad to loose this 300MBit/s fully used Exit.
yl
···
On 2/19/22 00:06, nusenu wrote:
You can run a relay that does allow exiting to IPv6 and not IPv4 but it will
_______________________________________________https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays