<div dir="ltr">I can only spare a few GB or so day from my home internet, so I set the ACCOUNTING MAX daily limit to 3GB (in + out = 6GB) and RELAYBANDWIDTHRATE to 200KB (BURST 400KB), after much experimenting this was the balance between not hibernating before the 24hr are over and leaving enough bytes left over for me + my house 4K netflix use.<div><br></div><div>Recently, 3GB daily limit hasn't been enough to last the 24 hours some days it went offline at the afternoon, I raised ACCOUNTINGMAX to 4GB and it seems fine.</div><div><br></div><div>Perhaps this is related to the recently trends (I am non-exit, middle only). Unfortunately I do have to reboot my relay once a week or so due to updates or other people I live with messing with the home router's reset switch when they deem their netflix over wifi experience to be poor so I will probably never get the guard flag.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 26, 2017 at 12:04 PM, Iomega <span dir="ltr"><<a href="mailto:iomega@protonmail.ch" target="_blank">iomega@protonmail.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>I run a small relay and it went down intermittently during Nov 1 to Nov 25, with a lot of hiccups [1] since I started it earlier in the year, which may or may not be due to this attack. It is my first and only relay so I cannot relate.<br></div><div><br></div><div>What I can say is that during most of that time in November, the relay was running, the instance was running, tor was running (if with an older version), there were no traffic restrictions I can say, etc.<br></div><div><br></div><div>Obviously after that period the relay lost its Guard flag, and since 0.3.1.9 the relay it seems to be catching up quickly, actually with much more traffic than any time before.<br></div><div><br></div><div>In the past days I did a lot of cleanup so I cannot provide logs (I barely log notices, not even that if there are no issues).<br></div><div><br></div><div>[1] <a href="https://atlas.torproject.org/#details/1FA8F638298645BE58AC905276680889CB795A94" target="_blank">https://atlas.torproject.org/#<wbr>details/<wbr>1FA8F638298645BE58AC9052766808<wbr>89CB795A94</a><br></div><div><br></div><blockquote class="m_-2267721316592773144protonmail_quote" type="cite"><span class=""><div>-------- Original Message --------<br></div><div>Subject: Re: [tor-relays] Decline in relays<br></div><div>Local Time: December 26, 2017 11:16 AM<br></div><div>UTC Time: December 26, 2017 11:16 AM<br></div><div>From: <a href="mailto:zwiebel@quantentunnel.de" target="_blank">zwiebel@quantentunnel.de</a><br></div><div>To: <a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.<wbr>org</a><br></div><div><br></div><div><div>-----BEGIN PGP SIGNED MESSAGE-----<br></div><div> Hash: SHA256<br></div><div> <br></div><div> <br></div><div> Am 23-Oct-17 um 15:32 schrieb David Goulet:<br></div></div><blockquote><div><div>Since July 2017, there has been a steady decline in relays from ~7k<br></div><div> to now ~6.5k. This is a bit unusual that is we don't see often such<br></div><div> a steady behavior of relays going offline (at least that I can<br></div><div> remember...).<br></div></div><div><div>It could certainly be something normal here. However, we shouldn't<br></div><div> rule out a bug in tor as well. The steadyness of the decline makes<br></div><div> me a bit more worried than usual.<br></div></div></blockquote><div> <br></div></span><blockquote><span class=""><div><div>That being said, I don't have an easy way to list which relays went<br></div><div> offline during the decline (since July basically) to see if a<br></div><div> common pattern emerges.<br></div></div><div><div>So few things. First, if anyone on this list noticed that their<br></div><div> relay went off the consensus while still having tor running, it is<br></div><div> a good time to inform this thread :).<br></div></div></span><div><span class=""><div>Second, anyone could have an idea of what possibly is going on that<br></div><div> is have one or more theories. Even better, if you have some tooling<br></div></span><div> to try to list which relays went offline, that would be <i>awesome</i>.<br></div></div></blockquote><span class=""><div><div> <br></div><div> a) Please find two pictures which show tap[1] and ntor[2] in 2016 and<br></div><div> 2017 for a certain relay. Obviously the number of tap/ntor increases<br></div><div> since July 2017.<br></div><div> <br></div><div> b) Taps becoming hourly massive on all my guards since October 2017.<br></div><div> <br></div><div> c) An other relay had the largest amount of taps. It received 6<br></div><div> million taps. The tap flood took 65 minutes and the tor cpu power went<br></div><div> up from 60% before to 120-210% during the flood.<br></div><div> <br></div><div> I can not prove but because of outbound packet abuse letters from an<br></div><div> ISP I start thinking if this is an other measure to damage guard/hsdir<br></div><div> flags. Beside the enormous consumption of cpu resources.<br></div><div> <br></div><div> I hope this helps.<br></div><div> <br></div><div> [TAP 1] <a href="https://i.imgur.com/jDj3M5W.jpg" target="_blank">https://i.imgur.com/jDj3M5W.<wbr>jpg</a><br></div><div> [NTOR 2] <a href="https://i.imgur.com/jDncdMx.jpg" target="_blank">https://i.imgur.com/jDncdMx.<wbr>jpg</a><br></div><div> <br></div></div></span><div><hr><br></div><span class=""><div><div>Cheers, Felix<br></div><div> -----BEGIN PGP SIGNATURE-----<br></div><div> Version: GnuPG v2<br></div><div> <br></div><div> iQIcBAEBCAAGBQJaQi/<wbr>cAAoJEF1W24InZUQdA48QAOy8CnnJG<wbr>Mkl+d9B844JE4uE<br></div><div> vZ2L96OSFOCl7Au3l+V/<wbr>dYIvgdMUUe4ju8hQHhzB0918IY8Y4l<wbr>MngTTgptVfwhKv<br></div><div> cb6RB6Ib8/<wbr>1zfzLtmrEn6pdiHoUY2qlm7xB6lzsf<wbr>az3JT+KOTq1adzV9DSQAAkNV<br></div><div> Cp0+jdpYX/<wbr>X3T7OOXzSxUDmKiqaMu7K181agMeyy<wbr>bUFzIPEZgmRCdnYNHmD2W2aH<br></div><div> zjBfSm5J1OncFcs5GwmtCKCUq5DVrj<wbr>jmYZHLB4E91ExQafwcqLYfqAQDqh8u<wbr>i0tW<br></div><div> W9//<wbr>fkgPxcNgQ5hOQq2Ucf7cZJ1I12fKCA<wbr>pBYtfgfq91sCtt2+sozNnr4u5d5Jxy<br></div><div> JxiWX/<wbr>t5MEWjvXcAy3jOYoPnTiuDHwG6EYWj<wbr>omU+RpZwqJkdV00043a8F9UzYe67<br></div><div> O7/<wbr>pRcDSZe3MdL7CkLZcirNMS0dSHPlxL<wbr>WJCd0XlWPs5d8aW/<wbr>F8kRFndQoisN7c7<br></div><div> zxeFFUs9/NRPCCXrzymX/<wbr>rTgUtlvZ8xKjQ0K8v/<wbr>giLXoNxTf02P5FK4pcD3Bu47m<br></div><div> qGTqfiaBFywDvFA5+<wbr>icDZICJqFxtBG+6W0tWO8K79w+<wbr>oKmqEyk6TBKhZDZWcH1K4<br></div><div> Qu62tkOZs7Qp8jKz6M8kYWsr+ATO8+<wbr>IWz6o/<wbr>xWTZJPVeir8qsZShR71Xz4kGftu2<br></div><div> 1Sar8xKb/lw+xQAOoV27<br></div><div> =Nqx3<br></div><div> -----END PGP SIGNATURE-----<br></div></div><div><hr><br></div></span><span class=""><div><div>tor-relays mailing list<br></div><div> <a href="mailto:tor-relays@lists.torproject.org" target="_blank">tor-relays@lists.torproject.<wbr>org</a><br></div><div> <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" target="_blank">https://lists.torproject.org/<wbr>cgi-bin/mailman/listinfo/tor-<wbr>relays</a><br></div></div></span></blockquote><div><br></div><br>______________________________<wbr>_________________<br>
tor-relays mailing list<br>
<a href="mailto:tor-relays@lists.torproject.org">tor-relays@lists.torproject.<wbr>org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays" rel="noreferrer" target="_blank">https://lists.torproject.org/<wbr>cgi-bin/mailman/listinfo/tor-<wbr>relays</a><br>
<br></blockquote></div><br></div>