- tor-relays - lists.torproject.org

What is the command to view the tor log file on Debian?
by Keifer Bly 08 Aug '20

08 Aug '20

6 8

Availables ports for obfs4 on Fedora
by I.N.R.I. 07 Aug '20

07 Aug '20

Hi To install Tor I try to set a port for obfs4 The ports 22, 80 and 443 are used I wish to find a free port conpatible with the TCP 127.0.0.1 Or an other adress May you help me pls ? Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email.

1 0

Re: [tor-relays] Tor is showing it's running different versions, and continuing previous thread
by Keifer Bly 07 Aug '20

07 Aug '20

That returns "reading config failed" so no luck. Thanks anyway though! --Keifer On Fri, Aug 7, 2020 at 12:43 PM <tschador(a)posteo.de> wrote: > On 07.08.20 20:47, Keifer Bly wrote: > > > Hi all, > > > > So my relay at > > > > > https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36… > > > > Says it is running two different versions, on metrics it is showing it is > > running tor 0.4.3.5 but when I log into the VPS via SSH it says it is > > running tor 0.4.3.6. It has been like this for a few days now. Something > > is also not allowing me to check tors data logs, when I check my torrc it > > says the log file is /var/log/tor/notices.log, it either just loads a > blank > > file or says the file is unwrite able. This is odd I don’t believe I did > > add any special configuration for this. > > Hi Keifer, > > on Debian you can check: tor -v; dpkg -l|grep "ii ?tor" > For me it shows: > Tor 0.4.3.6 running on Linux > ii tor 0.4.3.6-1~d10.buster+1 > ii tor-geoipdb 0.4.3.6-1~d10.buster+1 > > Next - check: ls -lA /var/log/tor > An my server it shows: > -rw-r----- 1 debian-tor adm 0 Jul 13 21:03 log > > The owner should be "debian-tor" or whatever your tor is running. > use: chown to change file owner and group > and: chmod to change file mod bits > > Good luck! >

1 0

Tor is showing it's running different versions, and continuing previous thread
by Keifer Bly 07 Aug '20

07 Aug '20

Hi all, So my relay at https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36… Says it is running two different versions, on metrics it is showing it is running tor 0.4.3.5 but when I log into the VPS via SSH it says it is running tor 0.4.3.6. It has been like this for a few days now. Something is also not allowing me to check tors data logs, when I check my torrc it says the log file is /var/log/tor/notices.log, it either just loads a blank file or says the file is unwrite able. This is odd I don’t believe I did add any special configuration for this. Heads up, on my end the spam emails are coming through again. Cheers. Thanks very much. --Keifer

1 0

The “tor-relay” Well-Known Resource Identifier - IANA registration
by nusenu 07 Aug '20

07 Aug '20

Hi, as already sent to the tor-dev mailing list a week ago I planning to submit a well-known URI registration ( https://tools.ietf.org/html/rfc8615 ) so the verifyurl is at a static place and no longer needs to be specified explicitly. Please let me know if you have any comments. https://nusenu.github.io/tor-relay-well-known-uri-spec/ kind regards, nusenu -- https://mastodon.social/@nusenu

2 1

West Coast US Tor Relays Slow - Low Consensus Weight versus East Coast
by Neel Chauhan 06 Aug '20

06 Aug '20

Hi network-health@/tor-relays@ mailing lists, I noticed one thing: Tor relays on the West Coast US (and Canada) are generally slower than those on say the East Coast and in Europe. I moved to the West Coast this January, but this was not an issue in the past when looking at dedicated servers I had from the West Coast prior to this year. These are two middle relay instances on an Gigabit FTTH connection (Wave G in Redmond, WA): https://metrics.torproject.org/rs.html#details/B0F9BA27944FA59E3B1A182208FF… https://metrics.torproject.org/rs.html#details/DB710B14D7329B7289CFCC547F48… The Consensus Weight often is slower than the Advertised Bandwidth, and isn't ramping up despite having lots of bandwidth. I set RelayBandwidthRate to about 500 Mbps on each instance. This isn't just a Wave G problem, this affects almost every relay in the West Coast including other Gigabit ISPs such as AT&T (AS7018) and Sonic (AS46375), as well as hosting companies and colocation facilities. For instance, my Los Angeles-based Exit relays at Psychz Networks (AS40676) show this issue (however they are new): https://metrics.torproject.org/rs.html#details/156AAC3FAD1ACC8906316519DCB4… https://metrics.torproject.org/rs.html#details/A69CEB30328B1E85C6B167FECAF2… Even Emerald Onion has this issue: https://metrics.torproject.org/rs.html#details/09DCA3360179C6C8A5A20DDDE1C5… What is causing this issue and is there a solution? Is it backbone congestion due to COVID-19? The high load on dirauths? sbws regressions? Can I help fix this issue? I am a Core Tor contributor and am open to also working on sbws. Is there a way to optimize my relays (they run FreeBSD). -Neel === https://www.neelc.org/

2 1

FreeBSD Relays in VMware VSphere
by MacLemon 06 Aug '20

06 Aug '20

Hi! We've been having serious networking problems with a FreeBSD VM in VMware VSphere for several months now. The symptom is that network throughput slowly degrades and packet loss increases until your VM is unable to transmit any meaningful data. (Cannot SSH in anymore, etc. We're talking literally BITS per second bad.) We've been suspecting the vmx(8) networking driver for some time and now there's an update to the driver available in FreeBSD 12.1-p8. So if you're running a Relay on FreeBSD under VSphere, this should fix the issue. https://bsdsec.net/articles/freebsd-announce-freebsd-errata-notice-freebsd-… We hope that our two-in-one FreeBSD relay will be stable and passing traffic again! C3WLittleGem https://metrics.torproject.org/rs.html#details/B1F09810C4F7B9D30F483DCE3891… C3WPhantomStreak https://metrics.torproject.org/rs.html#details/C04850673F655A91F5AD3C06E1E5… C3W Family Members: https://metrics.torproject.org/rs.html#search/family:C04850673F655A91F5AD3C… Best regards MacLemon for the Chaos Computer Club Vienna/Austria

1 0

Exit relay: ERROR -- No Descriptor Available
by raspitor 05 Aug '20

05 Aug '20

After running an exit relay for a few days I see the message: ERROR -- No Descriptor Available on the torstatus.rueckgr.at site, and the traffic of my exit node is almost zero, also seen in nyx. Rebooting the system restarts everything normal and it is listed on the ruckgraet site, but after a day or so the problem occurs again. What might ne the cause of this?

2 1

Should I use Tor Alpha on my relays
by Sebastian Elisa Pfeifer 01 Aug '20

01 Aug '20

Hello, I am currently running Tor from the Tor Repositories on Debian Stable. Its working ok, but I was wondering if the network would benefit if I would start using Tor Alpha? Greetings, Sebastian

3 3

Recently very low Consensus Weight
by tor_this_too＠aol.com 01 Aug '20

01 Aug '20

Hi everyone, this is my first ever post on a mailinglist, so bare with me if I'm doing it wrong... I've been running a relay for some time now and recently the traffic dropped neraly completely https://metrics.torproject.org/rs.html#details/564A7F1D0314125AF60096CDE0A8… Consensus Weight is down to 71 and I wonder why this is the case? The relay was recently rebooted (just in case) and all other traffic I may initiate from this server is without a problem and at max speed. Any ideas?

1 0