torix via tor-relays:
> The advertized bandwidth of my aramis family of relays has gone up from
> around 45 to 67 total since last week. ZimmerLinux (quetzalcoatl) sees
> inflation as well. I found a graph here of quetzalcoatl:
> https://nusenu.github.io/OrNetStats/quetzalcoatl-relays.org.html
>
The advertized bandwidth of my aramis family of relays has gone up from around
45 to 67 total since last week. ZimmerLinux (quetzalcoatl) sees inflation as
well. I found a graph here of quetzalcoatl:
https://nusenu.github.io/OrNetStats/quetzalcoatl-relays.org.html
which whose weekly graph current
Hello,
Did you try running obfs4proxy on Debian Buster or Bullseye and it worked?
For me it stopped working entirely. All it says is:
[warn] Pluggable Transport process terminated with status code 256
Here is what I checked so far:
- I am on Debian Bullseye with all packages up to date
- go
All:
Does anyone here know the procedure of the
router_do_orport_reachability_checks() function?
I've increased logging of my Tor Relay to info and taken several
packet-captures, but can't seem to identify connections initiated by my Tor
Relay when verifying my ORPort reachability. I just see co
