Hey toer, I actually removed the Bandwidth Rates per another suggestion.
Just sucks I can donate more to the TOR Network, but because other
people abused the advertised bandwidth settings now it is what it is.
https://puu.sh/DAw2V/aeb55530e8.png
Also I guess the fact that most of the traffic across tor is http/https
It's not ever going to "observe" a whole lot because it's quick small
packets of data.
I moved it to another IP and put it on 443 / 80 so maybe that will help
cause firewalls and such. It's also directly on a public wan IP now, so
firewall/router complications.
Config in Nyx: https://puu.sh/DAwXD/39269fba87.png
Chutney Results - https://puu.sh/DAwYD/131f6f1959.png
Ran a 30 MB Test 10 was fast and 100 kept crashing
2nd Run: https://puu.sh/DAx0v/4c73a8b661.png
So looks like my hardware can only handle about 100Mbps Full Duplex, but
that's still way more than 9 :-D
Guess we'll see what happens.
I didn't see if anyone answered if I need a separate IP or if I can
create another tor instance on different ports but on the same IP, to
increase the load I'm handling.
Thanks,
Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672
------ Original Message ------
From: "teor" <t...@riseup.net>
To: tor-relays@lists.torproject.org
Sent: 6/2/2019 1:45:35 AM
Subject: Re: [tor-relays] Relay Consensus Low
Hi,
On 1 Jun 2019, at 14:57, Matt Westfall <mwestf...@ecansol.com> wrote:
Hello thanks for the comments, I might do that, remove the limits, because
it's self limiting by the 1 Gbps network port, so it can't use more than that
anyway.
Following the instructions here:
https://trac.torproject.org/projects/tor/wiki/doc/MyRelayIsSlow#TorNetworkLimits
It looks like your relay is limited by its own observed bandwidth.
(The observed bandwidth that your relay has seen itself using.)
So increasing the RelayBandwidthRate would be a good idea.
If your relay's observed bandwidth gets above 9 megabytes a second, your
relay will be limited by the bandwidth authorities' measurements. (The
median measurement for your relay is 8910 scaled kilobytes per second.)
https://consensus-health.torproject.org/consensus-health-2019-06-02-04-00.html#B1B10104EB72A1FBBF6687B05F1915D87D00DBDE
There might not be much you can do about this: Comcast has slow peering
with a large number of internet networks. And it looks like 4/6 of tor's
current bandwidth authorities are on those networks.
This isn't something Tor can fix: we can only measure the bandwidth that
Comcast is giving you. If Comcast has slow peering to US East and Europe,
then clients using your relay will be slow.
I tried to run chutney tests to see what hardware supports but haven't quite
figured out what the command line I should be using is.
Any help with that would be appreciated.
You're right, the README is more confusing than it needs to be.
Try:
./chutney/tools/test-network.sh --data $[10*1024*1024]
If a 10 MB transfer is too fast, try 100 MB.
I opened this ticket for us to fix our documentation:
https://trac.torproject.org/projects/tor/ticket/30720
T
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
