Re: [tor-relays] obfsbridge operators: git master enables client statistics!
George Kadianakis desnac...@riseup.net writes: Greetings obfsbridge operators, tl;dr, you might want to upgrade your tor to the latest git master. Trac tickets #4773 and #5040 have been merged to tor's git repository. This means that if you run the current git master, your obfsbridge will produce interesting statistics. Oops, I forgot to mention that you will also need to add the following line in your bridge's torrc: ExtORPort 6669 (or any other port value instead of 6669) This should start an Extended ORPort listener on 127.0.0.1:6669 that obfsproxy will use. Specifically, your bridge will count the number of its unique users like normal bridges do (but because of some complications it was not so easy for obfsbridges). It will also count the number of users per transport. Your bridge will then send these statistics to the bridge authority, and they will be published in metrics.torproject.org so that we can easily track the deployment of pluggable transports. You can experience the stats yourself by peaking at $DataDirectory/stats/bridge-stats. BTW, make sure that you are using the latest obfsproxy written in Python, and not the obsolete obfsproxy written in C. Cheers! ___ 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] MaxAdvertisedBandwidth, MaxOnionQueue and so on
Hi, currently trying to set up a bog standard relay node that's supposed to generate about 20TB/month of outgoing traffic. I've thus set RelayBandwidthRate 7500 KB RelayBandwidthBurst 2 KB but keep getting tons of these Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. Questions: - Is this log message still accurate? I've seen from e.g. ticket 9005 that apparently circuit creation is anyway already handled in parallel, and my machine is definitely not constantly overloaded on all 8 threads. - The node also crashes far too often, i.e. multiple times a week. Annoyingly, I can't seem to get core dumps for these crashes even though I've verified that the core ulimit is set to unlimited, but still the crashes themselves or a kill -SEGV $TORPID do not give me core files. Any ideas? I've also verified that the cwd is /var/lib/tor and that /var/lib/tor is writable :( - I've also set MaxOnionQueue 250, but that didn't change much. Any other suggestions? ciao, -- [*Thomas Themel*] I just want an EDitor!! Not a viitor. Not a emacsitor. [Albulastrasse 52] Those aren't even WORDS ED! ED! ED IS THE STANDARD!!! [ CH-8048 Zürich ] [*+41 78 9070988*] Paul J. LoPresti in 1991jul11.031731.9...@athena.mit.edu ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] MaxAdvertisedBandwidth, MaxOnionQueue and so on
On Wed, 04 Sep 2013 13:00:02 +0200 Thomas Themel tho...@themel.com wrote: - The node also crashes far too often, i.e. multiple times a week. Annoyingly, I can't seem to get core dumps for these crashes even though I've verified that the core ulimit is set to unlimited, but still the crashes themselves or a kill -SEGV $TORPID do not give me core files. Any ideas? I've also verified that the cwd is /var/lib/tor and that /var/lib/tor is writable :( How much RAM do you have available there? Do you have any swap space? -- With respect, Roman 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] MaxAdvertisedBandwidth, MaxOnionQueue and so on
Hi Thomas, Thank you for running a relay! On 09/04/2013 01:00 PM, Thomas Themel wrote: Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. Right now, Tor sees a lot of circuit creation requests due to what most people think is a botnet that is using Tor. The second issue is that Tor does not scale well across multiple CPU cores yet. Looks like, either way, you are hitting the limit of your CPU core. - I've also set MaxOnionQueue 250, but that didn't change much. Any other suggestions? MaxOnionQueue should not be necessary or helpful to set in modern Tor releases. If you see a maxed out CPU core, what you might want to try is run multiple Tor processes in parallel. We do that, although usually for modern CPUs this is only necessary at and above roughly 100 Mbit/s. https://www.torservers.net/wiki/setup/server#multiple_tor_processes -- 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
Re: [tor-relays] Patch
Niels Hesse: Please excuse my ignorance. I saw the mention of a patch in the recent tor blog post. https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94-september-4th-2013 How does one apply that? If you don't know already, it's probably better to simply wait a little bit. Everyone is working hard at this very moment to ready some useful code to mitigate the issues we are seeing. Expect a release soon. Otherwise, it means using Git to retrieve the right branch, and manually build tor. But kittens might get hurt until the code is ironed out. -- Lunar lu...@torproject.org signature.asc Description: Digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Patch
On Wed, Sep 04, 2013 at 10:57:24PM +0200, Niels Hesse wrote: Oh, okay. Thank you for your answer. I really hope this will be resolved somehow. Keep an eye on https://trac.torproject.org/projects/tor/ticket/9657 if you want to follow along. --Roger ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Patch
Oh, okay. Thank you for your answer. I really hope this will be resolved somehow. 2013/9/4 Lunar lu...@torproject.org: Niels Hesse: Please excuse my ignorance. I saw the mention of a patch in the recent tor blog post. https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94-september-4th-2013 How does one apply that? If you don't know already, it's probably better to simply wait a little bit. Everyone is working hard at this very moment to ready some useful code to mitigate the issues we are seeing. Expect a release soon. Otherwise, it means using Git to retrieve the right branch, and manually build tor. But kittens might get hurt until the code is ironed out. -- Lunar lu...@torproject.org ___ 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
