In my implementation of the loadbalanced OBFS4 configuration, it appears that BridgeDB still tests the ORPort for availability and without it marks the OBFS4 bridge as being down.
I gather that default bridges don't require a DistributionMethod as your loadbalanced Snowflake configuration is set to "none?"
BTW... I have the loadbalanced OBFS4 configuration up and running, and am able to manually confirm loadbalanced OBFS4 connections are successfull.
nginx => obfs4proxy => tor
I believe it's time to enable a DistributionMethod.
Thank you for the clarifications.
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 Thursday, December 8, 2022, 10:03:09 PM PST, David Fifield <david@bamsoftware.com> wrote:
On Fri, Dec 09, 2022 at 01:09:05AM +0000, Gary C. New wrote: > Is it truly necessary to expose the ORPort to the World in a pluggable > transport configuration?
I don't know if it is necessary for ordinary bridges to expose the ORPort. For a long time, it was necessary, because BridgeDB used the ORPort to check that a bridge was running, before distributing it to users. See: https://bugs.torproject.org/tpo/core/tor/7349 But now there is rdsys and bridgestrap, which may have the ability to test the obfs4 port rather than the ORPort. I cannot say whether that removes the requirement to expose the ORPort. https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/merge_requests/36