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.
I'm using an Opnsense routing platform, and I've had more than 4,000 simultaneous connections just running torrents, lol.
Am I able to run another tor instance just on different ports on the same IP?
According to file descriptor limit I shouldn't be hitting a socket/file descriptor limit either.
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.
Thanks,
Matt Westfall
President & CIO
ECAN Solutions, Inc.
Everything Computers and Networks
804.592.1672
------ Original Message ------
Sent: 5/30/2019 7:05:20 PM
Subject: Re: [tor-relays] Relay Consensus Low
Hi,
Doesn't ever go up above 8800 or so.
One thing I notice in Nyx is that my connections never go above about 2000 in and out connections.
That's unusual, because there are about 7,000 relays in the network.
How many simultaneous connections does your router support?
(Lots of them claim to support unlimited connections, but only support
a few hundred or a few thousand.)
I have advertised bandwidth of just shy of a gigabit in my config. I understand now that the "advertised bandwidth" is calculated based on observed traffic through the node, which while more reliable and avoids abuse, seems to be counter productive to a degree.
Ultimately what do I need to do to get more traffic through my node? Cause I have a 2Gbps fiber sitting here basically doing nothing so I was giving 1Gbps to tor :)
You could remove all the bandwidth limits, and put them back in when tor is using
more than you want it to. (Tor tries to keep some extra bandwidth to deal with
traffic spikes, so a 1 Gbps limit will get you around 300 kbps sustained traffic.)
Here's a more detailed explanation, and some other things to try:
T
