[tor-relays] rdsys was ignoring BridgeDistribution

[Fran]

Hey,

never mind, with some coffee I find them :blush:

Not blocked in Russia (yet) \o/

Thanks anyway and have a great weekend!

Fran

On 3/4/22 19:08, Fran via tor-relays wrote:
> Hey,
> 
> stuff like this happens meskio, thanks for the effort!
> 
> Slightly off topic:
> 
> I couldn't find my bridges in the files under
> 
> https://metrics.torproject.org/collector/recent/bridge-pool-assignments/
> 
> But they seem to work (although not getting much traffic):
> 
> Heartbeat: Tor's uptime is 16 days 6:00 hours, with 39 circuits open. 
> I've sent 31.25 GB and received 34.24 GB. I've received 9792 connections 
> on IPv4 and 1095 on IPv6. I've made 54819 connections with IPv4 and 
> 16694 with IPv6.
> While not bootstrapping, fetched this many bytes: 247726854 (server 
> descriptor fetch); 22993 (server descriptor upload); 26840442 (consensus 
> network-status fetch); 1784 (authority cert fetch); 2540630 
> (microdescriptor fetch)
> 
> 
> https://bridges.torproject.org/status?id=<fp> returns:
> 
> Bridge <fp> advertises:
> 
> * obfs4: functional
>    Last tested: 2022-03-04 16:28:39.248278403 +0000 UTC 
> (1h26m57.466661568s ago)
> 
> Setting is "BridgeDistribution any"
> 
> Any ideas why this might be?
> 
> Thanks,
> fran
> 
> 
> On 3/4/22 16:56, meskio wrote:
>> As mentioned before[0] BridgeDB now uses rdsys as backend. I just 
>> found out that
>> there was a bug in rdsys and the BridgeDistribution configuration was 
>> ignored.
>>
>> Private bridges configured with 'BridgeDistribution none' might have 
>> being
>> distributed by bridgedb if they were not configured with
>> 'PublishServerDescriptor 0'. Disabling PublishServerDescriptor stops 
>> the bridge
>> from sending it's descriptor to the bridge authority, so rdsys doesn't 
>> know it
>> exists.
>>
>> Other bridges configured to be used by an specific distributor might 
>> have being
>> distributed by a different one.
>>
>> This has being happening from February 28th ~12:00UTC until today March 4
>> ~12:00UTC.
>>
>> You can search for your hashed fingerprint in the pool assignments 
>> during this
>> period if you want to know to what distributor was your bridge 
>> assigned to:
>>    
>> https://metrics.torproject.org/collector/recent/bridge-pool-assignments/
>> Only bridges assigned to moat, email or https might have being 
>> distributed, as
>> telegram, settings and reserved bridges are not distributed at the 
>> moment.
>>
>> The metrics relay search[1] will take some time to display the new 
>> assignments.
>> I'm sorry for the situation.
>>
>>
>> [0] 
>> https://lists.torproject.org/pipermail/tor-relays/2022-February/020365.html 
>>
>> [1] https://metrics.torproject.org/rs.html
>>
>>
>> _______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays