[tor-relays] Help keeping Tor relay up
I've managed to get my relay running long enough to run the bandwidth check and have it succeed. I'll check Atlus and it'll say my relay's up and running. However when I check again about an hour later, it's saying that Running: false. I've set up the relay recently, so I'm not expecting a lot of traffic. However, I'm confused as to if my relay is suddenly failing for no reason or is Atlus saying my relay is no longer running because there's no traffic on it. Any help would be appreciated. Thanks. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Debian relay Puppet module
On Wed, Jun 18, 2014 at 9:34 PM, Zack Weinberg za...@cmu.edu wrote: If the process listening on port 80 is the Tor process, then any vulnerability in the HTTP service it presents to port 80 can be exploited for a direct attack on the relay itself. If port 80 service is provided by a separate program (e.g. lighttpd) running under a different user ID, then an exploit of *that* program may not be able to affect the relay. That's all I meant. (The Wikipedia article is talking about a related thing, but not really the same.) Yes, clear now, thanks for the explanation. -- http://about.me/alexanderfortin ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] CLI tool like Atlast
Does tor-prompt provide any more info than arm? -K_ On Wednesday, June 18, 2014 11:56 PM, Damian Johnson ata...@torproject.org wrote: Hmm.. what am I doing wrong here: sudo apt-get install python-stem Reading package lists... Done Building dependency tree Reading state information... Done python-stem is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. tor@KaliTorLinLon:~$ tor-prompt tor-prompt: command not found Stem 1.2.2 was released just a couple weeks ago, so it's too bleeding edge for the Debian repos. Try the following instead... % sudo pip install stem ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help keeping Tor relay up
On Wed, Jun 18, 2014 at 10:11 PM, Evelyne Fong darkbahamu...@hotmail.com wrote: I've set up the relay recently, so I'm not expecting a lot of traffic. However, I'm confused as to if my relay is suddenly failing for no reason or is Atlus saying my relay is no longer running because there's no traffic on it. Do you have hibernation set up? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] CLI tool like Atlast
Hi, onion.py is in the bin/ folder. If you run sudo python setup.py install, it will be installed globally, or you can run it directly from the source folder, as it says in the readme - |PYTHONPATH=. python bin/onion.py|. Best Luke signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Traffic limitation
One way is to limit the bw in /etc/tor/torrc RelayBandwidthRate 100 KB Long term you have to get at least 2TB vps or unmetered bandwidth. Once the relay is stable there will be lot of connections. On Wednesday, June 18, 2014 8:56 PM, s...@sky-ip.org s...@sky-ip.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/18/2014 10:46 PM, Relay Admin wrote: Both has downsides but I think daily is better, if it starts to get a lot traffic than it will serve the network for a few hours every day, but in monthly if it use the all available bw in 4 days, it won't do anything for 26 days. I'm sure you can get a better answer for it from someone who limits the traffic on his/her relay. Berkay On June 18, 2014 9:11:57 PM EEST, johhher mailinglists-incom...@eigenbasis.de wrote: Hi, I'm running a Tor relay on a cheap Linux vserver with high bandwidth. I have a traffic limitation of 500Gb per month and was just wondering what would be the best configuration for the network. Currently I've limited the traffic to a daily maximum to prevent it from hibernating a long time at the end of the month. Is this the right way to do it? Or would be better to limit it on a monthly basis. Thanks for an answer! Johhher tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays That is quite a low limit for a monthly cap. If it is a high speed server it will consume the traffic within 5 days, after some time and it's known in the consensus and gains some flags. I think you are better of putting accounting per day, a daily limit of 16GB should do it. Or, see if you negotiate with your provider unlimited traffic :) long shot worth to try - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 PGP Pubkey: http://www.sky-ip.org/s...@sky-ip.org.asc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJTofVAAAoJEIN/pSyBJlsRmnsIALOSA29lsMED59ELox99J7td UKelAVzbusfvxxXIeEUW2sCYT1RTIuPhZHzT2VjrflNpppk9f9DDRQgAdB29LQeL +A4r1fjUvFYOJwUzgMirwJG+MpwjWxkLcujTTzRL4dh7eGVMffEOiNwm5KizKGIf Vuz1TII8sFB/wuRBXfGFy9iP7nOgAmrDR3k6Cid8rsPsKttwFHA1NNHSsqNkL/I4 /Rr7cIIytbDbsIqDvvCQNG0eCGoc2lRvLg6K1DW2fTJNsgOCxHiF6YzsbjrXRw/N EpfkD2EajNIS2kyrM2tKnvDaU1XkGJ9ON1vf3HeXgcE/Dj9ue6dbWulV2Hz2foc= =uUXO -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help keeping Tor relay up
If you are on Linux it is worth to install ARM to monitor it. https://www.torproject.org/projects/arm.html.en Also check from https://globe.torproject.org/ On Thursday, June 19, 2014 5:26 AM, Evelyne Fong darkbahamu...@hotmail.com wrote: I've managed to get my relay running long enough to run the bandwidth check and have it succeed. I'll check Atlus and it'll say my relay's up and running. However when I check again about an hour later, it's saying that Running: false. I've set up the relay recently, so I'm not expecting a lot of traffic. However, I'm confused as to if my relay is suddenly failing for no reason or is Atlus saying my relay is no longer running because there's no traffic on it. Any help would be appreciated. Thanks. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor-arm question
What does the cat /var/log/tor/log says? On Tuesday, June 17, 2014 6:56 PM, Adam Griffin adgri...@gmail.com wrote: Running top in a separate SSH session shows ~50% load average. I imagine spikes would cause the CLI interruptions and maybe relay unresponsive/resumed notices. Did you have the same blank uptime issue? On Tue, Jun 17, 2014 at 2:08 PM, Elrippo elri...@elrippoisland.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Had the same issues on my pi when running over ssh. It simply is the fact, that your pi is running almost on max load. Type top in your console, and watch the pi working :) On 17. Juni 2014 19:28:23 MESZ, Adam Griffin adgri...@gmail.com wrote: Hi, Just started a new tor relay on my raspberry pi yesterday and I'm monitoring with tor-arm over ssh. I'm currently listed on atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' with 17hrs uptime. However, tor-arm is showing a blank for uptime and about once a minute, the CLI goes blank and then flickers back. (the flickering happens at the same rate for local and remote SSH) Also, about once every couple hours I get a 'Relay unresponsive' and then 10 seconds later 'Relay resumed'. Anything to do to remedy these issues? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays - -- We don't bubble you, we don't spoof you ;) Keep your data encrypted! Log you soon, your Admin elri...@elrippoisland.net Encrypted messages are welcome. 0x84DF1F7E6AE03644 - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.11 (GNU/Linux) mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU 3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPIdocPLBaeA/tRD8Pg5CCmncAmSub4F5T An7FlnACtSOv3cIWQ0TymS42DihDaJ5d1RvNzKw+zHYdPvf471JFZR3TDhkPbLIr 9czR7kbpnXRwchgwXQn306NVWf37TgA8wpbnFTazZ38iOeqcb9oKprqnbgEdr3PN OhKSlMTkzAqf3MEi2Fyua4BADMhS3oBwCRgDTlt6wquEytpNSlZaHnyiyIgOpekF Uy5K3w8NhHqeifRPrNb/UcCbXtXz+puqIEZHMenpv6FRlTTKpdoHoVXSkp1TPMGN /VaCiLbP4Z3xEw/9EbAJJkhmmx1Qw3ueoqc4h1MmhUtIdxSZ/oA9SjwlnY++zvaZ 6w1wTS4P+OUkETNDtItdpxXMJ9qfSy9voAQc2K43WMZCCmpPJYSdqaZZNPFj+Ne8
Re: [tor-relays] Traffic limitation
I cannot remember where I read it, but I have read that it is preferred to run a higher speed relay with accounting over a low speed relay. Also, from https://www.torproject.org/docs/faq#LimitTotalBandwidth : Note that your relay won't wake up exactly at the beginning of each accounting period. It will keep track of how quickly it used its quota in the last period, and choose a random point in the new interval to wake up. This way we avoid having hundreds of relays working at the beginning of each month but none still up by the end. On 06/19/2014 08:17 AM, Contra Band wrote: One way is to limit the bw in /etc/tor/torrc RelayBandwidthRate 100 KB Long term you have to get at least 2TB vps or unmetered bandwidth. Once the relay is stable there will be lot of connections. On Wednesday, June 18, 2014 8:56 PM, s...@sky-ip.org s...@sky-ip.org wrote: On 6/18/2014 10:46 PM, Relay Admin wrote: Both has downsides but I think daily is better, if it starts to get a lot traffic than it will serve the network for a few hours every day, but in monthly if it use the all available bw in 4 days, it won't do anything for 26 days. I'm sure you can get a better answer for it from someone who limits the traffic on his/her relay. Berkay On June 18, 2014 9:11:57 PM EEST, johhher mailinglists-incom...@eigenbasis.de wrote: Hi, I'm running a Tor relay on a cheap Linux vserver with high bandwidth. I have a traffic limitation of 500Gb per month and was just wondering what would be the best configuration for the network. Currently I've limited the traffic to a daily maximum to prevent it from hibernating a long time at the end of the month. Is this the right way to do it? Or would be better to limit it on a monthly basis. Thanks for an answer! Johhher tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays That is quite a low limit for a monthly cap. If it is a high speed server it will consume the traffic within 5 days, after some time and it's known in the consensus and gains some flags. I think you are better of putting accounting per day, a daily limit of 16GB should do it. Or, see if you negotiate with your provider unlimited traffic :) long shot worth to try ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] CLI tool like Atlast
Does tor-prompt provide any more info than arm? I assume you mean the control prompt in arm (the fifth page). That prompt is similar and was the basis for the tor-prompt, but it's being removed from arm (that panel causes curses glitches) and the Stem version of the /info command includes all descriptor output for a relay. Here's an example /info moria1 moria1 (9695DFC35FFEB861329B9F1AB04C46397020CE31) address: 128.31.0.34:9101 (moria.csail.mit.edu) tor version: 0.2.5.4-alpha-dev flags: Authority, Fast, HSDir, Named, Running, Stable, V2Dir, Valid exit policy: reject *:* contact: 1024D/28988BF5 arma mit edu Server Descriptor: router moria1 128.31.0.34 9101 0 9131 platform Tor 0.2.5.4-alpha-dev on Linux protocols Link 1 2 Circuit 1 published 2014-06-19 01:57:28 fingerprint 9695 DFC3 5FFE B861 329B 9F1A B04C 4639 7020 CE31 uptime 1130120 bandwidth 512000 62914560 1288658 extra-info-digest 9BA9064FC6C413BA03FEB5AB25A9081B8A2D8436 caches-extra-info onion-key -BEGIN RSA PUBLIC KEY- MIGJAoGBAOfhLtI8FpZS27FvUdEYltlAOFJsdwCWYNvdZ3ivqtXRt6Rp0Oq94+fo LlKx4XzjU7GpPs1kWO62I/Xlwqh6rgbc7vgxlVPcuHXCirckYOxEvda9Me+no2Ny GsWsL1PoT8vGTpjL5ONQaudzVDfEa71KMXASv6YcLakJj4Ge7IElAgMBAAE= -END RSA PUBLIC KEY- signing-key -BEGIN RSA PUBLIC KEY- MIGJAoGBALtJ9uD7cD7iHjqNA3AgsX9prES5QN+yFQyr2uOkxzhvunnaf6SNhzWW bkfylnMrRm/qCz/czcjZO6N6EKHcXmypehvP566B7gAQ9vDsb+l7VZVWgXvzNc2s tl3P7qpC08rgyJh1GqmtQTCesIDqkEyWxwToympCt09ZQRq+fIttAgMBAAE= -END RSA PUBLIC KEY- hidden-service-dir contact 1024D/28988BF5 arma mit edu ntor-onion-key VhxdpiMoHxrTHqGFu7Eupcy4hnh/nSJw3xOpO4J1/n4= reject *:* router-signature -BEGIN SIGNATURE- FVnuIM/22C/jzf3vuPr/nsZ4Azq3KM0wzdF/76mgcoEbVs94Tl91wtvHX+g/q0xf OI2jubHu2k7GDMs3Tirqmohdu90VYYxCklXIKXtscRthFrS+fZP2GB8HDtPZseAZ JMXMYZbWZ9ai6Fyygu1cPE5oqW7lL3r7Lq4DQJ0fQyo= -END SIGNATURE- Extrainfo Descriptor: extra-info moria1 9695DFC35FFEB861329B9F1AB04C46397020CE31 published 2014-06-19 01:57:28 write-history 2014-06-19 01:48:17 (900 s) 496873472,822779904,678929408,473645056,506991616,715395072,681116672,411208704,451326976,656055296,630102016,410365952,510575616,685982720,657693696,440340480,462490624,653119488,586785792,424977408,415206400,685920256,716089344,546408448,561561600,860252160,766703616,508184576,497261568,808691712,822632448,552358912,551654400,836164608,740415488,554012672,515691520,784584704,750459904,516459520,530599936,800103424,781259776,483474432,539444224,867778560,809338880,632835072,560136192,869916672,806222848,537466880,538954752,849017856,828844032,549480448,549689344,978973696,940964864,698497024,739622912,1070049280,966208512,676659200,734222336,1059842048,943287296,662800384,713388032,1012765696,971621376,595393536,613312512,917506048,870929408,549361664,568411136,972704768,894880768,568323072,598233088,849361920,743531520,481337344,454830080,786594816,710964224,546359296,462736384,667881472,652960768,401728512,430392320,692613120,618632192,388550656 read-history 2014-06-19 01:48:17 (900 s) 79498240,69858304,64569344,60034048,91601920,76338176,64618496,59077632,80771072,63081472,64591872,58112000,89427968,64851968,63969280,60345344,80471040,71065600,62567424,61836288,77986816,63676416,69273600,61675520,80965632,70822912,65712128,59408384,75437056,66962432,69486592,61251584,80453632,70142976,74030080,89346048,82542592,69871616,81146880,72501248,86639616,71948288,72060928,63085568,81788928,69519360,76326912,102928384,83399680,70574080,73345024,70081536,88821760,72610816,72532992,64514048,88225792,74373120,74736640,71306240,95561728,107585536,76473344,72662016,95979520,83960832,79443968,7920,96991232,81178624,84353024,72841216,86589440,77880320,85440512,68847616,87705600,79765504,80477184,109486080,90619904,75940864,72767488,62712832,77673472,69785600,69362688,171729920,103734272,60462080,60198912,54415360,72517632,62489600,56928256,53815296 dirreq-write-history 2014-06-19 01:48:17 (900 s)
Re: [tor-relays] Help keeping Tor relay up
Yes, I do. I've attempted to set my bandwidth cap to 50 GB per day. I'm running this on Windows 7. From: alexander3223...@gmail.com Date: Thu, 19 Jun 2014 03:01:36 -0700 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Help keeping Tor relay up On Wed, Jun 18, 2014 at 10:11 PM, Evelyne Fong darkbahamu...@hotmail.com wrote: I've set up the relay recently, so I'm not expecting a lot of traffic. However, I'm confused as to if my relay is suddenly failing for no reason or is Atlus saying my relay is no longer running because there's no traffic on it. Do you have hibernation set up? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] tor-arm question
Last 'log' entry was from a few days ago when I started it. Just shows bootstrapping 0-100% without errors. 'notices.log' entries happen fairly regularly. Mostly heartbeat uptime notifications and lifetime sent/received. Also bugging me to add my ContactInfo. No errors relating to tor-arm's odd behavior. On Thu, Jun 19, 2014 at 8:24 AM, Contra Band contra0b...@yahoo.com wrote: What does the cat /var/log/tor/log says? On Tuesday, June 17, 2014 6:56 PM, Adam Griffin adgri...@gmail.com wrote: Running top in a separate SSH session shows ~50% load average. I imagine spikes would cause the CLI interruptions and maybe relay unresponsive/resumed notices. Did you have the same blank uptime issue? On Tue, Jun 17, 2014 at 2:08 PM, Elrippo elri...@elrippoisland.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Had the same issues on my pi when running over ssh. It simply is the fact, that your pi is running almost on max load. Type top in your console, and watch the pi working :) On 17. Juni 2014 19:28:23 MESZ, Adam Griffin adgri...@gmail.com wrote: Hi, Just started a new tor relay on my raspberry pi yesterday and I'm monitoring with tor-arm over ssh. I'm currently listed on atlas.torproject.org with flags 'Fast', 'Running', 'V2Dir', and 'Valid' with 17hrs uptime. However, tor-arm is showing a blank for uptime and about once a minute, the CLI goes blank and then flickers back. (the flickering happens at the same rate for local and remote SSH) Also, about once every couple hours I get a 'Relay unresponsive' and then 10 seconds later 'Relay resumed'. Anything to do to remedy these issues? ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays - -- We don't bubble you, we don't spoof you ;) Keep your data encrypted! Log you soon, your Admin elri...@elrippoisland.net Encrypted messages are welcome. 0x84DF1F7E6AE03644 - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.11 (GNU/Linux) mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU
[tor-relays] Yahoo and AOL emails removed from tor-relays due to bounces
It seems Yahoo and AOL email servers have decided to refuse all messages from this tor-relays list. Other lists aren't affected, yet. We're seeing this message from Yahoo and AOL servers: Status: 5.2.1 Remote-MTA: dns; mailin-04.mx.aol.com Diagnostic-Code: smtp; 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being refused due to provided DMARC Policy There is no fix for this yet as it breaks mailing list software globally. This bug explains the situation, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752084 If you use yahoo or aol for email, unfortunately you can't join nor receive email from our lists. I suspect this will become true for all of our email lists soon. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] CentOS of the air
At about 02:00 UTC June 18th 2014, changes at the domain registrar caused the CentOS.org domain to get marked as Inactive. This caused widespread outages, with all services in centos.org including: - - Mirror Network ( internal centos.org as well as external ) - - All mirrorlist - - All isolist - - Website ( including bugs.centos.org and wiki.centos.org - - All internal support infrastructure Services were restored at the registrar just before 9:00 AM UTC June 18th, however depending on dns path some users might still see issues for upto 6 to 8 hrs from that point. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Yahoo and AOL emails removed from tor-relays due to bounces
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Does the list support email addresses from hidden_service *.onion mail servers? If so, I've got one :) On 19. Juni 2014 21:36:35 MESZ, Andrew Lewman and...@torproject.is wrote: It seems Yahoo and AOL email servers have decided to refuse all messages from this tor-relays list. Other lists aren't affected, yet. We're seeing this message from Yahoo and AOL servers: Status: 5.2.1 Remote-MTA: dns; mailin-04.mx.aol.com Diagnostic-Code: smtp; 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being refused due to provided DMARC Policy There is no fix for this yet as it breaks mailing list software globally. This bug explains the situation, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752084 If you use yahoo or aol for email, unfortunately you can't join nor receive email from our lists. I suspect this will become true for all of our email lists soon. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays - -- We don't bubble you, we don't spoof you ;) Keep your data encrypted! Log you soon, your Admin elri...@elrippoisland.net Encrypted messages are welcome. 0x84DF1F7E6AE03644 - -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.11 (GNU/Linux) mQINBFH797MBEAC0Y0NeI7lmDR9szTEcWuHuRe0r/WjSRC0Nr5nXsghuMcxpJ3Dd BOBimi4hdMMK4iqPVMwNw6GpKYR3A9LHHjbYRXHUKrJmB+BaJVyzJXN5H6XvxTTb UfX+DaXAGJW/G+3cBB3qm/QaU8QGkBKfXq0DLTaTGPkGKxEAldj/8onGZhawdJs+ B92JrW+S2HDh15pIuXzSqe7eCcIOdvvwfWe0fJi2AraA7LYGpxP6GcC/b9JJpbq5 Y6DfE2Aun9ZK3iHqURyrms0Whbv1CgmUahL2MVYCsTsXwe0GwlAxxKvjXAiXuo+R 9wO5wsXvVVSVNqsk9Yqi+wYzdPKndTU0GyxSApQHroF+cxaZ8Lk0xloj18+LdCSs e5IiTSXH0MMsDdWWdHlrgk+bgDG+0Gu3ne4vMwGdKO7AhYgQW/ueMy4RnkG/nsV9 jry5BO4gGAI1Ij8KvqUzEnvJFGE3ptJogU+zazWWDUWmL3ecKb3aDRlJFnZ3kJ5h q8GolZVjpk99V+4B5WVRPXdej/p5J19tXycK/jdNmr4oC8NyUhIpe8xHELnfoB4z +rxiTx+KMnW0rY8EQg8O2ixEYt5my90IwQkxcxIxextVrqjJjYn8extc2/v8yGzI KmTEJxdADB5v/Jx4HiLHNDSfBUb8gfONCkNSTYvTcSwTjWzHOkXeE/9ZbQARAQAB tD5lbHJpcHBvIChrZWVwIHlvdXIgZGF0YSBlbmNyeXB0ZWQpIDxlbHJpcHBvQGVs cmlwcG9pc2xhbmQubmV0PokCOAQTAQIAIgUCUfv3swIbLwYLCQgHAwIGFQgCCQoL BBYCAwECHgECF4AACgkQhN8ffmrgNkT8+BAAoAXBqu4/O2Cs5FSWWZpzgScNEgq7 uHhOKeYmRfgKlOUPoYlPB1DBqdOAXSKb9OvsmyOvpoGnqijB7aAJBoyQYW/OCQgd U8L4eTCf4yRZnfFLdgskcPfN1p0Rs/yinGEooBJFtYa7mT6J0UTW2JjCLZK2AFCW oF+KBu5JICXGBXigb2ZbX1jWjxP5H1RidQw6HF5z4z34SjLWAOOeZ8B/Xfz6Fs0s IAuLu2O4HE4DI8Qu196LhSVHHgr3uMTkvN1t5nKwyjrRQztwXXk9qIomII3ydNYb BYAGdWNNMfLb1kmDwC5wQHAFvSP1aiMF3aKAY+gl2wXSGO6JqM0SteJS3dytIljI kzu0atc9HuGs/HDQgdmpAS4WU2YefEr/WieltSiAKlwuC+3wg+CONJ6TE1vgNDU/ axerttb0jq7UQb/nAp05bsrB7XH1Vs+1ON9lUPEfWRmwQcrVK5JUrUWa/4tA/UeM XvFcPFtFluGTlLewgJIqcvjPXFwpbDZprXJsMkwew/A6B6n3+0sbgf7p3QSGkVbi dwQAymTbHdYqLnbcnKZhjto3Wjw1J5QB2wuiRYlpjV3i7AWTGlqoSTOWCCV+HamQ qeFYNYAWNFx3+J/oi7xDi8t9bHVNA205equ+y2sj3G5uGJ6LSHQ8AXp9uOipUUvU 1MJN0yLXr9PIwvi5Ag0EUfv3swEQAL0+MnxHGrTjSYdfdua4SBpmytDONM1EngeY s+WyaC/760MughKbaysI/nK2LB1vnwEY7f3NM4fxBx8u2T7VBm6Ez6Fs23Bb8Rkz f97bPSdxCmg64GPHfLA9uwTIXcYS+MpI86WOf6eWY0rRpf7Y9Nl7YoUNvzOyUPqc ggdcnHce8zYv7A/WS8flZDm8tVFPsHrQDEwNMws7ZhiNnHkeZeRJrvCuB7oEVich O/ROYoA5o6NozWYQbjxe1f6Yur4Q10qgVcxVnyLFJSbg6vZSzL7KYh3Z5iBOzPHt 7cwEDrW8W4Kl2Qj8rhJ4Wxs94CAtua7IXK44sVZWQbyHcOXRikgGMZKkEZzVCQa5 KD1u1ZrcBCyuMAir0hsmS3jhCUwpiE2c3SRk8O8CgixhTcBk0X/k9ZFu3Hbi1JMB FLzs/Nq3tYAYvVivhPloSxmYBPsafYHCZM83yBNNsralXh5zjB+di90G+AMXt2PN LTcdovZuWtC0s8/jrx+zv/AA4FAGYU9OVl+YL9ybFX8gSdMEcixyzQcKfiFBjpWv 5iFrwIuDlaXMcheyrhc9aGOxfx44OXc505+VjO/1Q/8EOWlJ6UwOi6GMkj5T+RFJ MDyP0UixS7dt6wTuD5t6PRuyWWxZswgrbL9hjwGFr154Z19TWeNWc23pWtUvQJos UCxl2nFHABEBAAGJBD4EGAECAAkFAlH797MCGy4CKQkQhN8ffmrgNkTBXSAEGQEC AAYFAlH797MACgkQJEPd69lQ0evA+Q/+M7lSFlrQWiRsFqDjh+kTJc+0OEBCvnfo N2KPyXXbfc//qup55PfEygE6C60zvrlv3WE33GZ5GS5MLuDMP82b+a5Yt16NQU7L WtAg1g0S0BvazW+28TgnfO8bhbGaFeE9ccw3xLmlbwZQ3f3LtMKdwFIROiG6hvAs 9U54QYti3tv9DowRYYWpdr0Ga8RqeGNtCKc0v2opy51MpzKWjwUW0i3XlSlyY8Lj 1KT8PyznNPw32nYpmDizz+0OUJNnn/kT+GnFoR3DJnFosTOrnxFJp+N+nejMp/gW r9NM0/E7H+P53IiytBOt5/0vsOaCFGdYGhKEjmJi3dHS4Xk1ObD1mjdD1YDOlWWU 3Md6BDHd4W7Q8gT7oQfTIMLd3HzV+WNPIdocPLBaeA/tRD8Pg5CCmncAmSub4F5T An7FlnACtSOv3cIWQ0TymS42DihDaJ5d1RvNzKw+zHYdPvf471JFZR3TDhkPbLIr 9czR7kbpnXRwchgwXQn306NVWf37TgA8wpbnFTazZ38iOeqcb9oKprqnbgEdr3PN OhKSlMTkzAqf3MEi2Fyua4BADMhS3oBwCRgDTlt6wquEytpNSlZaHnyiyIgOpekF Uy5K3w8NhHqeifRPrNb/UcCbXtXz+puqIEZHMenpv6FRlTTKpdoHoVXSkp1TPMGN /VaCiLbP4Z3xEw/9EbAJJkhmmx1Qw3ueoqc4h1MmhUtIdxSZ/oA9SjwlnY++zvaZ 6w1wTS4P+OUkETNDtItdpxXMJ9qfSy9voAQc2K43WMZCCmpPJYSdqaZZNPFj+Ne8 6FNtNKuUkXREybpHwlVAXnHzInmFOOM9RAmF70r3zEmKt77W1ztBLo2o9X79gPgL u9ThgrH6Oc2k46n+9nc3joccr7miiX/bp976DNWcWdOYThiSSOCb8Zw9/Zs935i1 wUVkYTj24tmBH4H5ov9ib7RPmU21ru458RbUKG0ONAqBtAHNyXHzUnXsrke+D4VW MI06YcXSk8YeYgQ8GxgHQc+W2bb8LIbKN1hEYJ0wzM62vKR2/Oiwuf8lXutIKTuz +v7Vj1PQd66DGHsxtWRaWnr1c54JTL2wICHJYKFH4grp7864+GL/uQ1O/Z/XxVku
Re: [tor-relays] CLI tool like Atlast
there you go: https://github.com/woeisme/torchart On 06/18/2014 03:17 PM, Kali Tor wrote: Hi, On Wednesday, June 18, 2014 11:26 AM, ja...@icetor.is ja...@icetor.is wrote: I fooled around with some php json parsing in order to get my metrics charts working on icetor.is . I can send you the code if you'd like. -Jason That would be much appreciated! Thanks, KaliTor On 06/18/2014 10:15 AM, Lukas Erlacher wrote: Hi, I'm working on that. The onion.py script in OnionPy [1] has some rudimentary atlas-like functionality that I hope I can soon make complete as soon as I find some free time. If you know python, it shouldn't be too hard to do that, PR's welcome! Best, Luke [1] https://github.com/duk3luk3/onion-py On 06/18/2014 12:01 PM, Kali Tor wrote: Hi all, Is there a CLI client/tool that does what https://atlas.torproject.org/ does? Basically provide an output based on a node's fingerprint? e.g. https://atlas.torproject.org/#details/7EDE11A41D1C7DF4F9103ABAA4F0A31E42CB0C02 Thanks, KaliTor ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Yahoo and AOL emails removed from tor-relays due to bounces
But I just received this email! _KaliTor_ On Thu, 6/19/14, Andrew Lewman and...@torproject.is wrote: Subject: [tor-relays] Yahoo and AOL emails removed from tor-relays due to bounces To: tor-relays@lists.torproject.org Date: Thursday, June 19, 2014, 12:36 PM It seems Yahoo and AOL email servers have decided to refuse all messages from this tor-relays list. Other lists aren't affected, yet. We're seeing this message from Yahoo and AOL servers: Status: 5.2.1 Remote-MTA: dns; mailin-04.mx.aol.com Diagnostic-Code: smtp; 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being refused due to provided DMARC Policy There is no fix for this yet as it breaks mailing list software globally. This bug explains the situation, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752084 If you use yahoo or aol for email, unfortunately you can't join nor receive email from our lists. I suspect this will become true for all of our email lists soon. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
