Re: [tor-relays] Tor Consensus Weight Stuck at 20 (Even on Relay with Stable Flag)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Speak Freely: It seems like the most pertinent task would be to fix the problem, not display it. Just saying... I agree. Do we know already which relays are affected and why? teor asked in the trac entry as well. https://trac.torproject.org/projects/tor/ticket/13450 -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVVKxnAAoJEFv7XvVCELh0nOgP/j6L5CI4qrbmvff3PsVfC/R9 Tnl6evM7HSZPF56jRZCiM8Ou8gfTeYJVkWJWLqJiTzK0ac04C/+UYCP6VGeELkv1 VchwGPD6CmnYxHClCMccZdcA/vnESl/kWq39mbo+kjK8CJPyf0ApdH139nuk+lQX V59gOzFB7esq/+XQn/ByHbnW8/63TgW7kWXqAOyWkuwpZh3WCGNAsX75qkAH7dev M2fnBUUNXP7dxiqfbb5D/qaUGJpnG+9KS6t7r8pAOCgJP0ttDKg9hNqm+5LtLpWp i/uP2pmh0OY5WkNFrGBHOHsvRnykz+h8Wxb6b4rWHhLoGQqngEbia0JjPRkyxrvt I1B1tnmxQTTf5ZyuJ8XpVgMsj5ebJwAlsWVqXN9B3qjFGW8FjvpDiWEJE9G9V+Uw C5b/G4nfjz20I3ujA9dMogGmE95KJBvcrqH50KZTaS7891d4UJeRw/ey6qTnJd3N 1uCwJAZwqjG7XEKhltx7DherY3Vu1iPoAUFimV4FcDt6Tvz+rq/7+iY5PwCeZ/je 40lc1B45qacsx1tvhBFrO5X8FA5Bvd/jINuAzzqt+9RyEhLekh9+WJQyHiQGvf50 BWh1bt4XHMVE7N/kFeGwWe7tMSWlSbivqFD7+g8jGKvlkIpIfF73c9mSEi83KqwF F0bRcUkCmKOjFiOAqbxu =u3Y2 -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Please enable IPv6 on your relay!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/14/2015 05:09 AM, Sharif Olorin wrote: Hi Michael, From [0]: There is currently no support for running a DIR port on IPv6. Leave any DirPort option as is. HTH, Sharif [0]: https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto Ah, I didn't catch that. Thank you for pointing that out. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJVVJnKAAoJEKBpQL3CDq4dxjIP/3OeK1p1iBmragygr+iJ88pa UR/J2OdukjycC0MIqOsZwjx9qapDdF7t20HhX46bwaTww5I7bqX0doDVLncxv2Wc dhUxwn/5ejXFUGpLrfFSCqMNxRwMW8Xr3ObXLSeSSMcuHdu2D2WfDQqLGDgmnb66 cmrr3pbaOlir9+NAtfSTw06dgYVfE8yaHEkg3YiJDpwx2r9re4lB2EJoSCD2iopU ZSfsMyXldsD5rprCHpYzGRW8u6btOdPB4NLqeB8POHF8B53GJsGZMVy7Jh/qegIq /v+fDgcHeUJV6dgzJe37YDWnV3swdTuf7i1H00+pTDapVQfljGfzzob7900/F+u0 qfS6lqIbb4k0N2TS9bL96sksVIh4YGGSU7XTCFzCY9Yc7//Jn4gMbaBaCmhmSDlb k4k9bG9p5v7hsWUXUx6JeiCLNdo7ZFbWM83tqIFccq8MYu2Ff2LiFrxrPvlRRJxp 3ZGw1+HDXTRvZ1u7fxkyMRT+LTV14COl9vJoATV02mFtqgVwN6ngMXBiw2me6sHH +T1IQdNFS+kFwwAAoYFxBTTA9w89MrmVz4LpjmNFR3oqtiauM/VQJzpBMdyDFwMv ABu+E4DPEXjJ/lI4angbWMz64mgG7uwv5JyDoo4BApQrVNHOFa1Rf5wOjAjYjBWC Yx5jJYPOLnOJbP95Dzyl =XnNM -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor Consensus Weight Stuck at 20 (Even on Relay with Stable Flag)
From my experience, this happens only with exit relays. Changing from an exit relay to a guard fixes the problem immediately. I've seen past threads that mentioned deleting your id key would fix the problem, but that never fixed it for me. But that is also counter-intuitive given that going from exit to guard while keeping the same id fixes the problem. If I recall correctly, going back to exit causes the problem to re-appear - I will see if I can confirm that again with one of my guards-that-was-exit. The common theme I keep seeing is that the bwauths need to fix their systems, but beyond that, or which part of their system, I don't know. Matt Speak Freely ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Please enable IPv6 on your relay!
Tunnelbroker's ToS don't seem to prohibit proxies/relays, so I don't see an issue here. Don't know how they'd react to exits, though. On 13/05/2015 19:09, Michael Gorbach wrote: Is there anything I should be concerned with w.r.t to activating IPv6 on a relay that has IPv6 connectivity only through a Hurricane Electric tunnel? ~ M. On May 12, 2015, at 6:09 PM, Moritz Bartl mor...@torservers.net wrote: Hi! We still have a depressingly low number of relays that support IPv6 (currently only ~120 of ~1900 relays). If your host supports IPv6, please enable it, especially if you run an exit! This has to be done explicitly. https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto In short, you add: ORPort [IPv6::address]:port IPv6Exit 1 ExitPolicy reject6 *:* (or a more open exit policy respectively) Thanks! -- Moritz Bartl https://www.torservers.net/ ___ 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] Tor Consensus Weight Stuck at 20 (Even on Relay with Stable Flag)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Speak Freely: From my experience, this happens only with exit relays. Changing from an exit relay to a guard fixes the problem immediately. I've seen past threads that mentioned deleting your id key would fix the problem, but that never fixed it for me. But that is also counter-intuitive given that going from exit to guard while keeping the same id fixes the problem. If I recall correctly, going back to exit causes the problem to re-appear - I will see if I can confirm that again with one of my guards-that-was-exit. The common theme I keep seeing is that the bwauths need to fix their systems, but beyond that, or which part of their system, I don't know. thanks for that post. please add that (or a pointer to it) also in the trac bug entry. -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVVNQTAAoJEFv7XvVCELh0whcP/Rvdw95CZXxCFVztnmkgzG/4 I4E+NzcxpSirSnFWXrTpP8IHMUGml9y0h/xo0i+SqFN12JbhrmBVHmwXwG0ymQLR JD1fFh+ogQ602GMEilKpY+jVbdP+nbMPmOzuYCdM6/pruotZ9MxTzeYBaScxOUzg fDaWBJFflDw9jI0o1S/AiGKHPL3gehVNkVsihsAtims9pIdItnTLg25EpLSn7D83 fUO+h+Xc2J/9utmVXdD5nxhE6KR3wjcnUDvLofqmQpKj+FY1qdr3VSaRoWA2iI/f fFQR8ot2rui8DZKAMYM3Ss8vL4R5TZyGHkmCPEs6Vm781qSdVEikpmTsJZns/JpF 7B+OHovTtJtIYcl4/wDmVIm6YrstkSVsu9incjrNaOKvUlV7xn2OQGN3CT3cnr2C aPPcUZFM+MapR9d5KbZbUwLajxmWY2KoU/a0LF6tsURKFt2RiJYo56JrrI60HUnP b0GWq+Cflo+vTmiXmt2yXz47wJcp41Zjcxch7YGI7foL0/OaFMN+RIbbEot47LkY 82NBLuc0M5JDwClobv3S7qjySzBbatNwHQwxeOWtc++vuVxWuUNZIuOPRqP1RRH+ SOiEJJnt5hcmSgIsl1bO9cM5ZBZyhIw2eMCU/9tz9KVr0UdQV0SJnwClYzAnMcqD X+ua7Hq2otDd8w/ntqZW =nK8I -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] amount of unmeasured relays continuously rising since 2 weeks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear Tor BW Authories, we'd like to bring the following issue to your attention. Since the last two weeks the amount of unmeasured relays is steadily rising [1]. unmeasured relays on 2015-05-01: 387 unmeasured relays today: 1087 (and growing) Graph showing the last 5 months: https://trac.torproject.org/projects/tor/attachment/ticket/13450/unmeasured_relaycount.png Data: https://trac.torproject.org/projects/tor/attachment/ticket/13450/2015-01-01__2015-05-13_unmeasured_count.csv Would be great if you had some time to look into this: https://trac.torproject.org/projects/tor/ticket/13450 (follow ups should probably go to trac) ..so bw doesn't go wasted. A contributed but unused relay doesn't make relay ops happy. thanks! [1] https://lists.torproject.org/pipermail/tor-relays/2015-May/006946.html -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVVP8PAAoJEFv7XvVCELh03bwP/1NQi99IweePw+o/Mj4nWieE yRLDmTt2J8IeJXp8tMQPcqJIZSEzSOW7u7J9o7McNR+n2lm2Mx9x9IMKQPCX6CFh /v5JJ2/aZyfu7JnkTLr7sNKw6DqkAODnKHbyALuc20zsc1oQmu56VZpY6orwC3RG n4qhbXxyD7+TXCv5iZF5CZsnlrVojHevK6tKkivOem/qMVSwshFHCUSnYVi/YK+R CcLIGllT5fx8msYEWDnnTdIBi9PoIl2gO7SE4Y3TKEpkFhGeU8FEsGmIV9LQi8O1 XcaIeU2BVup4PJMDBSgtB9BlSuKGQAq1ICiVx3OnVUVPleTYsFATFUQxW83irfu9 o8Q3ns3srj3tmtLHE0LA9c2gCuE4NiWA++t72sCc+tiqCy9+X4f5BKsqsem7bT5o 89PfZijjuR4ZI3531e+PCjZDokNY9Gx7lCjIlnrGDeGKSIPqPz9N53bYYIXB+d4r uKDeRaRjv3iz/yKjXFYSra3p70HcQmx+CM4aws035LSCTLg/zFyARXb+hf8/NeKn JzXaVoURRiRX3gzeyiznQ7EVNXTyQmr1ppGJVZAXhtfAuiCrqS5JsPJ8BTzxcylI hZBkcwyQzkV3cCeBFMABQFy3AtQ2SZSOuLzS1vyH1oAHPPWd5K1bgHcSMvOqIEPh LspnH0QSv8ICnU1uhbTZ =rNB9 -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor Consensus Weight Stuck at 20 (Even on Relay with Stable Flag)
A quick update regarding my guard-that-was-exit. This relay, when it was an exit relay, never got past consensus weight of 20. When I changed it to guard, the consensus weight immediately jumped, and bandwidth was finally starting to be used. As usual, it took a few days for full usage, but it did come. Instead of measured bandwidth at 20b/s, it now read 45kb/s. Though arm indicated the average speed was 7-11Mb/s. A few hours ago I switched that relay back to exit, and so far everything looks goodish. The measured bandwidth still says 45Kb/s. I'm now averaging 10.6Mb/s, and have downloaded 16GB and uploaded 17GB since my last email. In arm, I lost my HSDir flag, but I have received Exit flag, and have just over 500 exit connections and 1700 in/out connections. The consensus weight, or anything for that matter, hasn't changed in Atlas yet, but that's not terribly surprising. There were recent changes in how/when Atlas report things now, right? So... perhaps I just found a fix? Err... Workaround. This isn't a fix. I'll take a look at doing this to the other relays to see if this fixes the problem for them as well. Maybe some other people can do the same thing to confirm? 1) Comment out your ExitPolicy accept rules 2) service tor restart 2) Run the relay as a middle/guard until you see in Atlas your consensus weight rises - it should rise within a few hours, but seeing as how your relay isn't working anyway - you can try to wait a day to make sure all those bwauths pick you up. 3) Uncomment your ExitPolicy accept rules 4) service tor restart 5) Report your status back. How exciting! Matt Speak Freely ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] amount of unmeasured relays continuously rising since 2 weeks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Graph showing the last 5 months: https://trac.torproject.org/projects/tor/attachment/ticket/13450/unmeasured_relaycount.png you can also see that the adv. bw. is going down since the beginning of the month: https://metrics.torproject.org/bandwidth.html while the relay count didn't change that much: https://metrics.torproject.org/networksize.html -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVVQDYAAoJEFv7XvVCELh0zDUP/R7t84YE1o9T/RahvrbcZy9H JCSdVzyLqeK3pXZJHUPNn8JDN5S+Yl9W7PMTcs3geeJXEMm12NSZ57OwT6GM1+BA 5L1meDyw2+7m/HpdMCSaGcSpQANCoFuPBC1MWZvuD6tcWPV+6VjG6CarALJMZTxJ lIUEb5GLQkseLl6sHASyuR9PFCdp5tMvMrE4xidn9iTQNIQSgvdwc0MOtkORaCzi zt4Na9h5lQNXrw339AuTukCIweNSYw4H2EcEaEW8DO/u8MT2YFay5DXlItShx1Pz SToVvq11tprENrNwNybVHXFlsSkZ+F8swBlDdjDRl37X0jJym0NSBvkHnoYB92ds 5eK4q90Di/DDhFte1i4aqLUvC5abtQv49JLK+XGK7PMYUTZTv3odGIk8zkd3qTEX KMwI6P+uP4TWYwPsyQCJjBk4kFgNr+A14LFTWMWGyhoiTBo1IZQwvM0t66AU2y5L cputbBDX3eSLEzQRK/8zIJKC+/xGmNatneAokSy+auKFi+X4VBEyKLbGtzHja19J sSjp2CWHs6ZUowewvvV2rtDX+lATUlfUnc8d6bbGbtFM/hL1AvIEjzxAE9Nbujw0 5lQM19CE1ba/4csqh6fNSCTClBPWOWZFBt2GuTNKyIRsZ+KlIAqlwZHYijgZRsGX WzDBtzb+inqhkQXQ5s3S =Gqtz -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] amount of unmeasured relays continuously rising since 2 weeks
On Thu, May 14, 2015 at 08:01:19PM +, nusenu wrote: Dear Tor BW Authories, we'd like to bring the following issue to your attention. Since the last two weeks the amount of unmeasured relays is steadily rising [1]. Hello nusenu, Thanks for the kick. For other statistics, each hour I copy over the votes that moria1 sees: http://freehaven.net/~arma/moria1-v3-status-votes And there's also https://consensus-health.torproject.org/#bwauthstatus It is clear that the bwauth scripts are buggy and need a rewrite. And not just buggy -- I think their design is probably flawed too. I know of several research groups who have been working on better bandwidth estimation schemes, with the main goal of making them more robust to cheating, but with the secondary goal of still being adequately accurate. I had been hoping that one of those would be ready by now, but the research group I've been paying the most attention to has quite a bit of work left to do before they have a cheating-resistance estimation scheme that doesn't open up too many other problems. Another hope we have is Aaron Gibson's upcoming OTF fellowship, which focuses on improving the bwauth system. I think we'll have to find the right balance there between a redesign, which would take a while but could be better for us in the long run, and bugfixes on the current system, which would help things in the short term but take time away from the redesign. I'll call Aaron's attention to this thread too and see if he can provide some insights. --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Please enable IPv6 on your relay!
Hi Michael, From [0]: There is currently no support for running a DIR port on IPv6. Leave any DirPort option as is. HTH, Sharif [0]: https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto -- PGP: 6FB7 ED25 BFCF 3E22 72AE 6E8C 47D4 CE7F 6B9F DF57 signature.asc Description: PGP signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Tor Consensus Weight Stuck at 20 (Even on Relay with Stable Flag)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 In the light of this thread I made an onionoo (- atlas) feature request to display the Unmeasured=1 flag on atlas (eventually). https://trac.torproject.org/projects/tor/ticket/16020 -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJVVHtkAAoJEFv7XvVCELh08fAQALmTAmZW/ckerY3nAWyScKDN msCriBFA8SwIDssy3KM+OPqLgZ7K5nADHvF5NvHIuhcYOZm06OyDWBj5vVhQvGGt uRFYkX+Gm88R6mtjwyVx5hvc/VSgCrY5d3/FqPk44rPmoUUPoZpKkPfo2VIuywhQ 5h48udX5aW7P3pXvTLM9B3HYzBCDfTcARfc+CPqDlysZCQLnbyZM5IW603jGi+oK tDik5RTGV+jTWAP2zdsoL6VrtWlOgVuaxpqBKKr0bn+jRQw2j9j9CgPJXxrMmnV/ xUsWkYdtsOAWSsaOjCO7qAXFCkPdmRV13ux5C8pq+zvJb2cRykyPMGCnWWhdvQxc 4jLC2eM01TolhFcwdo/JfbChl5eikR29c6ziXhi0OzH8a/f5pMtDdd2TqXtLycif s9dCWRq7M0XwynIovV/c4tYpBPwbS2bvW8FoyNeRjSXRtNJ43eJd6Fq8reGf0LFf A6vI3AjAT74+Jeq0dYMgRL3oGuqRY2U2PCr91ei3QcKKcYay30ZO+D47RQ4dxhqf W+61yrxMIWQTPoP09Rm2TvmQeIF6mzqLSS635Mm7iT78H0RDu6Tgto5BDhtUl0Ms SrKCSBw+gxVLePNfIU2tWzwm7ymW2vPYEDTPkFkRrpcOFgE3Dp2+XbavhwUrVK22 DJGP/WrwnVS6oxaJbMCR =t5uM -END PGP SIGNATURE- ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
