FYI there is an open ticket about this. My relay is also experiencing
this problem.
https://trac.torproject.org/projects/tor/ticket/14763
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/to
ing
ls -l | wc -l
returns 1591, so I'm not hitting the limit of 4096.
In any case, if you know why my limits.conf doesn't appear to have taken
effect, let me know.
I've also added other optimizations from the torservers wiki. My
/etc/sysctl.conf is http://paste.debian.ne
https://www.att.com/shop/u-verse/gigapower.html
In Austin we have Gigapower, "1Gbps" up and down.
I should have mentioned, using speedtest-cli I can measure about 450
down, 100 up.
With AT&T's proprietary "speed test" I can "measure" 1Gbps both directions.
I don't really believe those numbers, bu
After months of trying to figure out where the bottleneck in my relay is
(I'm on gigabit down/up connection, but relay won't push more than
10mbps), I was poking through my NVG589 router's NAT Table and noticed
Total sessions available 2560
Total sessions in use 2048
Followed by a table containin
I too am experiencing a recent and significant drop in bandwidth, and
have previously had problems gaining and losing the guard flag
repeatedly (though not recently).
I wonder if these issues are somehow connected, or if there is some kind
of new attack/exploit that decreases relay consensus to al
