- tor-relays - lists.torproject.org

0.3.2.9 not reporting bandwidth in atlas
by Paul Templeton 01 Feb '18

01 Feb '18

Is it me or is there some issue. Since I've upgraded to version 0.3.2.9 there has been no update to the bandwidth graphs. family:867B95CACD64653FEEC4D2CEFC5C49B4620307A7 Paul 609662E824251C283164243846C035C803940378

3 2

MyFamily and ContactInfo fields are required for operators running multiple tor instances
by nusenu 01 Feb '18

01 Feb '18

Hi, I'd like to highlight that today the following two sentences requiring ContactInfo and MyFamily for operators running multiple relays got added to the tor manual page [1]: > ContactInfo **must** be set to a working address if you run more than one > relay or bridge. (Really, everybody running a relay or bridge should set > it.) > > > MyFamily **must** be set correctly if you run more than one relay or > bridge. (That is, every relay should list all the others as described > above.) The main motivation for this change have been suspicious tor relays that bad-relays@ ML decided to remove but had no way direct way to contact and so was forced to make hard decisions. With these clear statements bad-relays@ ML group can handle problematic cases better. regards, nusenu [1] https://gitweb.torproject.org/tor.git/tree/doc/tor.1.txt#n1717 -- https://mastodon.social/@nusenu twitter: @nusenu_

6 8

Tor uses up all available memory and eventually quits
by georgemaschke＠posteo.de 31 Jan '18

31 Jan '18

I am running a Tor (0.2.5.16 on Debian Linux) relay on a VPS with one gigabyte of RAM and no swap partition or swap file. The hosting company states that it doesn't support swap in order to prolong the life of its solid state drives. Tor gradually uses up more and more memory until its percentage usage is in the high 90s. Then Tor quits. This happens within about 48 hours of launch. What can I do to resolve this problem? Thanks! George W. Maschke https://georgemaschke.net

6 7

#2667 [Core Tor/Tor]: Exits should block reentry into the tor network
by nusenu 31 Jan '18

31 Jan '18

> Comment (by arma): > > I continue to think that teaching exit relays to avoid allowing exit > connections to known relays (IP:ORPort) is a good and useful step. > > We keep running across messy situations where letting somebody connect to > a relay from an exit relay's IP address turns into a security surprise. Does that mean that exits will no longer be able to run tor clients (ie. to run apt updates via tor)? -- https://mastodon.social/@nusenu twitter: @nusenu_

2 2

Attack or issue? 4 / 11 M of traffic
by Stijn Jonker 31 Jan '18

31 Jan '18

Hi All, Since around midnight CET, my relay who was happily running almost the same amount of traffic in and outbound, has dropped to 4 Meg in, 11 Meg out according to SNMP on the host. (Cap: 10M/peak 12.5M). Lots of messages like: - Channel padding timeout scheduled 304317ms in the past. - Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [45685 similar message(s) suppressed in last 60 seconds] Any suggestions what to check / verify for this? 328E54981C6DDD7D89B89E418724A4A7881E3192 Thx, Stijn

2 1

How to post to this list
by grarpamp 30 Jan '18

30 Jan '18

1) DO NOT Top Post, backwards it's because that's, reply below what you're replying to. 2) DO NOT Bulk Quote, trim what you're replying to down to the minimum size needed to convey the relavant context. 3) DO NOT Block Reply, piecewise interleave your replies below each piece of context to which you are replying. 4) DO NOT send HTML, set you rmailer to compose and send plain text emails. Far too many breaking basic "email netiquette" lately. Learn more by searching that quote.

4 5

tor on arm vps
by Quintin 29 Jan '18

29 Jan '18

I see online.net has a lot of ARM VPSes. Does tor run fine on these? Q -- 0101100101000001010010000101011101000101010010000010000001000010 0100110001000101010100110101001100100000010110010100111101010101

3 11

A lot of Warn messages when bootstrapping Tor 0.3.2.9 (stable)
by Dark Matter 29 Jan '18

29 Jan '18

Hello, I'm running a tor-relay with Tor version 0.3.2.9 (stable). I had to do some daemon restarts, because of connection limit issues. Since the last two restarts the Tor process issues a lot of warnings while bootstrapping, because it could not create a (client) circuit. Relay functionality is working without problems. Before these restarts I had no problems connecting to the tor network and creating circuits. Tor usually booted within less than a minute without warnings. I found a ticket describing the same problem (although for a different Tor version) here: https://trac.torproject.org/projects/tor/ticket/24639. Are there any known workarounds yet? For more detail, I'll post the last warning messages: Jan 25 18:31:54.000 [warn] Problem bootstrapping. Stuck at 90%: Establishing a Tor circuit. (Connection timed out; TIMEOUT; count 1503; recommendation warn; host B7047FBDE9C53C39011CA84E5CB2A8E3543066D0 at 199.249.223.60:443) Jan 25 18:31:54.000 [warn] 1503 connections have failed: Jan 25 18:31:54.000 [warn] 1026 connections died in state connect()ing with SSL state (No SSL object) Jan 25 18:31:54.000 [warn] 392 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE Jan 25 18:31:54.000 [warn] 84 connections died in state handshaking (Tor, v3 handshake) with SSL state SSL negotiation finished successfully in OPEN Jan 25 18:31:54.000 [warn] 1 connections died in state handshaking (TLS) with SSL state unknown state in HANDSHAKE Tor had to try to open a circuit for more than half an hour before finally succeeding... Regards, Dark

3 2

The Onion Box: Connections
by Ralph Wetzel 29 Jan '18

29 Jan '18

3 2

Upgraded relay non show in ATLAS
by MLTor Node 27 Jan '18

27 Jan '18

6 11