<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div>On 17 Oct 2017, at 17:02, tor <<a href="mailto:tor@anondroid.com">tor@anondroid.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div>> You are on 0.2.9.11 and #20059 was merged in 0.2.9.12<br></div><div>> <a href="https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?h=release-0.2.9">https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?h=release-0.2.9</a><br></div><div><br></div><div>I see. I'm trying to stay on 0.2.9.x since that is considered the "long-term support" release. This is a fallback directory mirror which I'd like to keep as stable as possible. apt wants to upgrade straight to 0.3.1.7 (from the repo at <a href="http://deb.torproject.org/torproject.org">http://deb.torproject.org/torproject.org</a>). I will see if I can install 0.2.9.12 from the repo instead, or perhaps install the package manually (or perhaps give up and switch to 0.3.1.7).</div></div></blockquote><div><br></div>I think Tor LTS / 0.2.9 is in Debian stable:<div><br></div><div><a href="http://deb.torproject.org/torproject.org/dists/stable/">http://deb.torproject.org/torproject.org/dists/stable/</a><br><div><br></div><div>I've opened a ticket to add LTS to the Debian repository instructions:</div><div><br></div><div><a href="https://trac.torproject.org/projects/tor/ticket/23897#ticket">https://trac.torproject.org/projects/tor/ticket/23897</a></div><div><br></div><div>I wouldn't recommend upgrading to 0.3.0 or later, there are stability issues</div><div>on some clients, and maybe relays.</div><div><br></div><div><a href="https://trac.torproject.org/projects/tor/ticket/21969">https://trac.torproject.org/projects/tor/ticket/21969</a></div><br><blockquote type="cite"><div><div>> As for the relay, I am pretty sure there is a firewall or something<br></div><div>> which throttles the incoming / outgoing TCP connection a<br></div><div>> process/user/pid can initiate or something like this. The problem is<br></div><div>> either in the operating system itself either a network-level firewall or<br></div><div>> built-in router firewall.<br></div><div><br></div><div>Could be. It's just simple iptables on the node, and I've tried to follow best practices for the sysctl and ulimit tweaks, but I don't really know what's going on upstream with the provider. It's a little odd that this is only a recent problem, as the node has been up for 700+ days and aside from kernel upgrades, there's no recent changes. Maybe it's just busier than usual now. I'll keep digging. Thanks for the feedback!</div></div></blockquote><br><div>There's a bug in 0.3.0 and later that causes clients to fetch</div><div>microdescriptors from fallbacks. So fallbacks (and authorities)</div><div>will have extra load until that's fixed.</div><div><br></div><div><a href="https://trac.torproject.org/projects/tor/ticket/23862">https://trac.torproject.org/projects/tor/ticket/23862</a></div><div><br></div><div>T</div></div></body></html>