Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-21 Thread 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 not get the exit flag. Which means what? Will it be use for exit at all? Would be sad to loose this 300MBit/s fully used Exit. yl ___ to

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-21 Thread yl
On 2/18/22 16:13, li...@for-privacy.net wrote: Before changing exit policies, read 'man torrc' carefully. SERVER OPTIONS ExitPolicy* and IPv6Exit. 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

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-21 Thread yl
Hello On 2/17/22 21:20, Martin Gebhardt wrote: ExitPolicy accept [::]:20-21 # FTP, SSH, telnet ExitPolicy accept [::]:23 # FTP, SSH, telnet ExitPolicy accept [::]:43 # WHOIS [..] ExitPolicy reject *:* Oh yes, I will try that. Now that you write it here I could also keep some other IPv4 ports

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-18 Thread nusenu
On Wednesday, February 16, 2022 1:45:51 PM CET yl wrote: 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 onl

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-18 Thread yl
Hello, On 2/18/22 13:40, newslet...@unicorncloud.org wrote: 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. I believe this changed with the last version, but I am not sure. I want to use IPv4 and IPv6, I just do

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-18 Thread newsletter
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, how can I used a reduced exit policy and don't allow any IPv4 exit traffic? The following line in the top of

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-18 Thread Martin Gebhardt
Hi , I would try the following: ExitPolicy accept [::]:20-21 # FTP, SSH, telnet ExitPolicy accept [::]:23 # FTP, SSH, telnet ExitPolicy accept [::]:43 # WHOIS [..] ExitPolicy reject *:* I would recommend that you block outgoing email ports instead of trying to block out all IPv4 traffic. I've

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-18 Thread lists
On Wednesday, February 16, 2022 1:45:51 PM CET yl wrote: > 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 53 open on IPv4. > The following line in the top of all the ExitPolicy lines in to

[tor-relays] Reduced exit and not IPv4 exit traffic at all

2022-02-17 Thread yl
Hello all, how can I used a reduced exit policy and don't allow any IPv4 exit traffic? The following line in the top of all the ExitPolicy lines in torrc seems not to work. ExitPolicy reject 0.0.0.0:* What is the order I needed here, first "reject" and then accept or the other way around? R