Re: [tor-relays] Moving Bridges
Marco, You are absolutely correct. I had relays on my mind. Thank you for the correction. Respectfully, Gary— This Message Originated by the Sun. iBigBlue 63W Solar Array (~12 Hour Charge) + 2 x Charmast 26800mAh Power Banks = iPhone XS Max 512GB (~2 Weeks Charged) On Friday, March 11, 2022, 2:52:30 PM MST, li...@for-privacy.net wrote: On Friday, March 11, 2022 9:39:14 PM CET Gary C. New via tor-relays wrote: > It's to allow a Tor Relay to continue to build on an established reputation > and avoid the ramp-up cycle of a new Tor Relay. Respectfully, Bridges don't have a ramp up phase. After a few hours they are in the Bridge DB ;-) -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!___ 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
Re: [tor-relays] Flooding of unbound via resolve attempts
On Thursday, March 10, 2022 9:33:07 AM CET Georg Koppen wrote: > It seems that someone (intentionally or not) is overwhelming unbound > leading to DNS resolution issues for those exit operators that do run > this local resolver, which we currently recommend. Yes, I had this rubbish on exits with unbound for a few days recently: https://paste.debian.net/1233888/ On colocation machines¹ that are connected with 10G and more, I and other exit operators use powerdns + dnsdist. ¹A new server is currently on its way to the data center :-) -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Moving Bridges
On Friday, March 11, 2022 9:39:14 PM CET Gary C. New via tor-relays wrote: > It's to allow a Tor Relay to continue to build on an established reputation > and avoid the ramp-up cycle of a new Tor Relay. Respectfully, Bridges don't have a ramp up phase. After a few hours they are in the Bridge DB ;-) -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Moving Bridges
Toralf, It's to allow a Tor Relay to continue to build on an established reputation and avoid the ramp-up cycle of a new Tor Relay. Respectfully, Gary— This Message Originated by the Sun. iBigBlue 63W Solar Array (~12 Hour Charge) + 2 x Charmast 26800mAh Power Banks = iPhone XS Max 512GB (~2 Weeks Charged) On Friday, March 11, 2022, 11:44:12 AM MST, Toralf Förster wrote: On 3/8/22 19:48, Eddie wrote: > as I'm certain that there's no way to "move" them to the new location Yes. And that's why I do wonder why you want to "continue" the stats ? -- Toralf ___ 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
Re: [tor-relays] Moving Bridges
On 3/8/22 19:48, Eddie wrote: as I'm certain that there's no way to "move" them to the new location Yes. And that's why I do wonder why you want to "continue" the stats ? -- Toralf OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Auto-discovered IPv6 address [...] has not been found reachable.
Hej, 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 (2a02:a446:5ef1:1:d072:53ff:fef4:ea59) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server did not agree to a protocol * Server certificate: * subject: CN=www.s5uu2cs3ui4yok4.net * start date: Nov 2 00:00:00 2021 GMT * expire date: Apr 16 00:00:00 2022 GMT * issuer: CN=www.yi5r3anmk2gd3fbqrw4.com * SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. > GET / HTTP/1.1 > Host: [2a02:a446:5ef1:1:d072:53ff:fef4:ea59] > User-Agent: curl/7.82.0 > Accept: */* > * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing ^C What if you configure the IPv6 address by hand in torrc? Can you please send your torrc and the output of ip route show table all ip address show tnx & ciao, fran On 3/11/22 13:33, Onion Operator wrote: Hi Need another couple of eye balls on my relay, RealityLeighWinner. I keep reading "Auto-discovered IPv6 address [2a02:a446:5ef1:1:d072:53ff:fef4:ea59]:443 has not been found reachable..." in the logs but I actually can reach it with openssl s_client from another ipv6 box not in the same network. Could please anybody double check and maybe explain this behavior? Thanks. Oo. ___ 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] Auto-discovered IPv6 address [...] has not been found reachable.
Hi Need another couple of eye balls on my relay, RealityLeighWinner. I keep reading "Auto-discovered IPv6 address [2a02:a446:5ef1:1:d072:53ff:fef4:ea59]:443 has not been found reachable..." in the logs but I actually can reach it with openssl s_client from another ipv6 box not in the same network. Could please anybody double check and maybe explain this behavior? Thanks. Oo.___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
