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,
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 wit
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 ;
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 Week
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-re
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, offerin
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 netw
