how to use chutney for private tor network

How to use chutney for private tor network how to#

Run a test using tor and chutney to find out how fast tor can get on your CPU.Run a test using tor to see how fast tor can get on your network/CPU.If your relay thinks it is slow, or the bandwidth authorities think it is slow, you can test the bandwidth yourself: You need to work out why they measure it slow. If it's the median measured bandwidth, your relay looks slow from a majority of bandwidth authorities.If it's the observed bandwidth, your relay won't ask for more bandwidth until it sees itself getting faster.If it's the bandwidth rate, increase the BandwidthRate/Burst or RelayBandwidthRate/Burst in your torrc.The smallest of these figures is limiting the bandwidth allocated to the relay. Here is some more detail and some examples: Drop in consensus weight and Rampup speed of Exit relay. Then mouse over the bandwidth heading to see the observed bandwidth and relay bandwidth rate. Otherwise, check your relay's observed bandwidth and bandwidth rate (limit). Are there more than 2 relays on its IPv4 address?.Is its IPv4 or IPv6 address unreachable from some networks?.Does it have the wrong IPv4 or IPv6 address?.If your relay is not marked Running by some directory authorities: Check each of the votes for your relay on consensus-health (large page), and check the median.

How to use chutney for private tor network how to#

Here's how to find out which measurement is limiting your relay: Relay bandwidth can be limited by a relay's own observed bandwidth, or by the directory authorities' measured bandwidth. Relays outside North America and Western Europe are usually slower. Relays transiting via Comcast have been slow at times.

Check the Internet peering (bandwidth, latency) from your relay's provider to other relays.

Others can be viewed using top or similar tools.

Check RAM, CPU, and socket/file descriptor usage on your relay.

Other times, it is the network that is slow: the relay has bad peering to most other tor relays, or is a long distance away. Sometimes, a relay is slow because its processor is slow or its connections are limited. Then Tor would be almost as fast as the wider Internet). (We want enough relays to so that each relay is loaded at 10%. This is good for clients: an overloaded relay has high latency. It's normal for most relays to be loaded at 30%-80% of their capacity.

So even if all relay operators set their advertised bandwidth to their localĬonnection speed, we would still need bandwidth authorities to balance the loadīetween different parts of the Internet. So we need to know how well each relay can connect to the entire world. Most providers tell you the maximum speed of your local connection.īut Tor has users all over the world, and our users connect to one or two Guard relays at random. It will have diagnostics for relays that don't get measured, and relays that have low measurements. We're working on a new bandwidth scanner, which is easier to understand and maintain. Tor wants low-latency web pages, which requires fast connections with headroom.īitTorrent wants bulk downloads, which requires using all the bandwidth. It does a reasonable job for most relays.īut Tor's goals are different to protocols like BitTorrent. Tor manages bandwidth across the entire network.