Hi,
You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/6D7079FDCC0E29DFF8FD239AE0F0D7...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Ideally you will switch to keeping up with our stable releases, but if you need a stable that is especially stable, the Tor 0.3.5 branch will be maintained until Feb 2022: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorR... and you can see the lifetimes of other Tor versions on that table too.
Let us know if we can do anything to make the process easier.
And lastly, I am cc'ing the new network health mailing list (which has public archives), to help us stay synced: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkHealthTeam
Thanks! --Roger
Hi,
see me a bit surprised to get the email, didn't expect it.
Am 02.09.19 um 10:50 schrieb Roger Dingledine:
You are running a Tor relay, which is great: http://rougmnvswfsmd4dq.onion/rs.html#details/6D7079FDCC0E29DFF8FD239AE0F0D7...
First: that Tor version is obsolete, and because of old bugs, we will soon cut relays running those versions out of the network. Please consider upgrading!
Yes, I'm aware of this. Updating isn't trivial.
Second: let us know if there is any way to help you bump up the bandwidth that you are allocating to the Tor relay. :)
Not much. This relay is running on consumer internet access, 60 Mbit download, but only 3 Mbit upload, so 200 kB/s is about what I can allocate without disturbing other traffic too much.
You can find Tor packages for your distro / OS here: https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Platformspecific...
Unfortunately there's none for OpenWRT, which happens to be the router's OS. This relay is running directly on the router, the only device running 24/7 here.
There's hope: next OpenWRT release will provide Tor v0.4.1.5, so it's just a matter of waiting for this to be released.
https://github.com/openwrt/packages/commit/1ac69ffc594fc8e3692ceb63a2013f909...
Another note: this relay is running for more than two years already (always "Traumflug"). I just had to generate new keys, because previous keys aborted with "The signing cert we have was not signed with the master key we loaded!" (not sure what exactly caused this).
Markus
Hi Markus,
On 2 Sep 2019, at 21:47, Markus Hitter mah@jump-ing.de wrote:
Another note: this relay is running for more than two years already (always "Traumflug"). I just had to generate new keys, because previous keys aborted with "The signing cert we have was not signed with the master key we loaded!" (not sure what exactly caused this).
I remember that bug!
We fixed it a while ago, upgrading to the latest 0.4.1 should make sure it never happens again.
T
On Mon, Sep 02, 2019 at 01:47:01PM +0200, Markus Hitter wrote:
There's hope: next OpenWRT release will provide Tor v0.4.1.5, so it's just a matter of waiting for this to be released.
https://github.com/openwrt/packages/commit/1ac69ffc594fc8e3692ceb63a2013f909...
Ok, sounds good.
I notice that there is an 0.4.1.6 out, as of almost a month ago, and as we wait longer there will probably be a few more point releases. I don't see any huge bugs addressed in the 0.4.1.6 minor version, but that doesn't mean anything about whether the next minor version will have something important.
I also looked a bit at the init script: https://github.com/openwrt/packages/blob/master/net/tor/files/tor.init and it doesn't do things like raising the max number of file descriptors ("ulimit -n") so it will have problems being a proper relay.
In sum, I would say to be wary of running a relay with the current (or upcoming) openwrt package, because it is missing many of the things that a proper Tor package should have. Maybe that means we should encourage you to fix up the openwrt package? Or maybe that means we should warn people away from it? :)
Thanks, --Roger
Am 14.10.19 um 12:26 schrieb Roger Dingledine:
I also looked a bit at the init script: https://github.com/openwrt/packages/blob/master/net/tor/files/tor.init and it doesn't do things like raising the max number of file descriptors ("ulimit -n") so it will have problems being a proper relay.
Well, right now it uses a total of 14 open file descriptors, which doesn't exactly make the default of 1024 look like a throughput limiting barrier. Everything is a bit smaller on routers :-)
In sum, I would say to be wary of running a relay with the current (or upcoming) openwrt package, because it is missing many of the things that a proper Tor package should have. Maybe that means we should encourage you to fix up the openwrt package? Or maybe that means we should warn people away from it? :)
Warning people away is obviously not a good recipe for growth, so I'd prefer to get Tor better aligned with small servers. Like refining it to get away with fewer file descriptors if necessary. Also refining it to get away with 128 MB RAM without complaining. Current usage is 19% of 128 MB, > 50% system memory unused, it apparently works fine with this few memory.
Running Tor on routers is obviously a great opportunity, because the hardware exists already, devices run anyways, and there are millions of them. One doesn't have to advertise "buy a $2000 server, rent a $50/month ISP line, pay the electricity bill", one can advertise just "help by installing this package". Likely routers can serve only a few connections simultaneously, still 10 connections multiplied by a million "servers" isn't too shabby, IMHO.
Markus
network-health@lists.torproject.org
-
Markus Hitter -
Roger Dingledine -
teor