<div dir="ltr"><div>Hello again.</div><div><br></div><div>I'm found it weird that all resources says that "Distribution mechanism" should change after a few days and mine was still "none". </div><div>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.</div><div><br></div><div>The hashed fingerprint for my bridge is now: 3B5D1AE581EE4113610E094D5993D6299E64EDEF</div><div>Its the same torrc file I shared before, just new nickname.<br></div><div><br></div><div>This is the log of the last heartbeats is the following, minus timestamps (I will update after one week):</div><div>/var/log/tor# cat notices.log.1 notices.log | grep Heart | grep -v Accounting<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 1 unique clients.<br>[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.<br>[notice] Heartbeat: In the last 6 hours, I have seen 0 unique clients.<br></div><div><br></div><div>I also added a IPv4 iptables rule just to count the traffic:</div><div># iptables -vnL|grep TOR<br>74451 14M ACCEPT tcp -- * * <a href="http://0.0.0.0/0">0.0.0.0/0</a> <a href="http://0.0.0.0/0">0.0.0.0/0</a> multiport dports 6661:6662 /* TOR R */<br># <br></div><div><br></div><div>Is this ammount of connections/clients normal for the first day of a bridge?</div><div>Thanks</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El mar, 21 dic 2021 a las 20:10, torix (<***>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>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.<br></div><div><br></div><div>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:<br></div><div>/var/lib/tor/keys/ in linux<br></div><div>/var/db/tor/keys in freeBSD<br></div><div>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. <br></div><div>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.<br></div><div><br></div><div>Good Luck!<br></div><div><br></div><div>--Torix<br></div><div><br></div><div><div></div><div>Sent with <a rel="noopener noreferrer" href="https://protonmail.com/" target="_blank">ProtonMail</a> Secure Email.</div></div><div><br></div><div>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br>
On Tuesday, December 21st, 2021 at 4:03 PM, - <<a href="mailto:damisame@gmail.com" target="_blank">damisame@gmail.com</a>> wrote:<br>
<blockquote type="cite">
<div dir="ltr">Hi. <div>Thanks for the suggestions.</div><div>I thought it will take a couple of days to show activity, not a couple of months.</div><div><br></div><div>This is my torrc:</div><div>-------------</div><div>BridgeRelay 1<br>BridgeDistribution any<br>PublishServerDescriptor 1<br>Log notice file /dev/shm/tor-notices-bridge.log<br>RunAsDaemon 1<br>RelayBandwidthRate 2000 KB <br>RelayBandwidthBurst 3000 KB <br>AccountingMax 5120 GB<br>AccountingStart month 1 00:00<br>ORPort 6661<br>ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy<br>ServerTransportListenAddr obfs4 <a href="http://0.0.0.0:6662" rel="noreferrer nofollow noopener" target="_blank">0.0.0.0:6662</a><br>ExtORPort auto<br>ContactInfo <<a href="mailto:address@email.com" rel="noreferrer nofollow noopener" target="_blank">address@email.com</a>><br>Nickname *(editted)*<br></div><div>------------------</div><div><br></div><div>Ports 6661-2 are reachable externally.</div><div><pre style="color:rgb(0,0,0)"><a href="https://bridges.torproject.org/status" rel="noreferrer nofollow noopener" target="_blank">https://bridges.torproject.org/status</a> says:</pre><pre style="color:rgb(0,0,0)">* obfs4: functional
Last tested: 2021-12-21 04:39:48.514002439 +0000 UTC (11h19m41.110084213s ago)
</pre><br></div><div>Thanks</div></div><br><div class="gmail_quote"><div dir="ltr">El mar, 21 dic 2021 a las 16:57, <<a href="mailto:lists@for-privacy.net" rel="noreferrer nofollow noopener" target="_blank">lists@for-privacy.net</a>> escribió:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">On Sunday, December 19, 2021 5:47:29 PM CET - wrote:<br>
<br>
> However I dont see practically any traffic besides when I'm using it, and<br>
> on "Relay Search" it shows as "Bridge distribution mechanism: None".<br>
> The bridge has been up and running for 10 days straigth.<br>
It can take many weeks or months before the first users start using the bridge.<br>
<br>
> At first I only had the line: "PublishServerDescriptor 1".<br>
This is default ...<br>
<br>
> After five days, I tried adding "BridgeRelay 1" <br>
... if you set 'BridgeRelay 1' (this is absolutely necessary to be a bridge)<br>
<br>
> and "BridgeDistribution<br>
> moat", "https" and "any".<br>
AFAIK only none or any (default) can be set. BridgeDB then automatically assigns 'https, moat, Email or reseved'<br>
<br>
man torrc | grep Bridge<br>
BridgeDistribution string<br>
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<br>
avoid distributing your bridge address, or "any" to let BridgeDB decide. See <a rel="noreferrer nofollow noopener" href="https://bridges.torproject.org/info" target="_blank">https://bridges.torproject.org/info</a> for a more up-to-date list of options. (Default: any)<br>
<br>
> Neither seems to have produced any change.<br>
> <br>
> Is this normal or could I have missed something on the configuration?<br>
Don't forget obfs4:<br>
<br>
## obfs4 is used because it can do IPv4 and IPv6 connections simultaneously<br>
## <a rel="noreferrer nofollow noopener" href="https://gitweb.torproject.org/pluggable-transports/obfs4.git/tree/README.md" target="_blank">https://gitweb.torproject.org/pluggable-transports/obfs4.git/tree/README.md</a><br>
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy<br>
<br>
## The ServerTransportListenAddr line is dual stack friendly.<br>
ServerTransportListenAddr obfs4 [::]:443<br>
<br>
> Thank you.<br>
If there are further problems, it is best to post your whole torrc:<br>
~$ grep ^[^#] /etc/tor/torrc<br>
<br>
-- <br>
╰_╯ Ciao Marco!<br>
<br>
Debian GNU/Linux<br>
<br>
It's free software and it gives you freedom!_______________________________________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org" rel="noreferrer nofollow noopener" target="_blank">tor-relays@lists.torproject.org</a><br>
<a rel="noreferrer nofollow noopener" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br>
</blockquote></div>
</blockquote><br>
</div></blockquote></div></div>