Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread lists
On Monday, March 14, 2022 8:46:23 PM CET Christian Pietsch wrote: > I almost put the netcologne mirror into a blog post I co-wrote > – but then I noticed > that the download links do not work. For example, >

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread Christian Pietsch
I almost put the netcologne mirror into a blog post I co-wrote – but then I noticed that the download links do not work. For example, https://mirror.netcologne.de/dist/torbrowser/11.0.7/tor-browser-linux64-11.0.7_en-US.tar.xz → Error 404 Cheers,

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread lists
On Monday, March 14, 2022 9:19:41 AM CET Georg Koppen wrote: > > Pad notes will be posted after the meeting. > > > Here they come. Thanx a lot! > * Censorship situation in Russia: > > Since Dec 2021, the censorship department in Russia started to block > parts of the Tor network. It's not

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread Toralf Förster
On 3/14/22 09:19, Georg Koppen wrote: But, there is a lag between when a new bridge appears and when Russia starts blocking it. That lag is often a week or more these days. So, after a week the affected bridges can be stopped ? -- Toralf OpenPGP_signature Description: OpenPGP digital

Re: [tor-relays] Auto-discovered IPv6 address [...] has not been found reachable.

2022-03-14 Thread Onion Operator
> On 14/03/2022 11:07 s7r wrote: > > Onion Operator wrote: > > >> What if you configure the IPv6 address by hand in torrc? > > > > for months my torrc had > > > >ORPort 443 IPv4Only > >ORPort [2a02:a446:5ef1:1:d072:53ff:fef4:ea59]:443 IPv6Only > > > >Address XXX > > > > and read

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread Leon D
Just wanting to put this out there, I was wondering whether during the current situation in Russia is it best to run a Bridge or a Relay? I want to make sure that Tor can be easily accessed anywhere in the world, as such they are both good choices. My bandwidth is 1Gbps and I have the hardware

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread Vasilis
Hi, Georg Koppen: ## Meetup notes March 5 Thank you for sending the meetup notes Georg. With Russia blocking most western media outlets and Facebook etc. I was expecting an uptick in traffic but I saw nothing... Is Tor not well enough known maybe? Sanctions against Russia, EU council

Re: [tor-relays] Auto-discovered IPv6 address [...] has not been found reachable.

2022-03-14 Thread s7r
Onion Operator wrote: What if you configure the IPv6 address by hand in torrc? for months my torrc had ORPort 443 IPv4Only ORPort [2a02:a446:5ef1:1:d072:53ff:fef4:ea59]:443 IPv6Only Address XXX and read in the logs: Unable to find IPv6 address for ORPort 443. You might want to

Re: [tor-relays] Tor Relay Operator Meetup (Saturday, March 5th @ 2000 UTC)

2022-03-14 Thread Georg Koppen
George: On 3/5/22 13:40, flux via tor-relays wrote: Hi, will there be a recording? Unfortunately I won't be able to attend. Unfortunately not flux. We will catch you next time. Pad notes will be posted after the meeting. Here they come. On March 5, a group of 40-50 operators joined the

Re: [tor-relays] Auto-discovered IPv6 address [...] has not been found reachable.

2022-03-14 Thread Onion Operator
> Fran wrote: > Hej, Hello, > > TLS handshake succeeds for me from my laptop: > > $ curl --insecure https://[2a02:a446:5ef1:1:d072:53ff:fef4:ea59] -v > * Trying 2a02:a446:5ef1:1:d072:53ff:fef4:ea59:443... > * Connected to 2a02:a446:5ef1:1:d072:53ff:fef4:ea59 >