conflux appears to be the primary source of bugs and crashes
for us in the past few months and there have been numerous
issues related to it on gitlab.
Conflux was a big change for the network and there are still some bugs that we are trying to solve. At the same time it has made things significantly better for users and it wouldn't be ideal if you disable it on all your relays. We would rather work with you to help you run your relays smoothly.
On 4/5/24 23:47, applied-privacy.net via tor-relays wrote:
from the tor manual page:
ConfluxEnabled 0|1|auto
If this option is set to 1, general purpose traffic will use Conflux which is traffic splitting among multiple legs (circuits). Onion services are not supported at the moment. Default value is set to "auto" meaning the consensus is used to decide unless
set. (Default: auto)
will
ConfluxEnabled 0
disable it for tor acting as a client only or for relays as well?
thanks!
applied-privacy.net
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org tor-relays Info Page
the tor_bug_reached metric basically becomes meaningless because it is "normal" to see that counter increase all the time.
To work around that issue we filed the following issue
which would make it possible to run exits with conflux enabled
without rendering the tor_bug_reached metric meaningless:
This tor is a relay and ConfluxEnabled is set to 0. We would ask you
to please write to us on tor-relay@lists.torproject.org or file a bug
explaining why you have disabled this option. Without news from you,
we might end up marking your relay as a BadExit.
I was wondering if you had disabled conflux for any of your relays, and if this was the case what we could do to help you and have you re-enable it again.
Talk soon,
-hiro
···
On 4/14/24 16:17, applied-privacy.net via tor-relays wrote:
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org tor-relays Info Page