Re: [tor-relays] IPv6 Tor authority is down?

Alright, good to know, thanks for your reply. -- Best, shruub ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] IPv6 Tor authority is down?

Hi, That IP address used to belong to Faravahar, which is in the progress of being relocated and hasn't found its new home yet (https://gitlab.torproject.org/tpo/core/tor/-/issues/40688). You can safely ignore this error. If you want a more up to date list, you can check the IP shown on

[tor-relays] IPv6 Tor authority is down?

Hello, so to also enable IPv6 on my relay I followed the post-install article which said that one should ping all IPv6 authorities with the following command: "ping6 -c2 2001:858:2:2:aabb:0:563b:1526 && ping6 -c2 2620:13:4000:6000::1000:118 && ping6 -c2 2001:67c:289c::9 && ping6 -c2

Re: [tor-relays] IPV6 address keeps changing every 2-3 days

Are you sure you are setting a private auto generated address that Ubuntu changes so that you can’t be tracked? Thanks, John C. > On Jan 19, 2022, at 1:49 AM, Quentin Campbell wrote: > > Hi, > > I'm running a non-exit relay on a home British Telecom broadband connection > (FTTC, 20Mb

Re: [tor-relays] IPV6 address keeps changing every 2-3 days

On Tuesday, January 18, 2022 10:36:21 PM CET Quentin Campbell wrote: > Its IP addresses (IPV4 & IPV6) are allocated dynamically. > > The IPV4 address can remain the same for weeks. However the IPV6 address > seems less stable and lasts no more than 2 or 3 days before changing. > > A consquence

[tor-relays] IPV6 address keeps changing every 2-3 days

Hi, I'm running a non-exit relay on a home British Telecom broadband connection (FTTC, 20Mb up/80Mb down). Its IP addresses (IPV4 & IPV6) are allocated dynamically. The IPV4 address can remain the same for weeks. However the IPV6 address seems less stable and lasts no more than 2 or 3 days

Re: [tor-relays] IPv6

> however I have now noticed a number of malicious login attempts Using a non standard ssh port and blocking power 22 should reduce the bot login attempts. (If you’re running a VPS be sure to test your custom port before blocking 22) I don’t see a relationship between IPv6 and login attempts

Re: [tor-relays] IPv6

On Wednesday, December 15, 2021 3:21:17 AM CET xplato via tor-relays wrote: > owever I have now noticed a number of malicious login attempts IPv6 login attempts (SSH) are very very rare. 1 per year! IPv4 several per day. I mostly _only_ allowed SSH login over IPv6. A /64 subnet has many

[tor-relays] IPv6

Hi all, I was able to add IPv6 on four HardenedBSD relays I run however I have now noticed a number of malicious login attempts. I am wondering if there is some correlation with the IPv6 or just a coincidence? Best regards, Dan Sent from ProtonMail for

Re: [tor-relays] IPv6 reachability tests fail on CenturyLink IPv6 6rd - reachability broken?

Neel Chauhan wrote Thu, 26 Aug 2021 21:16:20 -0700: > Aug 26 18:47:01.000 [notice] Auto-discovered IPv6 address > [REDACTED]:143 has not been found reachable. However, IPv4 address is > reachable. Publishing server descriptor without IPv6 address. > Aug 26 19:47:01.000 [notice] Auto-discovered

[tor-relays] IPv6 reachability tests fail on CenturyLink IPv6 6rd - reachability broken?

Hi, I recently moved into a home with CenturyLink Fiber and moved my FreeBSD relays to the said home. Fingerprints: https://metrics.torproject.org/rs.html#details/B0F9BA27944FA59E3B1A182208FF7C0CFF5497B2 https://metrics.torproject.org/rs.html#details/DB710B14D7329B7289CFCC547F48EF53F812C40D

[tor-relays] IPv6 not showing up on tor exit node

I run a tor exit node and have properly configured IPv6 but sometimes it does not appear on the tor relay list. This is fixed when I reboot the tor service but what could be the reason?___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

On 30.03.2021 21:38, Petrusko wrote: Ouch, this config looks like not so cool... I see on Metrics the ipv6 choosen by Tor process, is now on : "Unreachable OR Addresses" From: https://www.mail-archive.com/tor-relays@lists.torproject.org/msg17760.html 8< In short, with this new feature,

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

Ouch, this config looks like not so cool... I see on Metrics the ipv6 choosen by Tor process, is now on : "Unreachable OR Addresses" I'll write the other solution you given previously... with ORPort xxx.xxx.xxx.xxx:9001 ORPort [::xxx:x::::xxx]:9001 30/03/2021 à 20:07,

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

Ok ! So this only line will serve on both ipv4 and ipv6 together, ok thx ! Cool 30/03/2021 à 15:51, li...@for-privacy.net : > ORPort 9001 OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

On 27.03.2021 11:05, Petrusko wrote: I've set up a new relay, available with ipv4 and ipv6. And I'm not sure if I can serve DIRPort on the ipv6 too ? In the torrc file, I've config : ORPort 9001 ^ ORPort [::xxx:x::::xxx]:9001 Tor is dualstack now either:

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

Thx all for your answers. I'm not sure, because I see Tor listening too on DIRPort I've set up, with a "netstat -lpn", so may be it's still used ;) Le 27/03/2021 à 18:26, Toralf Förster a écrit : >> And I'm not sure if I can serve DIRPort on the ipv6 too ? > > If I understood it correctly a

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

On 3/27/21 11:05 AM, Petrusko wrote: And I'm not sure if I can serve DIRPort on the ipv6 too ? If I understood it correctly a DirPort are no longer needed for latest Tor software version. So you should be fine with opened IPv4|6 ORports only. -- Toralf

Re: [tor-relays] ipv6 ORPort + DIRPort too ?

> Petrusko hat am 27.03.2021 11:05 geschrieben: > > Is it allowed to add something like this, to advertise on ipv6 too ?? : > DIRPort [::xxx:x::::xxx]:9030 You can only advertise one DirPort, according to "man tor": > all but one DirPort must have the NoAdvertise flag set

[tor-relays] ipv6 ORPort + DIRPort too ?

Hey, I've set up a new relay, available with ipv4 and ipv6. And I'm not sure if I can serve DIRPort on the ipv6 too ? In the torrc file, I've config : ORPort 9001 ORPort [::xxx:x::::xxx]:9001 DIRPort 9030 Is it allowed to add something like this, to advertise on ipv6 too

Re: [tor-relays] IPv6 auto-discovery vs. privacy extensions

On 25 Feb (23:20:04), Onior Operator wrote: > > > Op 25/02/2021 14:19 schreef David Goulet : > > > > > > On 24 Feb (11:08:15), Onion Operator wrote: > > > Saluton, > > > > > > My relay started to log this message since 0.4.5.5: > > > > > > Auto-discovered IPv6 address [...]:443 has not been

Re: [tor-relays] IPv6 auto-discovery vs. privacy extensions

> Op 25/02/2021 14:19 schreef David Goulet : > > > On 24 Feb (11:08:15), Onion Operator wrote: > > Saluton, > > > > My relay started to log this message since 0.4.5.5: > > > > Auto-discovered IPv6 address [...]:443 has not been found reachable. > > However, IPv4 address is reachable.

Re: [tor-relays] IPv6

Roman Mamedov a écrit : > On Thu, 25 Feb 2021 16:54:50 +0100 > Casper wrote: > > > I found a "kind of solution" about that. > > > > Behind my fibre optique, I took 26000-26999 tcp ports with the NAT for > > IPv4 > > > > so I have 1 relay using pop3/pop3s for IPv4/IPv6, and many "little" > >

Re: [tor-relays] IPv6

On Thu, 25 Feb 2021 16:54:50 +0100 Casper wrote: > I found a "kind of solution" about that. > > Behind my fibre optique, I took 26000-26999 tcp ports with the NAT for > IPv4 > > so I have 1 relay using pop3/pop3s for IPv4/IPv6, and many "little" > relays on the range 26000-26999 for IPv4/IPv6.

Re: [tor-relays] IPv6

David Goulet a écrit : > On 24 Feb (12:02:11), Dr Gerard Bulger wrote: > > I am sure I am not alone in having much wasted bandwidth that could be put > > to good Tor use but they are only accessible via IPv6, while they can exit > > of course IPv4 and IPv6 I found a "kind of solution" about that.

Re: [tor-relays] IPv6

quot;firewall"). I cannot have my personal VPS seen as a Tor node, so cannot do that. Gerry -Original Message- From: tor-relays On Behalf Of David Goulet Sent: 25 February 2021 13:16 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] IPv6 On 24 Feb (12:02:11), Dr Gerard Bu

Re: [tor-relays] IPv6 auto-discovery vs. privacy extensions

On 24 Feb (11:08:15), Onion Operator wrote: > Saluton, > > My relay started to log this message since 0.4.5.5: > > Auto-discovered IPv6 address [...]:443 has not been found reachable. However, > IPv4 address is reachable. Publishing server descriptor without IPv6 address. > [2 similar

Re: [tor-relays] IPv6

On 24 Feb (12:02:11), Dr Gerard Bulger wrote: > Thinking of IPv6: > > How far has the team got in implementing IPv6 only OR port facility ? As of tor 0.4.5.x release, IPv6 is fully supported for tor clients and relays. > > Currently you can only run tor relay of any sort if there is open IPv4

Re: [tor-relays] IPv6

On Behalf Of Onion Operator Sent: 24 February 2021 10:08 To: tor-relays@lists.torproject.org Subject: [tor-relays] IPv6 auto-discovery vs. privacy extensions Saluton, My relay started to log this message since 0.4.5.5: Auto-discovered IPv6 address [...]:443 has not been found

Re: [tor-relays] IPv6 auto-discovery vs. privacy extensions

Onion Operator a écrit : >Saluton, >My relay started to log this message since 0.4.5.5: >Auto-discovered IPv6 address [...]:443 has not been found reachable. >However, IPv4 address is reachable. Publishing server descriptor without >IPv6 address. [2 similar message(s)

[tor-relays] IPv6 auto-discovery vs. privacy extensions

Saluton, My relay started to log this message since 0.4.5.5: Auto-discovered IPv6 address [...]:443 has not been found reachable. However, IPv4 address is reachable. Publishing server descriptor without IPv6 address. [2 similar message(s) suppressed in last 2400 seconds] I think it started

Re: [tor-relays] IPv6 Support or Uptime?

The Tor relay runs perfectly on IPv4 alone. I will leave it as IPv4 only until they fix the firmware for my router. The main reason I was trying IPv6 was that the Tor Project was pleading for more IPv6 capable relays. ‐‐‐ Original Message ‐‐‐ On Sunday, August 23, 2020 11:35 AM,

Re: [tor-relays] IPv6 Support or Uptime?

Hi Josh, the Tor network is still mostly IPv4 (https://metrics.torproject.org/relays-ipv6.html), so I would say it's ok to turn IPv6 off on your relay for now, especially if there's a problem with stability. Kind regards, Alexander > Josh Lawson hat am 21.08.2020 00:59 > geschrieben:

Re: [tor-relays] IPv6 Support or Uptime?

Dear Josh, thank you for running a Tor relay, but I have one concern: If your IPv6 configuration randomly "stops working", and in order to fix it, you have to restart your entire networking equipment, then this is going to affect many clients - even if your Consensus Weight equals the one of a

Re: [tor-relays] IPv6 Support or Uptime?

IMO uptime is more important because then you will get the stable (and after some time) other flags. Sebastian On 21/08/2020 00:59, Josh Lawson wrote: > I have IPv6 with my ISP, but there seems to be a bug in the firmware of my > networking equipment that causes IPv6 to stop working

[tor-relays] IPv6 Support or Uptime?

I have IPv6 with my ISP, but there seems to be a bug in the firmware of my networking equipment that causes IPv6 to stop working periodically and I have to take my network down and bring it back up. If I do not do this, my relay stops functioning as I have torrc configured to use IPv6 and IPv4.

Re: [tor-relays] IPv6 Port

On 10.06.2020 20:32, Josh Lawson wrote: Thanks! I’m a newbie and did not think you could use the same port for both in the configuration, but it does make sense networking wise. I have update my configuration and restarted the service. Just imagine IPv4 and IPv6 as 2 separate paths. IPtables

Re: [tor-relays] IPv6 Port

Thanks! I’m a newbie and did not think you could use the same port for both in the configuration, but it does make sense networking wise. I have update my configuration and restarted the service. On Wed, Jun 10, 2020 at 10:29, wrote: > On 31.05.2020 05:56, Josh Lawson wrote: >> I currently

Re: [tor-relays] IPv6 Port

On 31.05.2020 05:56, Josh Lawson wrote: I currently have my IPv6 connection running on port 9001. From an anti-surveillance perspective, would I be better changing the port to 80? I have IPv4 running on 443. I appreciate it! Take the same Port for IP & IPv6. Use [host]:port notation for IPv6

[tor-relays] IPv6 Port

I currently have my IPv6 connection running on port 9001. From an anti-surveillance perspective, would I be better changing the port to 80? I have IPv4 running on 443. I appreciate it!___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] IPV6

Hi, > On 5 May 2020, at 21:21, Dr Gerard Bulger wrote: > > Is there any work going on which would allow Tor to work with IPV6 alone? > i.e. no IPV4 OR ports etc. To protect user privacy, we need more dual-stack relays, before we can have IPv6-only relays. At the moment, we're working on

[tor-relays] IPV6

Is there any work going on which would allow Tor to work with IPV6 alone? i.e. no IPV4 OR ports etc. Gerry ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] ipv6 behaviour consensus

On Fri, 19 Apr 2019 01:46:19 +0300 s7r wrote: > I totally agree. But why would you want to advertise an IPv6 ORPort if > your Tor daemon only truly has IPv4 socket? This is what I don't > understand. Why would one want that? Just to look neat in the consensus? It is supported to advertise an

Re: [tor-relays] ipv6 behaviour consensus

Hi, > On 19 Apr 2019, at 07:41, Charly Ghislain wrote: > > I feel there is an issue in case the operator advertises an unreachable ip6 > address in the config. This seems like a configuration error that should be > spotted by a self-reachability mechanism that is yet to come, like for ipv4.

Re: [tor-relays] ipv6 behaviour consensus

Thursday, April 18, 2019 2:41 PM > *To:* tor-relays@lists.torproject.org > *Subject:* [tor-relays] ipv6 behaviour consensus > > > > Hi list, > > > > Last reply from s7r on jake Visser' issue included a link to an open issue > waiting for a consensus on a mailing list: >

Re: [tor-relays] ipv6 behaviour consensus

). So regardless of Full v6 support, or v6 only support [both are needed], at the very least some good logging to say if its failing would be great  From: tor-relays On Behalf Of Charly Ghislain Sent: Thursday, April 18, 2019 2:41 PM To: tor-relays@lists.torproject.org Subject: [tor-relays

Re: [tor-relays] ipv6 behaviour consensus

Hello, Charly Ghislain wrote: > selfreplying as I hadn't read the whole ticket thread at the time of > writing (still haven't, tbh). > > I think there are real reason to use natted traffic in this period of > transition toward ip6 and that must be supported. > My setup (ha proxy litening on both

Re: [tor-relays] ipv6 behaviour consensus

selfreplying as I hadn't read the whole ticket thread at the time of writing (still haven't, tbh). I think there are real reason to use natted traffic in this period of transition toward ip6 and that must be supported. My setup (ha proxy litening on both interfaces, tor relay listening on ip4

[tor-relays] ipv6 behaviour consensus

Hi list, Last reply from s7r on jake Visser' issue included a link to an open issue waiting for a consensus on a mailing list: https://trac.torproject.org/projects/tor/ticket/29570 Not sure if teor implied the dev mailing list or this one, but maybe gathering feedback from operators is a good

Re: [tor-relays] IPv6 not provided, guard relay

Thank you! I'll wait... Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ Am Samstag, 6. April 2019 09:28 schrieb nusenu : > No, IPv6 is not required for any type of tor relay. > > > > https://twitter.com/nusenu_ >

Re: [tor-relays] IPv6 not provided, guard relay

No, IPv6 is not required for any type of tor relay. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org

[tor-relays] IPv6 not provided, guard relay

Hello! I have read that it's recommended to enable IPv6 for a tor middle relay. But my provider doesn't offer IPv6. Is IPv6 required to become a guard middle relay? Yours Sent with [ProtonMail](https://protonmail.com) Secure Email.___ tor-relays

Re: [tor-relays] IPv6 ORPort autodetection on relays (Was: Re: Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".)

Op 01/03/2019 om 10:20 schreef Roman Mamedov: There are no globally designated "temporary" or "permanent" address ranges. Temporary addresses are created by the OS in the same /64 subnet received from the upstream router as other IPs. See https://tools.ietf.org/html/rfc4941 (There are the ULA

Re: [tor-relays] IPv6 ORPort autodetection on relays (Was: Re: Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".)

On Fri, 1 Mar 2019 11:54:31 +1000 teor wrote: > > I'd love that too -- but the thing I am thinking now is how to address > > the temporary addresses that are used in operating systems (in some my > > default, in some not by default)? Those addresses change over time > > randomly, and maybe more

Re: [tor-relays] IPv6 ORPort autodetection on relays (Was: Re: Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".)

> On 1 Mar 2019, at 10:26, s7r wrote: > > teor wrote: >> >> >> Cc'ing Linus, because he is also interested in IPv6. >> >> On 28 Feb 2019, at 19:01, s7r mailto:s...@sky-ip.org>> >> wrote: >>> >>> However, shouldn't the line: >>> ORPort 9050 >>> >>> bind to all v4 and v6 available interfaces

Re: [tor-relays] IPv6 ORPort autodetection on relays (Was: Re: Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".)

teor wrote: > Hi, > > Cc'ing Linus, because he is also interested in IPv6. > > On 28 Feb 2019, at 19:01, s7r mailto:s...@sky-ip.org>> > wrote: >> >> However, shouldn't the line: >> ORPort 9050 >> >> bind to all v4 and v6 available interfaces / IP addresses? If it does >> not, we should fix it to

[tor-relays] IPv6 ORPort autodetection on relays (Was: Re: Running 2 relays with 0.4.0.2_alpha [err] descriptor at 0x8a0acdb0830 begins with unexpected string "".)

Hi, Cc'ing Linus, because he is also interested in IPv6. > On 28 Feb 2019, at 19:01, s7r wrote: > > However, shouldn't the line: > ORPort 9050 > > bind to all v4 and v6 available interfaces / IP addresses? If it does > not, we should fix it to do so. As in: > > ORPort 9050 - bind to all

Re: [tor-relays] IPv6 and bridges

On 7/5/18 1:49 AM, teor wrote: > But there seems to be a bug right now: > https://trac.torproject.org/projects/tor/ticket/26542 > >> Will they then operate somewhat in the fashion of guards without >> published metrics? > > They will appear on Relay Search under the hash of their fingerprint. >

Re: [tor-relays] IPv6 on DSL

Thank you for your hint Ralph - the domain could be spoofing :-), but yes you are right, its non exit traffic. @nusenu: what whould be this list without you - thanks!! > > Based on your email domain and your question about a dynamic DSL link, > I'm guessing you are considering running a Tor

Re: [tor-relays] IPv6 on DSL

On 20.09.18 16:54, Paul wrote: > Can Tor cope with a daily changing IPv6 Address? Based on your email domain and your question about a dynamic DSL link, I'm guessing you are considering running a Tor relay at home? As stated in https://www.torproject.org/docs/faq-abuse.html.en : "In general,

Re: [tor-relays] IPv6 on DSL

Paul: > Can Tor cope with a daily changing IPv6 Address? unfortunatelly the IPv6 address currently has to be in the torrc file, so a daily changing IPv6 address won't be much fun -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital

[tor-relays] IPv6 on DSL

Can Tor cope with a daily changing IPv6 Address? If so, are there any additional inputs in torrc to be made as "ip addr|grep inet6|grep global" is not giving a fix value (global noprefixroute dynamic ) Thanks Paul ___ tor-relays mailing list

Re: [tor-relays] IPv6 and bridges

> On 5 Jul 2018, at 04:17, arisbe wrote: > > Hello to you all, > > Question: Is there a point to adding IPv6 addresses to the ORPorts of my > bridges? BridgeDB has an IPv6 option: https://bridges.torproject.org/options But there seems to be a bug right now:

[tor-relays] IPv6 and bridges

Hello to you all, Question:  Is there a point to adding IPv6 addresses to the ORPorts of my bridges?  Will they then operate somewhat in the fashion of guards without published metrics? Any info would be helpful. Arisbe ___ tor-relays mailing

Re: [tor-relays] IPv6 for the nifty?

Paul Templeton: > >> I was wondering if you have any plans to get IPv6 connectivity? > > At three of the ISPs i use have IPv6 available but my skill set is vastly > lacking. I would love to find a mentor to assist with configs. this should get you started:

Re: [tor-relays] IPv6 for the nifty?

> I was wondering if you have any plans to get IPv6 connectivity? At three of the ISPs i use have IPv6 available but my skill set is vastly lacking. I would love to find a mentor to assist with configs. IPv6 is the future. Paul 609662E824251C283164243846C035C803940378

Re: [tor-relays] IPv6 for the nifty?

Original Message On 26 Feb 2018, 19:52, nusenu wrote: > I was wondering if you have any plans to get IPv6 connectivity? As it happens AS28715 (BrassHornComms) is looking for any datacenters / ISPs that support IPv6 BGP peering from small (~1u / VPS) customers. I've got a /32

[tor-relays] IPv6 for the nifty?

Hi Markus, since you are by far the biggest exit relay operator I was wondering if you have any plans to get IPv6 connectivity? thanks, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_ signature.asc Description: OpenPGP digital signature

Re: [tor-relays] IPv6 Issue with Relay

Thank you. It’s always the small things, huh? :D Conrad > On Dec 21, 2017, at 6:12 PM, teor wrote: > > >> On 22 Dec 2017, at 09:13, Conrad Rockenhaus wrote: >> I’ve confirmed that the following entries are in torrc: ORPort 9001

Re: [tor-relays] IPv6 Issue with Relay

> On 22 Dec 2017, at 09:13, Conrad Rockenhaus wrote: > >>> I’ve confirmed that the following entries are in torrc: >>> >>> ORPort 9001 >>> ORPort [2600:1f14:ede:d601:e107:1a4b:ba3:803]:9001 >>> IPv6Exit 1 >> ... >> Also, you have set IPv6Exit, but Relay Search says: >>

Re: [tor-relays] IPv6 Issue with Relay

On Dec 21, 2017, at 3:01 AM, teor wrote:On 21 Dec 2017, at 16:33, Conrad Rockenhaus wrote:Hello,One of the relays that I brought online yesterday, ConradsAWSExit (Hash 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the IPv6 OR is

Re: [tor-relays] IPv6 Issue with Relay

> On 21 Dec 2017, at 16:33, Conrad Rockenhaus wrote: > > Hello, > > One of the relays that I brought online yesterday, ConradsAWSExit (Hash > 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the > IPv6 OR is unreachable. > > The other relay is

Re: [tor-relays] IPv6 Issue with Relay

On 12/21/2017 06:33 AM, Conrad Rockenhaus wrote: > Hello, > > One of the relays that I brought online yesterday, ConradsAWSExit (Hash > 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the > IPv6 OR is unreachable. Just a guess: IPv6 needs ICMPv6, so you should have

[tor-relays] IPv6 Issue with Relay

Hello, One of the relays that I brought online yesterday, ConradsAWSExit (Hash 1B47E33F9D422CC97BD2DDA1F082BFF2FC58E79A) is showing up on Atlas that the IPv6 OR is unreachable. The other relay is working just fine with IPv6. I’ve confirmed that the following entries are in torrc: ORPort 9001

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

> On 5 Jul 2017, at 10:27, Fof582 wrote: > >> Most tor clients send a DNS name, and flags that say whether they >> allow IPv4 and IPv6, and which one they prefer. They rely on the Exit >> to resolve the IP address and connect to the site. >> >> On the current network, an

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

> Most tor clients send a DNS name, and flags that say whether they > allow IPv4 and IPv6, and which one they prefer. They rely on the Exit > to resolve the IP address and connect to the site. > On the current network, an IPv6-only Exit won"t get the Exit flag, and > therefore won"t get much

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

On 06/30/2017 01:43 PM, teor wrote: > >> On 30 Jun 2017, at 19:26, Mirimir wrote: >> >> On 06/29/2017 08:41 PM, teor wrote: >>> On 30 Jun 2017, at 16:55, Scott Bennett wrote: >> >> >> Also, is there a problem with having IPv6-only exit service

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

On Fri, Jun 30, 2017 at 3:41 AM, teor wrote: > Tor client anonymity relies on every relay being able to connect to every > other relay (a "clique network"). Depends on what you're up against. Assumed ability to connect to and traffic through entire consensus isn't the same as

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

> On 30 Jun 2017, at 19:26, Mirimir wrote: > > On 06/29/2017 08:41 PM, teor wrote: >> >>> On 30 Jun 2017, at 16:55, Scott Bennett wrote: > > > >>>Also, is there a problem with having IPv6-only exit service where a >>> relay is accessable via IPv4

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

On 06/29/2017 08:41 PM, teor wrote: > >> On 30 Jun 2017, at 16:55, Scott Bennett wrote: >> Also, is there a problem with having IPv6-only exit service where a >> relay is accessable via IPv4 for clients and other relays? > > Most tor clients send a DNS name, and flags

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

> On 30 Jun 2017, at 16:55, Scott Bennett wrote: > > grarpamp wrote: > >>> We don't know how to give users good anonymity when some relays can't >>> connect to other relays. This would happen if we allowed IPv4-only relays >>> and IPv6-only relays in the

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

grarpamp wrote: > > We don't know how to give users good anonymity when some relays can't > > connect to other relays. This would happen if we allowed IPv4-only relays > > and IPv6-only relays in the same network. > > With "IPv6 only" relays available in the consensus the

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

> We don't know how to give users good anonymity when some relays can't > connect to other relays. This would happen if we allowed IPv4-only relays > and IPv6-only relays in the same network. With "IPv6 only" relays available in the consensus the answer may be... when their count is the same as

Re: [tor-relays] IPv6 to IPv4 tor exit relays would fix many daily tor-problems

> On 29 Jun 2017, at 23:55, Fof582 wrote: > > I have access to a fast internet connection. This connection only have > ipv6 IP and i can access the IPv4 network over the ISPs 6to4 bridge. > > So there are already many users using one single IPv4 address at this ISP. It

Re: [tor-relays] "IPv6 only exits"

t...@afo-tm.org: > IPv6 only exits are still not possible with this patch? What do you mean exactly with "IPv6 only exits"? If you want to add a relay to the tor network that has no IPv4 address: This does not work (for a long time I guess). If you have IPv4 and IPv6 connectivity but you want

Re: [tor-relays] IPv6 exits (onionoo misinterpretation?)

> is there a specific reason why most torservers.net exits do not allow > exiting to IPv6 destinations - even if many have ORPorts on IPv6? > > ++++ > | first_seen | nickname | exit_policy_v6_summary | >

Re: [tor-relays] IPv6 exits

> On 25 Jan 2017, at 09:43, nusenu wrote: > > If you run an exit with IPv6 connectivity consider allowing IPv6 exiting > as well, currently only ~12% of tor exit capacity allows also IPv6. > > https://trac.torproject.org/projects/tor/ticket/21269#comment:3 We found two

Re: [tor-relays] IPv6 Only Exit Node

> On 21 Dec 2015, at 03:36, Toralf Förster wrote: > > Signed PGP part > On 12/15/2015 07:25 PM, Tim Wilson-Brown - teor wrote: > > > > This is wise. Tor will block your own IPv6 address, but it doesn't > > know about your subnet: > > > >> ExitPolicy reject6

Re: [tor-relays] IPv6 Only Exit Node

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12/15/2015 07:25 PM, Tim Wilson-Brown - teor wrote: > > This is wise. Tor will block your own IPv6 address, but it doesn't > know about your subnet: > >> ExitPolicy reject6 [2A02:168:4A06::]/42:* # Block my subnet > Just clarify it for me :

[tor-relays] IPv6 Only Exit Node

Hi I would like to operate an IPv6 only exit node. I.e. it's fine if tor relays through IPv4, but I want exiting traffic only through IPv6 (because I don't want my (only) IPv4 to be blocked, abused and such). The way I thought this would work is with the ExitPolicy set as below. But atlas

Re: [tor-relays] IPv6 Only Exit Node

Am 2015-12-15 um 18:23 schrieb Hans Wurscht: > Hi > > I would like to operate an IPv6 only exit node. I.e. it's fine if tor > relays through IPv4, but I want exiting traffic only through IPv6 > (because I don't want my (only) IPv4 to be blocked, abused and such). > > The way I thought this would

Re: [tor-relays] IPv6 Only Exit Node

> On 16 Dec 2015, at 04:23, Hans Wurscht wrote: > > Hi > > I would like to operate an IPv6 only exit node. I.e. it's fine if tor relays > through IPv4, but I want exiting traffic only through IPv6 (because I don't > want my (only) IPv4 to be blocked, abused and such). You won't

Re: [tor-relays] IPv6 vs IPv4 exit policies

On 12 Aug 2015, at 08:53 , n...@cock.li wrote: If I recall correctly: Policies with '*' for the address count as both ipv4 and v6 policies, it is possible to use 0.0.0.0 for v4 and [::] (I think) for v6-specfic policies. Or *4 and *6, respectively, which expand to 0.0.0.0 and [::]. So the

Re: [tor-relays] IPv6 vs IPv4 exit policies

If I recall correctly: Policies with '*' for the address count as both ipv4 and v6 policies, it is possible to use 0.0.0.0 for v4 and [::] (I think) for v6-specfic policies. spriver: Hi, I just activated IPv6 support for my two exit relays today, but I do not unterstand/misconfigured the

[tor-relays] IPv6 vs IPv4 exit policies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I just activated IPv6 support for my two exit relays today, but I do not unterstand/misconfigured the exit policies. I just want to open certain ports at IPv4 (the common known reduced exit policy) and open all Ports at IPv6 except 25. How do

[tor-relays] IPv6 slows BW?

I have two relays that I set up last night to test. They're at the same datacenter, same spec server, and configured identically. The only difference is one is set up for IPv6 and the other isn't. With IPv6 BW is at: 75kB/s Without IPv6 BW is: 110kB/s Is this normal behavior or has anyone else

Re: [tor-relays] IPv6 slows BW?

On 06/02/2015 07:31 PM, torelay wrote: I have two relays that I set up last night to test. They're at the same datacenter, same spec server, and configured identically. The only difference is one is set up for IPv6 and the other isn't. With IPv6 BW is at: 75kB/s Without IPv6 BW is: 110kB/s

Re: [tor-relays] IPv6 adress valid?

On Mon, 1 Jun 2015 20:12:29 +0200 tor-server-crea...@use.startmail.com wrote: hi, is that IPv6 adress valid for example becks [2a01:4f8:162:7345::2]? how do i know if IPv6 is correct and reachable? thanks Yes this one is correct and reachable. You can check yourself by running on any

Re: [tor-relays] IPv6 adress valid?

Use ping6, Luke On Mon, Jun 1, 2015, 21:12 tor-server-crea...@use.startmail.com wrote: hi, is that IPv6 adress valid for example becks [2a01:4f8:162:7345::2]? how do i know if IPv6 is correct and reachable? thanks ___ tor-relays mailing list

Re: [tor-relays] IPv6 adress valid?

On 06/01/2015 08:12 PM, tor-server-crea...@use.startmail.com wrote: hi, is that IPv6 adress valid for example becks [2a01:4f8:162:7345::2]? how do i know if IPv6 is correct and reachable? thanks http://www.subnetonline.com/pages/ipv6-network-tools/online-ipv6-port-scanner.php?input=your

  1   2   >