- tor-relays - lists.torproject.org

No exit at home !!!
by for this post anon 03 Mar '18

03 Mar '18

Roger say it right: No exit relay at home! I write this mail in anon because I had bad experience with that. I had the experience to get visitors early in the morning from the police department some months ago. After that I must by new computers... Use ISP's only for exits. Or you want "fun". xyz

3 2

Port not rechable
by peter.zehetner＠liwest.at 02 Mar '18

02 Mar '18

Hi, I'm still trying to run a tor delay. Here's the error: Your server (81.10.248.112:80) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. But canyouseeme.org said: Your ISP is not blocking port 80 Whats's wrong? Thanks Peter

6 6

Port not rechable
by peter.zehetner＠liwest.at 02 Mar '18

02 Mar '18

OK, now I've set PortForwarding in Tor-Arm from "False" to "True", then restarted Tor: ...has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check... I'm going to run a non-exit-relay and I'm going to do this at home. Peter Am 02.03.2018 um 20:42 schrieb Matthew Finkel: > On Fri, Mar 02, 2018 at 08:27:29PM +0100, peter.zehetner(a)liwest.at wrote: >> Hi, I'm still trying to run a tor delay. Here's the error: >> > > Thank you for running a relay. > >> Your server (81.10.248.112:80) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. > > I do not see port 80 open, either: > > $ torsocks nc -v 81.10.248.112 80 > Ncat: Version 7.40 ( https://nmap.org/ncat ) > Ncat: Connection timed out. > >> >> But canyouseeme.org said: Your ISP is not blocking port 80 > > Maybe "not blocking" does not mean "is open". > > Are you running this relay at your home? If yes, then that is not > recommended, but you may need to allow port 80 on your firewall/router. > You may need to use port forwarding or add your computer into the DMZ > (if your router supports this). > > If you're not running this relay from home, is the server directly > connected to the Internet or is there a router/switch/blackbox in the > middle? > >> >> Whats's wrong? >> >> Thanks >> >> Peter > >> _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Port not rechable
by peter.zehetner＠liwest.at 02 Mar '18

02 Mar '18

There is no firewall installed. Peter Have you double-checked your firewall? -Cody On 03/02/2018 11:27 AM, peter.zehetner(a)liwest.at mailto:peter.zehetner@liwest.at wrote: > > Hi, I'm still trying to run a tor delay. Here's the error: > > Your server (81.10.248.112:80) has not managed to confirm that its DirPort is reachable. Relays do not publish descriptors until their ORPort and DirPort are reachable. > > But canyouseeme.org said: Your ISP is not blocking port 80 > > Whats's wrong? > > Thanks > > Peter > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org mailto:tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org mailto:tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

2 1

Upcoming security releases for Tor 0.2.9 and up.
by Nick Mathewson 01 Mar '18

01 Mar '18

Hi! This coming week, we'll be putting out new stable releases for 0.2.9 and later supported branches to fix a few security bugs. The highest-severity bug to be fixed is severity "medium". (See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/Securit… for information about how we rank security issues.) These releases will also backport the anti-DoS features from Tor 0.3.3. Relays and authorities should be sure to upgrade once packages are available; these issues are not high-priority for clients. best wishes, -- Nick

4 5

Unmeasured Flag
by Matthew Glennon 28 Feb '18

28 Feb '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 So if I'm understanding this correctly, we're still having problems with a bw testing nodes and that is why my relay has the unmetered flag? -----BEGIN PGP SIGNATURE----- Version: Keybase OpenPGP v2.0.76 Comment: https://keybase.io/crypto wsBcBAABCgAGBQJalsdlAAoJEHIAmlM/NGGbpQcH/16WQLlMAAVzx4blIRV2bIJF Hwdyj4FFQ+Ms0hHhj1DwMkB6EMa11kogLA8k+NGim8QeF2Qyobd1lARUXjZdfbV5 s/L6JYYCO+PsJxJY2+nOU41HUps1w5zLfFy+ekxkVwsX8dXq+SVy06+1HXfjY2uT HJnIpkx9/IZWMjJzRv33ylIMDq4u0MltJr+4MRrb5rSn6+9pz9m4z6CeUKJbsiLh nE0YRblkRwfrlVCP3VTaaRyQdMUwWzKwnB9S8dtKGDKb+tYz4QduFuzBf1eGGrO7 cp9GeHiittyBSGylRWveQgbkzwXRGPuUGtabXutQRqGXDvanDtEroHg+hUP0SEw= =b7/2 -----END PGP SIGNATURE-----

3 3

Re: [tor-relays] less than 3 bw auths available: self-measurement (with 10k cap in effect)
by Stian Fauskanger 27 Feb '18

27 Feb '18

if your relays behave strangely in terms of bandwidth seen, than this might be due to the fact that there are less than 3 bw auth votes available. If you run a fast relay it is capped to 10k cw. This affects currently the 857 fastest relays. It also affects "low-consensus" relays. I have a bw=5k relay which almost doubled the amount of traffic, increasing steadily from 14.30 UTC until 19.00 UTC [a.k.a. now]. I assume this is because 5k is a much higher percentage of the total bw now compared to when fast nodes was not capped at 10k and at the same time, 5k didn't "give" me enough traffic to meet RelayBandwidthRate. ~ Stian

1 0

IPv6 for the nifty?
by nusenu 26 Feb '18

26 Feb '18

Hi Markus, since you are by far the biggest exit relay operator I was wondering if you have any plans to get IPv6 connectivity? thanks, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

3 3

Tor Relay Setup
by Gabe D. 26 Feb '18

26 Feb '18

Hey Guys, Ive an issue... I wanted to aid the network and setup a tor exit node, however its failing to do so, everything looks perfect config wise and it says "publishing server descriptor" no errors but the node never shows up in tor atlas, is there something i may be doing wrong? This is my config: ORPort 9001 ExitRelay 1 Nickname ** ContactInfo ** DirPort 80 DisableDebuggerAttachment 0 ControlPort 9051 CookieAuthentication 1

6 9

Relay failed logins
by Olaf Grimm 25 Feb '18

25 Feb '18

Dear guys, I am now on my server with SSH and get the message during login: ... Last failed login: Sat Feb 24 14:22:47 EST 2018 from 5.188.10.179 on ssh:notty There were 1343 failed login attempts since the last successful login. ... This simple relay (no exit) is online since less days. Location Moldavia / Trabia Network; VPS Is this amount of attacks regular? In the past i had a log file of 12MB on an other server - all failed logins. It is not a problem. It is only for my feeling "Ok, That's right!". Nickname node49c Olaf

6 5