Re: [tor-relays] Bridge Distribution Mechanism none
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] Instabilities in Hydra family expected
Hello, Regarding Yourserver.se: I too recently began running an exit there.[1] I receive multiple abuse complaints a week, they simply forward them and close the ticket without needing a response. I have been a customer of Yourserver.se for many years, back when Sweden was the only option for a location, back when they were only providing OpenVZ and not KVM, back when they would limit servers running Tor relays to 5Mbps (which they no longer seem to bother with). I ran a middle relay back then, and I remember having discussions with them about Tor - they didn't really understand the principle of an exit relay, so I chose to just stick with a middle relay to be safer. Now having come back to relay operation I decided I would give an exit a go there - there are several others across their two ASNs[2][3] (majority Hydra) and having been a customer and having extensive contact with their team over the years I figured I am likely to have more of an understanding with them. The exit did get suspended a few weeks back for "malware", and I opened a ticket explaining Tor and how I am not responsible for whatever they mean "malware" to be. They unsuspended it with the response: > The VPS was blocked for malware. > We don't accept this malware. > We unspended Your VPS. I took that to mean that the "malware" being distributed over Tor is irrelevant to them. Everything has been fine since, until today (ironically) when it got suspended for "spam". They responded with: > We allow TOR, but don't allow spam. > We unsuspend Your VPS. > We receive very much spam abuse about Your VPS. > Please, check Your VPS. I think they continue to misunderstand the purpose of Tor or would prefer people to somehow run exits without any issues whatsoever. I do run my exit with an almost completely open exit policy (except for mail ports and ports they block[4]), so I plan to now set it to reduced and see if that helps them be ok with it. I notice the Hydra relays are already on a substantially reduced policy (beyond even the reduced-reduced policy), so perhaps this will make no difference in my case either and I will end up also needing to move them elsewhere. I am happy to endure with Yourserver.se though, I do not want my years of being a happy customer to be ended because they don't understand Tor well enough. With regards alternative hosts, I recently discovered rdp.sh[5], who operate under a new ASN.[6] They are happy with Tor exits if you comply with their policy[7] (let them know first and block mail ports), and they provide unmetered 5 Gbps connection in the Netherlands.[8] They also run some reduced exits and middle relays themselves, and the operators of the bauruine family also began running exits a few days before me. It's worth noting however that they don't provide IPv6 right now, and won't set reverse DNS PTR records on request (I tried). They could prove to be a good replacement for Yourserver.se if you need one. Cheers, Spydar007 [1] https://metrics.torproject.org/rs.html#details/CC8732E6E34D8C1AA61A3B7FE95DDD71BCE9C880 [2] https://metrics.torproject.org/rs.html#search/as:AS43513%20flag:exit [3] https://metrics.torproject.org/rs.html#search/as:AS52173%20flag:exit [4] https://www.yourserver.se/knowledgebase/35/Blocked-ports.html [5] https://rdp.sh [6] https://metrics.torproject.org/rs.html#search/as:AS210558 [7] https://rdp.sh/docs/faq/tor [8] https://rdp.sh/docs/faq/traffic-limit ___ 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
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] Tor Relay showing as down
I have been running a ToR Relay for almost a year. https://metrics.torproject.org/rs.html#details/6C6C87A774A211F53DE5116A7A8A9C447103A08B 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 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
