[tor-relays] Fw: Re: Bridge distribution method stuck at "none"

Fri Dec 24 13:50:46 UTC 2021

Hello again.

I'm found it weird that all resources says that "Distribution mechanism"
should change after a few days and mine was still "none".
So now I'm trying torix's suggestion and deleted the keys and all the
/var/lib/tor/ directory, changed nickname and started it again.

The hashed fingerprint for my bridge is
now: 3B5D1AE581EE4113610E094D5993D6299E64EDEF
Its the same torrc file I shared before, just new nickname.

This is the log of the last heartbeats is the following, minus timestamps
(I will update after one week):
/var/log/tor# cat notices.log.1 notices.log | grep Heart | grep -v
Accounting
[notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've
sent 1.89 MB and received 5.37 MB. I've received 38 connections on IPv4 and
38 on IPv6. I've made 26 connections with IPv4 and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
[notice] Heartbeat: Tor's uptime is 12:00 hours, with 0 circuits open. I've
sent 3.13 MB and received 9.85 MB. I've received 71 connections on IPv4 and
71 on IPv6. I've made 53 connections with IPv4 and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
[notice] Heartbeat: Tor's uptime is 18:00 hours, with 10 circuits open.
I've sent 5.93 MB and received 16.49 MB. I've received 141 connections on
IPv4 and 140 on IPv6. I've made 85 connections with IPv4 and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
[notice] Heartbeat: Tor's uptime is 1 day 0:00 hours, with 15 circuits
open. I've sent 7.37 MB and received 21.77 MB. I've received 175
connections on IPv4 and 174 on IPv6. I've made 114 connections with IPv4
and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
[notice] Heartbeat: Tor's uptime is 1 day 6:00 hours, with 14 circuits
open. I've sent 8.46 MB and received 27.03 MB. I've received 194
connections on IPv4 and 193 on IPv6. I've made 136 connections with IPv4
and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.
[notice] Heartbeat: Tor's uptime is 1 day 12:00 hours, with 15 circuits
open. I've sent 9.47 MB and received 31.66 MB. I've received 212
connections on IPv4 and 210 on IPv6. I've made 162 connections with IPv4
and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 1 unique clients.
[notice] Heartbeat: Tor's uptime is 1 day 18:00 hours, with 15 circuits
open. I've sent 10.64 MB and received 36.48 MB. I've received 229
connections on IPv4 and 227 on IPv6. I've made 181 connections with IPv4
and 0 with IPv6.
[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.

I also added a IPv4 iptables rule just to count the traffic:
# iptables -vnL|grep TOR
74451   14M ACCEPT     tcp  --  *      *       0.0.0.0/0
0.0.0.0/0            multiport dports 6661:6662 /* TOR R */
#

Is this ammount of connections/clients normal for the first day of a bridge?
Thanks

El mar, 21 dic 2021 a las 20:10, torix (<***>) escribió:

> I'm writing you at gmail because I got a note from the list admin saying
> they couldn't moderate my post because they couldn't decrypt it, so were
> refusing it.  However, you do seem to have seen my post, so I'm a bit
> confused about posting to the list.
>
> Since you don't seem to be getting anyone connecting with your current
> bridge and you are still stuck at "none", I'd think about just deleting the
> keys directory:
> /var/lib/tor/keys/ in linux
> /var/db/tor/keys in freeBSD
> This directory holds the actual identity of the tor relay, so if you
> delete it and restart tor, it will make a new key and start as a completely
> new relay, and give metrics a new chance to give you a bridge type.
> The lifecycle of a new relay post which gives a month before it settles in
> does not mean that you shouldn't be getting some connections in the first
> few days.  At least that has been my experience in the last few weeks
> putting up a couple of bridges in response to the Tor Project's call.  I
> started getting 1-5 concurrent connections in the first day.   I wish I'd
> been paying more attention, but I certainly had a bridge type assigned in
> the first or second day of running.
>
> Good Luck!
>
> --Torix
>
> Sent with ProtonMail <https://protonmail.com/> Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, December 21st, 2021 at 4:03 PM, - <damisame at gmail.com> wrote:
>
> Hi.
> Thanks for the suggestions.
> I thought it will take a couple of days to show activity, not a couple of
> months.
>
> This is my torrc:
> -------------
> BridgeRelay 1
> BridgeDistribution any
> PublishServerDescriptor 1
> Log notice file /dev/shm/tor-notices-bridge.log
> RunAsDaemon 1
> RelayBandwidthRate 2000 KB
> RelayBandwidthBurst 3000 KB
> AccountingMax 5120 GB
> AccountingStart month 1 00:00
> ORPort 6661
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ServerTransportListenAddr obfs4 0.0.0.0:6662
> ExtORPort auto
> ContactInfo <address at email.com>
> Nickname *(editted)*
> ------------------
>
> Ports 6661-2 are reachable externally.
>
> https://bridges.torproject.org/status says:
>
> * obfs4: functional
>   Last tested: 2021-12-21 04:39:48.514002439 +0000 UTC (11h19m41.110084213s ago)
>
>
> Thanks
>
> El mar, 21 dic 2021 a las 16:57, <lists at for-privacy.net> escribió:
>
>> On Sunday, December 19, 2021 5:47:29 PM CET - wrote:
>>
>> > However I dont see practically any traffic besides when I'm using it,
>> and
>> > on "Relay Search" it shows as "Bridge distribution mechanism: None".
>> > The bridge has been up and running for 10 days straigth.
>> It can take many weeks or months before the first users start using the
>> bridge.
>>
>> > At first I only had the line: "PublishServerDescriptor 1".
>> This is default ...
>>
>> > After five days, I tried adding "BridgeRelay 1"
>> ... if you set 'BridgeRelay 1' (this is absolutely necessary to be a
>> bridge)
>>
>> > and "BridgeDistribution
>> > moat", "https" and "any".
>> AFAIK only none or any (default) can be set. BridgeDB then automatically
>> assigns 'https, moat, Email or reseved'
>>
>> man torrc | grep Bridge
>> BridgeDistribution string
>> If set along with BridgeRelay, Tor will include a new line in its bridge
>> descriptor which indicates to the BridgeDB service how it would like its
>> bridge address to be given out. Set it to "none" if you want BridgeDB to
>> avoid distributing your bridge address, or "any" to let BridgeDB decide.
>> See https://bridges.torproject.org/info for a more up-to-date list of
>> options. (Default: any)
>>
>> > Neither seems to have produced any change.
>> >
>> > Is this normal or could I have missed something on the configuration?
>> Don't forget obfs4:
>>
>> ## obfs4 is used because it can do IPv4 and IPv6 connections
>> simultaneously
>> ##
>> https://gitweb.torproject.org/pluggable-transports/obfs4.git/tree/README.md
>> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
>>
>> ## The ServerTransportListenAddr line is dual stack friendly.
>> ServerTransportListenAddr obfs4 [::]:443
>>
>> > Thank you.
>> If there are further problems, it is best to post your whole torrc:
>> ~$ grep ^[^#] /etc/tor/torrc
>>
>> --
>> ╰_╯ Ciao Marco!
>>
>> Debian GNU/Linux
>>
>> It's free software and it gives you
>> freedom!_______________________________________________
>> tor-relays mailing list
>> tor-relays at lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20211224/c7e11e03/attachment.htm>