- tor-relays - lists.torproject.org

Should Onionoo consider relays with the same ip# to be part of the same family?
by Virgil Griffith 05 Feb '16

05 Feb '16

For example, these two pairs of relays that came online yesterday: * https://atlas.torproject.org/#details/0ED2D734F295427E5A3719FA7B9985C335839… * https://atlas.torproject.org/#details/667C297D3EC6E1281D68F7F4C8C9BE8324D13… and * https://atlas.torproject.org/#details/667C297D3EC6E1281D68F7F4C8C9BE8324D13… * https://atlas.torproject.org/#details/2FF21F475C2E668C23DB7625A9D45B52591B3… (Hat-tip to Sean Saito for pointing these out.) No wrong answer---just wondering what is the community's vibe on this issue. I can go either way. -V

6 9

"Relay unresponsive (last heartbeat:...)" every hour or so?
by Deep Lodokus 03 Feb '16

03 Feb '16

Hi All! Running a TOR relay on a Raspberry Pi B+, not overclocked, over WiFi, running Raspbian. TOR is capped at RelayBandwidthRate 1000 KBytes and RelayBandwidthBurst 1500 KBytes While my /var/log/tor/log suggests that all is fine, my tor-arm logs suggest otherwise. See some copy/paste from logs below. Is something wrong with my setup? If there's indeed a loss of connectivity every hour or so, should I refrain from running this relay altogether? I haven't tried to connect the Raspberry Pi directly with a network cable, I could try that. Thanks! Snippet from /var/log/tor/log: *Jan 28 19:30:51.000 [notice] Circuit handshake stats since last time: 576/576 TAP, 1281/1281 NTor.Jan 29 01:30:51.000 [notice] Heartbeat: Tor's uptime is 1 day 12:00 hours, with 23 circuits open. I've sent 565.53 MB and received 604.21 MB.Jan 29 01:30:51.000 [notice] Average packaged cell fullness: 98.805%* Snippet from tor-arm logs: * │ 21:26:44 [ARM_NOTICE] Relay resumed │ 21:26:17 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 21:26:07 2016) │ 20:04:22 [ARM_NOTICE] Relay resumed │ 20:03:56 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 20:03:42 2016) │ 19:30:51 [NOTICE] Circuit handshake stats since last time: 639/639 TAP, 1104/1104 NTor. │ 19:30:51 [NOTICE] TLS write overhead: 3% │ 19:30:51 [NOTICE] Average packaged cell fullness: 98.954% │ 19:30:51 [NOTICE] Heartbeat: Tor's uptime is 2 days 6:00 hours, with 40 circuits open. I've sent 1.72 GB and received 1.76 GB. │ 19:18:33 [ARM_NOTICE] Relay resumed │ 19:18:12 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 19:17:57 2016) 21:26:07 2016) │ 18:21:37 [ARM_NOTICE] Relay resumed │ 18:21:15 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 18:21:00 2016) │ 17:22:44 [ARM_NOTICE] Relay resumed │ 17:22:16 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 17:22:02 2016) │ 16:14:26 [ARM_NOTICE] Relay resumed │ 16:14:10 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 16:13:55 2016) │ 15:19:40 [ARM_NOTICE] Relay resumed │ 15:19:13 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 15:19:02 2016) │ 14:04:23 [ARM_NOTICE] Relay resumed │ 14:04:01 [ARM_NOTICE] Relay unresponsive (last heartbeat: Fri Jan 29 14:03:48 2016) │ 13:30:51 [NOTICE] Circuit handshake stats since last time: 593/593 TAP, 895/895 NTor.*

2 3

tor middle node question
by Markus Koch 03 Feb '16

03 Feb '16

hi, as a good TOR support peon I got a dedicated server and set up TOR 3-4 weeks ago. Everything went great, I got my Guard, Fast and Stable etc. Flag and my little server was busy & happy. After restarting the TOR daemon I lost all my flags and even after 12 hours I only got Running and Valid back. What went wrong? My server is: https://torstatus.blutmagie.de/router_detail.php?FP=caf1eea0e8e8919dfc480a8… Markus

8 10

Nameservers fail and come back at the same time?
by SuperSluether 02 Feb '16

02 Feb '16

My exit node's consensus weight just jumped from 20 to 1750 overnight. When I checked to see how things were going, my log file is full of nameserver problems, happening every couple of minutes: Jan 31 14:12:40.000 [warn] eventdns: All nameservers have failed Jan 31 14:12:40.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up Jan 31 14:18:35.000 [warn] eventdns: All nameservers have failed Jan 31 14:18:35.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up Jan 31 14:20:53.000 [warn] eventdns: All nameservers have failed Jan 31 14:20:53.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up Jan 31 14:20:59.000 [warn] eventdns: All nameservers have failed Jan 31 14:20:59.000 [notice] eventdns: Nameserver 8.8.4.4:53 is back up But the "All nameservers have failed" and "Nameserver xxx is back up" messages happen in pairs /at the exact same time./ What's going on here, and is there a way to fix this? My VPS has 2 nameservers listed for it, should I be using those? At any rate, my exit node is still getting enough traffic to hit the bandwidth limit, so I'm assuming it's still functioning at some capacity. Here's the Atlas link if anyone wants to check out the details: https://atlas.torproject.org/#details/D632232DDC823D00ACB4F99668B58B2D5BCFF…

4 8

Keypair Error
by Alan 02 Feb '16

02 Feb '16

I updated my relay and after installing the update, I pasted my private keypair in the right file... But in ARM it keeps saying "[WARN] http status 400 ("Looks like your keypair does not match its older value.”)" How do I fix this? Alan This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.

2 1

What does this message mean in my tor logs?
by Pat Scharmer 31 Jan '16

31 Jan '16

Hi all, I’m running a server with a couple of relays and was getting good overall performance (120+ Mbps) up until a couple days ago. For the last two days, the log for one of the two relays is showing thousands of the following message: [notice] Resolved [scrubbed] which was already resolved ignoring Prior to yesterday, I hadn’t ever seen this message in my log (and the second relay on this same server/same IP is not showing any such messages). Since this started, my throughput has dropped from around 120Mbps to about 80Mbps. Looking around on the internet, I can’t find anything about this message. My server is running tor 2.7.6 on Ubuntu. The relay in question is: https://atlas.torproject.org/#details/FE67A1BA4EF1D13A617AEFB416CB9E44331B2… <https://atlas.torproject.org/#details/FE67A1BA4EF1D13A617AEFB416CB9E44331B2…> Any suggestions on what might be going would be appreciated. Thanks in advance! Regards, -Pat

3 5

(undeclared) luaktt family running modified version of tor with more logging?
by nusenu 30 Jan '16

30 Jan '16

Hi, ornetradar spotted your group of relays [1][2] presumably running [3]. Thanks for setting the ContactInfo field. Would you mind setting MyFamily as well? [1] http://article.gmane.org/gmane.network.onion-routing.ornetradar/937 [2] http://article.gmane.org/gmane.network.onion-routing.ornetradar/945 [3] https://github.com/LuaKT/Tor/commits/master

1 0

Webiron
by Nicholas Suan 30 Jan '16

30 Jan '16

Looks like Webiron is spamming again, and this time they're including a web bug in the mail to see if you've opened it: https://www.webiron.com/images/misc/91.219.236.218/abuse@1d4.us/webiron-log… https://www.webiron.com/abuse_feed/abuse@1d4.us

8 9

tor-arm bandwidth state file -xxxx seconds is missing?
by SuperSluether 29 Jan '16

29 Jan '16

Found this error when checking my relay today: ARM_NOTICE Read the last day of bandwidth history from the state file (-xxxx seconds is missing) Every time I start arm, the -xxx seconds missing is different. The bandwidth graph is also stuck, but real-time data is still shown. Is this a problem with Tor, or with Arm? Anyone know a fix?

5 7

Relay ssh control/monitor ? Config is secure ?
by Pierre L. 28 Jan '16

28 Jan '16

Hi all, Some noob questions about controlling/monitoring my Tor relay on a Linux box... hosted in an ISP datacenter, so WAN IP and ports are showed to the www. I got SSH access. I've found tor-arm console UI, useful to show real-time bandwidth used, and other stuff. 1. If possible, I need to know if my current config is secure and useful, torrc contains ControlPort 9051 HashedControlPassword xxxxxxxxxxx CookieAuthentication 0 2. On some websites, I see screenshots with something like this on control config : /var/run/tor/control May be it's more secure on an online server ? No need to have another listening port like 9051 Sry I haven't found any information about this config... and how to make it possible... Thx for your help !

4 5