- tor-relays - lists.torproject.org

Arm thinks Tor is not running as a Daemon?
by Jannis Wiese 26 Nov '15

26 Nov '15

Hi, I’m a bit confused right now. I’ve upgraded my relay to Debian Jessie yesterday and since then, arm keeps telling me > [ARM_WARN] The torrc differs from what tor's using. You can issue a > sighup to reload the torrc values by pressing x. > - configuration value is missing from the torrc: RunAsDaemon I’m running the same configuration as before (running Debian Wheezy), where it worked without any warning. RunAsDaemon is set to 1 in tor-service-defaults-torrc, still arm is showing me on the Tor configuration page “RunAsDaemon False”. Putting RunAsDaemon into torrc as well triggers this: > [ARM_WARN] The torrc differs from what tor's using. You can issue a > sighup to reload the torrc values by pressing x. > - torrc value differs on line: 17 The problem here: There is no line 17 in my torrc… I’ve already read tickets like #16459[1] and #2501[2] but it didn’t help much. Damian says in Ticket #16459 > […] This message is meant to help people who edit their torrc, forget to restart tor, and are then confused why the settings didn't take effect. [...] I did restart tor (a couple times) and apparently it is running as a Daemon (service --status-all). So I hope this is “just” an issue with arm… Maybe someone of you has an idea? I’m running arm 1.4.5.0 and tor 0.2.7.5 (from deb.torproject.org <http://deb.torproject.org/>) Cheers, Jannis [1] https://trac.torproject.org/projects/tor/ticket/16459 [2] https://trac.torproject.org/projects/tor/ticket/2501

2 2

Re: [tor-relays] Faravahar messing with my IP address
by SiNA Rabbani 26 Nov '15

26 Nov '15

Dear Relay Operator, I am the operator of Faravahar, It has been having some network issues, specifically very long latency. But this is the first time I hear of an issue like this. 154.35.32.5 is Faravahr's older IP addresses which was replaced with and 154.35.175.225 is the new IP (current). There are iptable rules forwarding the traffic from OLD IP to the new one for the clients that have not updated yet. Are you running the latest version of tor software? I'll be sure to keep an eye on this email and open a ticket as needed. Thank you for reporting the issue and running a relay. All the best, Sina "Be the change that you wish to see in the world." - Mahatma Gandhi ----- On Oct 22, 2015, at 11:22 AM, Logforme m7527(a)abc.se wrote: > I run the relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34) > > Saw this in yesterday's log file: > Oct 22 03:17:55.000 [notice] Our IP Address has changed from > 84.219.173.60 to 154.35.32.5; rebuilding descriptor (source: > 154.35.175.225). > Oct 22 03:17:55.000 [notice] Self-testing indicates your ORPort is > reachable from the outside. Excellent. Publishing server descriptor. > Oct 22 03:17:56.000 [notice] Performing bandwidth self-test...done. > Oct 22 03:26:55.000 [notice] Our IP Address has changed from 154.35.32.5 > to 84.219.173.60; rebuilding descriptor (source: 194.109.206.212). > > 84.219.173.60: <- My real IP address > 154.35.32.5: faravahar.rabbani.jp <- No idea > 154.35.175.225: faravahar.redteam.net <- Authority server > 194.109.206.212: tor.dizum.com <- Better authority server > > So if I read it right my relay asked the authority server Faravahar what > my IP address is and got the wrong answer. 9 minutes later my relay > asked another authority server and got the right answer. My relay show > an uptime starting from this time and if the relay did a full restart it > meant all the circuits got dropped? Inconvenient for users. > > My relay have "restarted" like this a few times the last weeks (only Tor > daemon "restarting", not the machine). Don't know if Faravahar is behind > the other "restarts". This time I just caught it in the log file before > it got archived. > > Is this a know issue with Faravahar? If so, should it be fixed? > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

7 12

Nagios/Icinga plugin check_tor_bandwidth for gathering bandwidth data
by Josef Stautner 26 Nov '15

26 Nov '15

Hello @all, (I'm not sure if you guys are interested in a topic like this) I wrote a perl script to gather bandwidth data from my Tor exit relay. The script connects to the Tor control socket, fetches the running config to extract the bandwidth limits and the reject rule count. Afterwards the last 60 bw-cache entries are fetched and average values are built for bandwidth in and out. All this performance data is then forwarded to Nagios/Icinga where you can do anything with that values. Every 30 minutes a cronjob renders the graph showing the datapoints of the last 6 houres and uploads the resulting image to my website. You can find the image here (Hint: The values for in and out are stacked): https://blog.veloc1ty.de/bandwidth-large.png The source of the script can be found here on GitHub: https://github.com/vlcty/check_tor_bandwidth It's released under the GPLv3 Maybe somebody will find it usefull :-) ~Josef

4 4

(no subject)
by 海洋 23 Nov '15

23 Nov '15

1 0

keypair issue after backing up relay
by Matlink 23 Nov '15

23 Nov '15

Hi, I'm running a tor relay. I once had some trouble about running it, and I decided to reinstall tor via apt-get. Of course, it did erased all my private and public keys, that I missed to backup before reinstalling tor. Then I ran tor again, with the new identity. As I have a container backup running every day, I was able to recover the erased private and public keys, that I put them back. I can run tor with my original identity, but the directory server is saying me '[WARN] http status 400 ("Looks like your keypair does not match its older value.")'. How can I fix it ? I would like to keep the original identity, since I had all the convenient flags and don't want to wait another couple of weeks to get them back with a new identity. Sincerly, -- Matlink - Sysadmin matlink.fr Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/ XMPP/Jabber : matlink(a)matlink.fr Clé publique PGP : 0x186BB3CA Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2

2 2

warning in my relay log
by DARKNET.IT 23 Nov '15

23 Nov '15

I have changed server and tor version (from Tor 0.2.6.10 to Tor 0.2.7.5). My relay works but I have this warning: "http status 400 ("Looks like your keypair does not match its older value.") response from dirserver '208.83.223.34:443'. Please correct." This is my relay fingerprint: 59573AB90614D929360C7D9BCBF3313497A22AA2 What means and what I have to do? The keys for me is correct. Thanks for reply

3 2

Actions required after update?
by kingqueen 23 Nov '15

23 Nov '15

Hi That's a hefty changelog for the new stable release of Tor. I'm in awe of and grateful to the developers, as it's all well beyond me. Please could anybody confirm, is there any action required for somebody running the relay on a pretty bog-standard Ubuntu 12.04 Linux dedi, other than sudo apt-get update && sudo apt-get dist-upgrade ? Thank you!

3 3

IP-Echelon complains about claimed infringement
by Riccardo Mori 22 Nov '15

22 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, It's almost a week that I am receiving dozens of "Notices of Claimed Infringement" a day from IP-Echelon, all equals, saying that they "are contacting" me "on behalf of Paramount Pictures Corporation (Paramount)" and asking me to remove the film in question that is being shared via bittorent (the port varies each time). The first time I wrote them that the ip address in question is a Tor exit node, I explained briefly what is Tor and that I can't do anything to help them. I also wrote to MyLoc (the ISP) saying pretty much the same. I wrote to IP-Echelon another time but they never replied. Usually I wouldn't care about them but this time MyLoc told me to "fix the problem or" they "will block" my "server". I modified the exit policy so now I am running the reduced one[1] That (in theory) should fix the problem but I would like to avoid the reduced policy. Is there anyone that had the same issues with IP-Echelon and can help me? Usually how do you handle those annoying auto generated reports? Thanks, patacca [1] https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWT+YZAAoJEE1LNuolWAxgl90P/Rq5DCCc4FrrFqqOSKjisJ57 zBVOpzrfDxAG0ArRFWdhUBi8etpvbNtq042mjevVGp3N3p+IPpyl9bKvZWM7ACID BtBnra7WwMEW21BHqKGmzXJ6CG35AdVRUaJMaJXXSaNGNThFh+mXDGm4B8iHUoI3 3vZxiIHG17INY7lZM7RimYA1MKRQAcICldIYaCA2Nwt/n4gbUlZ3OUXmeGbJins/ NZrN98ZOhxeNg93+wk3f5ns1mQk137ZIcsdb+86uyaqDCxGn7fja2/MXBeHBUonM cZcBUSw1SKdY3XbYh6VyHRhRxWfmHeB/e2MLlDiOZbVc5QgGsOkmwmPKFuNA1dvg w5QoXcUSpUh01mxEK0x1IRl5BAD1zya4ZyITxLAr7OXGVx1jifCvkCKq6rDrLzsX XP8hq8w6Hp9GuFr8QrOx08Q6kvAvQjcF59s6/h0P3ehdbLnNaquEgQA86+WDtlNU lON0MnCf5vmZbww0TP5ymhiiZZIy6uilaqfVJry9lXdiXJvu/xeWs1p2VkxlUpaD ySnjFArg8iT5+veZro1ui0tmqseyu2BdEPfAyu86FcrS3wpbvI983aPDZOEpDoJh NaiE5pQCtsxj7moL1pDfHfFfS23aTGerpj9VTXYE9vd/hO8gqZTWCFA7coDZcXQV 0ZdIkA2C4EI7Rd6ui/cS =CxVx -----END PGP SIGNATURE-----

5 4

Tor Weather not working?
by Green Dream 21 Nov '15

21 Nov '15

I took a relay offline 2 days ago and still haven't received a notification from Tor Weather. The preferences page confirms everything is configured, but yet, it doesn't seem to be working for me. I checked the spam folder. Is there someplace to file tickets for this, or some other contact info for the maintainers of this service? I'd be happy to share additional details if someone wants to look into it.

12 15

IP-Echelon complains about claimed infringement
by Riccardo Mori 20 Nov '15

20 Nov '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, It's almost a week that I am receiving dozens of "Notices of Claimed Infringement" a day from IP-Echelon, all equals, saying that they "are contacting" me "on behalf of Paramount Pictures Corporation (Paramount)" and asking me to remove the film in question that is being shared via bittorent (the port varies each time). The first time I wrote them that the ip address in question is a Tor exit node, I explained briefly what is Tor and that I can't do anything to help them. I also wrote to MyLoc (the ISP) saying pretty much the same. I wrote to IP-Echelon another time but they never replied. Usually I wouldn't care about them but this time MyLoc told me to "fix the problem or" they "will block" my "server". I modified the exit policy so now I am running the reduced one[1] That (in theory) should fix the problem but I would like to avoid the reduced policy. Is there anyone that had the same issues with IP-Echelon and can help me? Usually how do you handle those annoying auto generated reports? Thanks, patacca [1] https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWT+YYAAoJEE1LNuolWAxg07MP/2ssZc9jiotv3+xReoTFs26j lOqTuEJ8dEAhmGig2hMkHwq+VZUhaDOB8OLPkFwUwFJ76PrvTz5j5p9LTYXwdFbE /2t8eeXTabITtQo0aO/t84g8UNRAmv4ZTWua9Z7DtzhLcrspvftTu3eL5rqbQ4v8 yxI55t8rHXH+sQG2K/io+OpRKjJLcMYexJl8PZOFld/AlkVvabwAtjJi5lhQfcmd V7dlckK1oQTWFGdyw9ww0Bsz1P7sjBLabUXuvP5gxdNyb3LB3uQVxL+29j5G+JBX W0JTJS25g52Mc2ggUiWnzUxdEuKf1pxHAy8Lb6CNG16ZGqZFBu/mdzt9yj72uzng ZUp5eanHVVJIzzkF7AviivkPI0RMUoK2FmwWa7/RrY3p97RrNRB+ytq2ky7IenKR cLx7WXPaG90lSYkHjTFpHZ4kRBVCX4Pd2xmQ8V1DOXMNiyTaabEWE58zVBnPrCQ4 QU+vUduWDkw0Lc8n3KZ0YDZfclhgCLn0qFageCmHRg8tlUgsHTySw6HFIDkYS+X3 6HZkkrOWsfjDAS9+6ZPe+/wzG7xIU9t/ObaxZIHPVydlDF8JlS4wdWHbLZYp608t DCk/l954+uVaQmQCBcah+tZr1Z+lxTJhCAh27QT/s/8WM+tYy9wHAmBLtlWACdFB i74TrbaBXGcX5/rplwjO =YDRS -----END PGP SIGNATURE-----

1 0