[tor-relays] Bridge distribution mechanism thoughts

[a tor op via tor-relays]

I have a few questions,

I have two obfs4 bridges updated with sw, one old since a few years and the 
other very new.

The older one I now notice all of a sudden have gotten distribution mechanisms 
'none'. It had 'moat' earlier, what would make it change like this? It usually 
has between 50-100 users according to metrics page.

The new bridge should be somewhat not/little used for some time according to 
lifecycle info on relays found online. I do however wonder if I should expect 
to see some users after 16 days?

Another wonder about the new bridge is yet again distribution mechanism, it has 
'email', is that really much used? Generally speaking I want my time and money 
to get the most use possible of course. How much use does the 'telegram' 
mechanism get?

Maybe someone can give some comments before I (possibly) change it manually on 
either of those bridges.

A tor op___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bridge Distribution Mechanism none

[lists]

On Wednesday, April 20, 2022 10:22:54 AM CEST Ross Camm wrote:
>  I have no error from Apparmor and I dont believe obfs4 proxy is the issue
> as I have obfs4 installed and confirmed running
> 
> dpkg -l | grep obfs4
> ii obfs4proxy 0.0.7-4
> 
> ps ax | grep obfs4
> 5501 ? Sl 0:01 /usr/bin/obfs4proxy
> 
> netstat -nap | grep obfs4
> tcp 0 0 X.X.X.X:12345 0.0.0.0:* LISTEN 5501/obfs4proxy
> 
> Tor logs
> 
>  Apr 18 17:00:33 pi Tor[5497]: Registered server transport 'obfs4' at
> 'X.X.X.X:12345'
> 
> torrc
> 
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 X.X.X.X:12345
> 
> [ https://bridges.torproject.org/scan/ ](
> https://bridges.torproject.org/scan/ )
> 
> also reports my ORPort is reachable via IPv4 and IPV6
> 
> Tor logs
> 
> Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort
> [X:Y:Z::A]:993 is reachable from the outside. Excellent. Apr 18 17:01:37 pi
> Tor[5497]: Self-testing indicates your ORPort A.B.C.D:993 is reachable from
> the outside. Excellent. Publishing server descriptor.
> 
> What am I missing ?
> 

Just to test, not 'PublishServerDescriptor bridge' try 1 (default):

BridgeRelay 1
PublishServerDescriptor 1
BridgeDistribution moat

If that doesn't work I would try the default 'any' here too:
BridgeDistribution any

-- 
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!

signature.asc
Description: This is a digitally signed message part.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bridge Distribution Mechanism none

[gus]

Hi Ross,

Could you disable your bridge IPv6 and see if it works?

Gus

On Wed, Apr 20, 2022 at 06:41:45PM +1000, Ross Camm wrote:
> 
> Thanks, that will no doubt be an issue
>  
> Upgraded via debian backports
>  
> dpkg -l | grep obfs4
> ii obfs4proxy 0.0.13-1~bpo11+1
>  
>  
> I will keep my eye on the bridge status page to see if the Bridge Mechanism 
> changes as well as my incoming connections. 
>  
> Regards
> Ross
>  
> Date: Tue, 19 Apr 2022 15:59:35 +0200
> From: li...@for-privacy.net
> To: tor-relays@lists.torproject.org
> Subject: Re: [tor-relays] Bridge Distribution Mechanism none
> Message-ID: <2335525.61UdpqZOmS@w530>
> Content-Type: text/plain; charset="utf-8"
> On Tuesday, April 19, 2022 2:28:01 PM CEST 55578 via tor-relays wrote:
> > Probably because obfs4 is not installed or not running properly.
> Get the obfs4proxy package from backports. Outdated obfs bridges are rejected
> AFAIK.
> https://lists.torproject.org/pipermail/tor-relays/2022-March/020447.html
> --
> ?_? Ciao Marco!
> Debian GNU/Linux
> It's free software and it gives you freedom!

> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


-- 
The Tor Project
Community Team Lead


signature.asc
Description: PGP signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Bridge Distribution Mechanism none

[Ross Camm]

Thanks, that will no doubt be an issue
 
Upgraded via debian backports
 
dpkg -l | grep obfs4
ii obfs4proxy 0.0.13-1~bpo11+1
 
 
I will keep my eye on the bridge status page to see if the Bridge Mechanism 
changes as well as my incoming connections. 
 
Regards
Ross
 
Date: Tue, 19 Apr 2022 15:59:35 +0200
From: li...@for-privacy.net
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] Bridge Distribution Mechanism none
Message-ID: <2335525.61UdpqZOmS@w530>
Content-Type: text/plain; charset="utf-8"
On Tuesday, April 19, 2022 2:28:01 PM CEST 55578 via tor-relays wrote:
> Probably because obfs4 is not installed or not running properly.
Get the obfs4proxy package from backports. Outdated obfs bridges are rejected
AFAIK.
https://lists.torproject.org/pipermail/tor-relays/2022-March/020447.html
--
?_? Ciao Marco!
Debian GNU/Linux
It's free software and it gives you freedom!___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bridge Distribution Mechanism none

[Ross Camm]

 I have no error from Apparmor and I dont believe obfs4 proxy is the issue as I 
have obfs4 installed and confirmed running
 
dpkg -l | grep obfs4
ii obfs4proxy 0.0.7-4
 
ps ax | grep obfs4
5501 ? Sl 0:01 /usr/bin/obfs4proxy
 
netstat -nap | grep obfs4
tcp 0 0 X.X.X.X:12345 0.0.0.0:* LISTEN 5501/obfs4proxy
 
Tor logs
 
 Apr 18 17:00:33 pi Tor[5497]: Registered server transport 'obfs4' at 
'X.X.X.X:12345'
 
torrc
 
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
ServerTransportListenAddr obfs4 X.X.X.X:12345
 
[ https://bridges.torproject.org/scan/ ]( https://bridges.torproject.org/scan/ )
 
also reports my ORPort is reachable via IPv4 and IPV6
 
Tor logs
 
Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort [X:Y:Z::A]:993 
is reachable from the outside. Excellent.
Apr 18 17:01:37 pi Tor[5497]: Self-testing indicates your ORPort A.B.C.D:993 is 
reachable from the outside. Excellent.
Publishing server descriptor.
 
What am I missing ?
 
Thanks again
 
Ross
> Probably because obfs4 is not installed or not running properly.> Check your 
> logs for obfs4 errors, and for Apparmor error messages as well.> On Mon, Apr 
> 18, 2022 at 09:07, Ross Camm  wrote:> I have been up and 
> running with my Tor Bridge for a number of months now, yet Tor Metrics 
> reports that the Bridge Distribution Mechanism for my server is stuck on 
> 'none'.>> Consequently I see no incoming connections to my Bridge.>> I have 
> tried altering the following>> BridgeRelay 1>> PublishServerDescriptor 
> bridge> BridgeDistribution moat>> with no success.>> The mechanism is always 
> noneand I have left the changes for a week to see if Metrics updates to 
> no avail.>> I have a static IPv4 address and functional IPv6 and have 
> confirmed my ports are publicly accessible for both protocols>> Self-testing 
> indicates your ORPort [::::XXX]:993 is reachable from the 
> outside. Excellent.> Self-testing indicates your ORPort XXX.XXX.XXX.XXX:993 
> is reachable from the outside. Excellent. Publishing server descriptor.>> I 
> am running raspberry pi os buster which had an obsolete Tor version.>> I 
> subsequently upgraded and stay up to date with the latest bullseye version 
> via bullseye backports,>> Currently Tor 0.4.6.10-1~bpo10+1>> Any ideas of why 
> my servers Bridge Distribution Mechanism is always reported and behaving as 
> none ?>> Thanks in advance ;)>> Ross
 
 ___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bridge Distribution Mechanism none

[lists]

On Tuesday, April 19, 2022 2:28:01 PM CEST 55578 via tor-relays wrote:
> Probably because obfs4 is not installed or not running properly.
Get the obfs4proxy package from backports. Outdated obfs bridges are rejected 
AFAIK.

https://lists.torproject.org/pipermail/tor-relays/2022-March/020447.html

-- 
╰_╯ Ciao Marco!

Debian GNU/Linux

It's free software and it gives you freedom!

signature.asc
Description: This is a digitally signed message part.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bridge Distribution Mechanism none

[55578 via tor-relays]

Probably because obfs4 is not installed or not running properly.

Check your logs for obfs4 errors, and for Apparmor error messages as well.

On Mon, Apr 18, 2022 at 09:07, Ross Camm  wrote:

> I have been up and running with my Tor Bridge for a number of months now, yet 
> Tor Metrics reports that the Bridge Distribution Mechanism for my server is 
> stuck on 'none'.
>
> Consequently I see no incoming connections to my Bridge.
>
> I have tried altering the following
>
> BridgeRelay 1
>
> PublishServerDescriptor bridge
> BridgeDistribution moat
>
> with no success.
>
> The mechanism is always noneand I have left the changes for a week to see 
> if Metrics updates to no avail.
>
> I have a static IPv4 address and functional IPv6 and have confirmed my ports 
> are publicly accessible for both protocols
>
> Self-testing indicates your ORPort [::::XXX]:993 is reachable 
> from the outside. Excellent.
> Self-testing indicates your ORPort XXX.XXX.XXX.XXX:993 is reachable from the 
> outside. Excellent. Publishing server descriptor.
>
> I am running raspberry pi os buster which had an obsolete Tor version.
>
> I subsequently upgraded and stay up to date with the latest bullseye version 
> via bullseye backports,
>
> Currently Tor 0.4.6.10-1~bpo10+1
>
> Any ideas of why my servers Bridge Distribution Mechanism is always reported 
> and behaving as none ?
>
> Thanks in advance ;)
>
> Ross___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Bridge Distribution Mechanism none

[Ross Camm]

I have been up and running with my Tor Bridge for a number of months now, yet 
Tor Metrics reports that the Bridge Distribution Mechanism for my server is 
stuck on 'none'.
 
Consequently I see no incoming connections to my Bridge.
 
I have tried altering the following
 
 
BridgeRelay 1
PublishServerDescriptor bridge
BridgeDistribution moat 
 
with no success.
The mechanism is always noneand I have left the changes for a week to see 
if Metrics updates to no avail.
 
I have a static IPv4 address and functional IPv6 and have confirmed my ports 
are publicly accessible for both protocols
 
Self-testing indicates your ORPort [::::XXX]:993 is reachable from 
the outside. Excellent.
Self-testing indicates your ORPort XXX.XXX.XXX.XXX:993 is reachable from the 
outside. Excellent. Publishing server descriptor.
 
I am running raspberry pi os buster which had an obsolete Tor version.
I subsequently upgraded and stay up to date with the latest bullseye version 
via bullseye backports,
 
Currently Tor 0.4.6.10-1~bpo10+1
 
Any ideas of why my servers Bridge Distribution Mechanism is always reported 
and behaving as none  ?
 
Thanks in advance ;)
 
Ross___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] bridge distribution mechanism

[Roger Dingledine]

On Sun, Dec 12, 2021 at 10:52:42AM +0100, trinity pointard wrote:
> There are multiple bridges distributions mechanism. One is chosen at random
> when your bridge first come to life, each being perfectly fine :
> - moat: distributed automatically to Tor Browser users
> - https: distributed on bridge-db website after solving a captcha
> https://bridges.torproject.org/
> - email: distributed when sending an email to brid...@torproject.org)
> - reserved: distributed manually, mostly in-person I imagine
> 
> The only distribution mechanism you might want to worry about is "none", it
> either mean your bridge is really young and bridge-db is not distributing
> it yet (it should only be in that state for about a few hours), or you
> decided to distribute this bridge yourself (no bridge-db involved, by
> setting  `BridgeDistribution none` in your torrc), or your bridge is down.

Right, exactly.

Two more documentation resources that could be helpful:

* The relay-search page makes each "Bridge distribution mechanism"
into a link to its entry on
https://bridges.torproject.org/info

* You can read about the original design idea here:
https://svn-archive.torproject.org/svn/projects/design-paper/blocking.html#tth_sEc7.4

And for those who enjoy reading even more, check out these blog posts
which detail the open research areas:
* https://blog.torproject.org/strategies-getting-more-bridge-addresses
* https://blog.torproject.org/research-problems-ten-ways-discover-tor-bridges
* 
https://blog.torproject.org/research-problem-five-ways-test-bridge-reachability

--Roger

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] bridge distribution mechanism

[trinity pointard]

Hi,

There are multiple bridges distributions mechanism. One is chosen at random
when your bridge first come to life, each being perfectly fine :
- moat: distributed automatically to Tor Browser users
- https: distributed on bridge-db website after solving a captcha
https://bridges.torproject.org/
- email: distributed when sending an email to brid...@torproject.org)
- reserved: distributed manually, mostly in-person I imagine

The only distribution mechanism you might want to worry about is "none", it
either mean your bridge is really young and bridge-db is not distributing
it yet (it should only be in that state for about a few hours), or you
decided to distribute this bridge yourself (no bridge-db involved, by
setting  `BridgeDistribution none` in your torrc), or your bridge is down.

Le dim. 12 déc. 2021 à 10:32, potlatch via tor-relays <
tor-relays@lists.torproject.org> a écrit :

> Hello Tor universe,
> One of the bridges I recently set up shows the Bridge distribution
> mechanism as *https*:
> Question:  Is this an issue or does it impact the functionality of the
> bridge?
> Or maybe I made a boo boo during setup.  Most of my bridges report Moat as
> the mechanism.  Just trying to learn something.
> Best,
> potlatch
>
> Sent with ProtonMail  Secure Email.
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] bridge distribution mechanism

[potlatch via tor-relays]

Hello Tor universe,
One of the bridges I recently set up shows the Bridge distribution mechanism as 
https:
Question: Is this an issue or does it impact the functionality of the bridge?
Or maybe I made a boo boo during setup. Most of my bridges report Moat as the 
mechanism. Just trying to learn something.
Best,
potlatch

Sent with [ProtonMail](https://protonmail.com/) Secure Email.___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays