tor-relays

tor-relays@lists.torproject.org

42 participants
4821 discussions

Re: [tor-relays] Bridge Distribution Mechanism none
by Ross Camm 21 Apr '22

21 Apr '22

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 <ross(a)whyza.net> 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 none....and 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 [XXXX:XXXX:XXXX::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

2 1

Bridge Distribution Mechanism none
by Ross Camm 20 Apr '22

20 Apr '22

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: lists(a)for-privacy.net To: tor-relays(a)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!

2 1

Bridges configuration
by onionize＠riseup.net 20 Apr '22

20 Apr '22

Hello, the Tor community. We already run relays and we have MyFamily configured. Now we want to start bridges. Should bridges have a separate family or we need to include them into relay family?

2 1

Another error
by onionize＠riseup.net 20 Apr '22

20 Apr '22

Hello, we tried a solution proposed by admin(a)for-privacy.net (deleting /var/lib/tor folder) but now we get another error: │ 19:41:54 [WARN] http status 400 ("Suspicious relay address range -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to │ bad-relays(a)lists.torproject.org mentioning your address(es) and fingerprint(s)?") response from dirserver 204.13.164.118:80. Please correct. │ 19:41:54 [WARN] http status 400 ("Suspicious relay address range -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to │ bad-relays(a)lists.torproject.org mentioning your address(es) and fingerprint(s)?") response from dirserver 154.35.175.225:80. Please correct. │ 19:41:54 [WARN] http status 400 ("Suspicious relay address range -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to │ bad-relays(a)lists.torproject.org mentioning your address(es) and fingerprint(s)?") response from dirserver 199.58.81.140:80. Please correct. │ 19:41:54 [WARN] http status 400 ("Suspicious relay address range -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to │ bad-relays(a)lists.torproject.org mentioning your address(es) and fingerprint(s)?") response from dirserver 86.59.21.38:80. Please correct. │ 19:41:54 [WARN] http status 400 ("Suspicious relay address range -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to │ bad-relays(a)lists.torproject.org mentioning your address(es) and fingerprint(s)?") response from dirserver 171.25.193.9:443. Please correct. │ 19:41:54 [WARN] http status 400 ("Suspicious relay address range -- if you think this is a mistake please set a valid email address in ContactInfo and send an email to │ bad-relays(a)lists.torproject.org mentioning your address(es) and fingerprint(s)?") response from dirserver 131.188.40.189:80. Please correct. Please help us if you know why it happens

2 1

Tor 0.4.5.8 died: Caught signal 7
by Gary C. New 19 Apr '22

19 Apr '22

All: I'm having an issue with a Tor Node catching signal 7 and exiting in high-load situations. ============================================================ T= 1650367869 Tor 0.4.5.8 died: Caught signal 7 /opt/sbin/tor(+0x1af500)[0x2a1af500] /opt/sbin/tor(hs_intro_received_introduce1+0x0)[0x2a09e6b8] /opt/sbin/tor(hs_intro_received_introduce1+0x0)[0x2a09e6b8] Anyone experience similar issues? Respectfully, Gary

1 0

Bridge Distribution Mechanism none
by Ross Camm 19 Apr '22

19 Apr '22

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 none....and 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 [XXXX:XXXX:XXXX::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

3 2

Instabilities in Hydra family expected
by abuse-node49＠posteo.de 19 Apr '22

19 Apr '22

Hello network! I would like to briefly inform that I have repeated problems with the hoster Yourserver.se, where I run some exit relays. Again a relay was deactivated with the message "Botnet". At that time I wrote a detailed explanation about the issue. I agreed to a temporary switch to a harmless relay, but as an exit operator I did not want to keep this state. So starting today the "Hydra family" will get some gaps which will take some time to replace. I know that there is an attempt to write a list of recommended providers somewhere. However, I have found that some of the information is not up to date. It is better to look into the Tor Metrics and find out the hoster for current exit relays that is mentioned there. Sometimes you are lucky. From my point of view, it should be possible to find out the age of exit relays from the Tor network database in relation to the hosters (ASxxxx) and thus find a ranking for reliability and suitability. Automatically, this would be a ranking for "privacy support". However, it would then be problematic that all newcomers would rely on these few hosters. Perhaps we will have to live with these problematic hosters and endure the dynamics. Here is a note about startup problems of the Tor service after a reboot: In my observation, this only happens with slow hardware and may also depend on the hypervisor. I use the same systems and configurations everywhere and see dead Tor services after startup only with the hoster Trabia.com and UDN (Ukrainian Data Network), with UDN working better now than a few years ago. It seems to be a timeout during start-up of the OS. With Debian "systemctl restart tor.service" solved the problem until the next reboot. With delayed start or a cron job this could be avoided, I assume. The fast hosters like * OVH.com, * Frantech.ca, * Flokinet.is, * Bahnhof.net * and Terrahost.com do not have the problem after reboot. First I will try to replace the failing VPS at Yourserver.se with reliable providers from my list, but I am checking other offers. I would also like to ask other participants in the network to name smaller, still unknown hosters. Kind regards Olaf

2 1

Tor Relay showing as down
by Alexandre Corradi Guerreiro 18 Apr '22

18 Apr '22

I have been running a ToR Relay for almost a year. https://metrics.torproject.org/rs.html#details/6C6C87A774A211F53DE5116A7A8A… and suddenly it stopped working. I don't see any errors on the logs but the relay is always showing in the relay search page as down. I even tried to upgrade the Tor client to a new version 0.4.6.10 to see if something changes, but no success. The process is running all the time, I see some circuit connections forming and after a while no more traffic going. Based on the syslog I see that everything looks fine, see next example. Apr 18 20:32:17 ubu01 Tor[1093]: Bootstrapped 10% (conn_done): Connected to a relay Apr 18 20:32:17 ubu01 Tor[1093]: Bootstrapped 14% (handshake): Handshaking with a relay Apr 18 20:32:18 ubu01 Tor[1093]: Bootstrapped 15% (handshake_done): Handshake with a relay done Apr 18 20:32:18 ubu01 Tor[1093]: Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits Apr 18 20:32:18 ubu01 Tor[1093]: Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits Apr 18 20:32:18 ubu01 Tor[1093]: Bootstrapped 95% (circuit_create): Establishing a Tor circuit Apr 18 20:32:19 ubu01 Tor[1093]: Bootstrapped 100% (done): Done Apr 18 20:32:54 ubu01 Tor[1093]: New control connection opened. Apr 18 20:37:51 ubu01 Tor[1093]: External address seen and suggested by a directory authority: 187.74.71.95 Apr 18 20:38:17 ubu01 Tor[1093]: Now checking whether IPv4 ORPort 187.74.71.95:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Apr 18 20:39:20 ubu01 Tor[1093]: Self-testing indicates your ORPort 187.74.71.95:9001 is reachable from the outside. Excellent. Publishing server descriptor. Apr 18 20:40:27 ubu01 Tor[1093]: New control connection opened. Apr 18 20:42:20 ubu01 Tor[1093]: Performing bandwidth self-test...done. I tried to test my income connection from another computer to validate that there was no block on the ISP side, I could connect successfully to port 9001 as indicated on the logs. How can I troubleshoot this problem? -- Alexandre C Guerreiro

1 0

How can I tell if standalone Snowflake is running?
by tor＠Bevitt.ws 18 Apr '22

18 Apr '22

I installed standalone Snowflake on Ubuntu per these instructions: https://community.torproject.org/relay/setup/snowflake/standalone/. Now how can I tell if it's running? Can I see the number of connections it's serviced? Will it continue after a reboot? Thanks, Chuck Bevitt Tor Project | Standalone Snowflake proxy<https://community.torproject.org/relay/setup/snowflake/standalone/> Our mission: To advance human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, supporting their unrestricted availability and use, and furthering their scientific and popular understanding. community.torproject.org

2 1

tor/munin/stem
by potlatch 15 Apr '22

15 Apr '22

Hello Tor braintrust, Is there some authoritative documentation for setting up VPS monitoring via stem and munin other than product websites? I hate to re-invent installations if I can gain knowledge elsewhere. I'm very slow working with python3. The TMS combo seems to work fine but the first error I found claims all of my relays and bridges have similar user count (as 1.67k US). They also don't self-upgrade when I modify the .conf files followed by restart. Thanks in advance for any user help, stay safe and sane, potlatch Sent with [ProtonMail](https://protonmail.com/) secure email.

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays