- tor-relays - lists.torproject.org

whonix tor-relay - help needed
by peter.zehetner＠liwest.at 25 Feb '18

25 Feb '18

Hi there! I try to configure a tor relay on an whonix-gateway but I allways receive the answer that my server has not managed to confirm that its ORPort and its DIRPort are rechable. How can I fix this? Thanks Peter

3 2

torproject.org outages? (was Re: Tor Relay Setup)
by tor 25 Feb '18

25 Feb '18

> Relay search appears to be down right now. It seems the website (https://www.torproject.org) and package repos (ex: deb.torproject.org) are currently down as well. Anyone working on it?

3 2

Not in the cached consensus
by katan＠ono.com 22 Feb '18

22 Feb '18

My LorneMalvo relay not in the cached consensus. Flags ok: running, v2dir, valid according to consensus-health. No estimate of my bandwidth never. Why? Best regards P.S.: Sorry for my english

2 4

Is it possible to run a Web server and tor ORPort on the same port?
by pikami 22 Feb '18

22 Feb '18

Hello, I was wondering if it's possible to run a Web server and tor ORPort on the same port. I'm using nginx for my web server and I'm using ports 80 and 443, it would be cool if the ORPort could also be 443, that would help people that are behind firewalls, but I can't find any solution for this on google. Is there any way to accomplish this? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

4 4

scale_active_circuits assertion fail
by Logforme 21 Feb '18

21 Feb '18

My relay (855BC2DABE24C861CD887DB9B2E950424B49FC34) just crashed with the following error: Feb 20 14:33:40.000 [err] tor_assertion_failed_(): Bug: ../src/or/circuitmux_ewma.c:711: scale_active_circuits: Assertion e->last_adjusted_tick == pol->active_circuit_pqueue_last_recalibrated failed; aborting. (on Tor 0.3.2.9 ) Feb 20 14:33:40.000 [err] Bug: Assertion e->last_adjusted_tick == pol->active_circuit_pqueue_last_recalibrated failed in scale_active_circuits at ../src/or/circuitmux_ewma.c:711. Stack trace: (on Tor 0.3.2.9 ) <snip stack trace> The relay had been up for 23 days: Feb 20 12:55:12.000 [notice] Heartbeat: Tor's uptime is 23 days 17:59 hours, with 30352 circuits open. I've sent 20574.36 GB and received 20125.28 GB. When I checked htop earlier everything looked fine. Modest CPU and MEM usage. What went wrong and what can I do to prevent this from happening again?

2 2

dns name
by TorGate 21 Feb '18

21 Feb '18

Hi onion friends :-) i have 2 relays, configured with ipv4 adresses. I have write to my isp and asked: can you change the ripe data ? isp: no my: ok :-( , i can also not change the reverse dnsname 1. So the question: is that a god way to change the config from IP-adress to dnsname in the torrc. 2. Can i also set the hostname manualy ? On Atlas is that my isp. So when there is coming a abuse, all contact is going first to my isp, and not to me. 3. Is that ok when i change the exit-html expl. with my email and business adress regards Steffen TorGate torgate(at)linux-hus.dk OpenGPG 7FD5 65EF A4EF EEF3 7A13 4372 8409 49D6 01A2 0890

2 1

gabelmoo's BW scanner, temporary or permanent leave?
by starlight.2017q4＠binnacle.cx 20 Feb '18

20 Feb '18

noticed gablemoo's BW scanner is offline and the entry for it at https://consensus-health.torproject.org/#bwauthstatus was removed; is it gone or just taking an extended break?

2 2

torservers.net DNS failure rate
by nusenu 19 Feb '18

19 Feb '18

Hi Moritz and Jens, Arthur's DNS exit scanner is detecting a high DNS failure rate on some of your tor instances: https://arthuredelstein.net/exits/ Would be great if you could look into this. thanks, nusenu -- https://mastodon.social/@nusenu twitter: @nusenu_

3 2

New Relay
by Gary 18 Feb '18

18 Feb '18

Hello. I recently set up a new relay, jaffacakemonster2, I would be grateful if someone could answer some questions for me. 1. The bandwidth on Atlas is listed as "0". Is this a wait a few days/new relay issue or a configuration issue. I was surprised to find exit relays are default now, I hope I didn't disable too much so to speak. 2. My family on Atlas - the little numbers in brackets are not all the same, I only run two relays, however on the listings it reports sometimes two sometimes three. Are you meant to include "yourself" in the torrc or only other relays?? Thanks.

5 7

PerConnBWRate, RelayBandwidthRate, BandwidthRate
by nusenu 18 Feb '18

18 Feb '18

Hello, I've got two questions regarding some bw related torrc settings. 1) after reading tor's manpage section about PerConnBWRate: > PerConnBWRate N > bytes|KBytes|MBytes|GBytes|TBytes|KBits|MBits|GBits|TBits If set, do > separate rate limiting for each connection from a non-relay. You > should never need to change this value, since a network-wide value is > published in the consensus and your relay will use that value. > (Default: 0) I was wondering what value dir auths set in consensus, but I was not able to find anything that looked like it in consensus [1]. dir-spec [2] > "perconnbwrate" and "perconnbwburst" -- if set, each relay sets > up a separate token bucket for every client OR connectio [...]> First-appeared: 0.2.2.7-alpha > Removed-in: 0.2.2.16-alpha Does that mean that dir auths stopped including it since tor 0.2.2.16-alpha should we update the manpage then? Is there a default value if consensus does not say anything about it or is there no per connection limit in that case? 2) Is there a RelayBandwidthRate torrc setting in addition to BandwidthRate so tor instances which act as clients and relays at the same time can have independent bw rates for each role (client, relay)? BandwidthRate -> affects client and relay role RelayBandwidthRate -> affects only relay role is this correct? [1] https://collector.torproject.org/recent/relay-descriptors/consensuses/2018-… [2] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1847 -- https://mastodon.social/@nusenu twitter: @nusenu_

2 1