nusenu:
To stop confusing operators it would make sense to remove the
"This relay is overloaded since"
banner from Relay Search for all tor versions prior to
0.4.6.9 and 0.4.7.3-alpha, no?
Well, not all potential overload is DNS related overload. There are a
bunch of different criteria for
These responses were automatic. We didn't mention anything about
video call.
We understand we maybe emailed to a wrong address regarding our issue but
why are you purposely making things more complicated for us?
Please tell us where we can ask about our issue? Should we open a new issue
on Github?
> however I have now noticed a number of malicious login attempts
Using a non standard ssh port and blocking power 22 should reduce the bot login
attempts.
(If you’re running a VPS be sure to test your custom port before blocking 22)
I don’t see a relationship between IPv6 and login attempts tho
Roger,
For completeness, I should amend point #3 to include configuring the
Loadbalancer's Timeout to a Large Value:
3. Loadbalance using IP Transparency Mode (This was discovered while tirelessly
combing through mountains of Tor debug logs), use Sticky Sessions based on
Source IP Addresses, and
Georg Koppen:
Well, not all potential overload is DNS related overload. There are a
bunch of different criteria for emitting a general overload warning.
Onionoo and this relay search have a hard time differentiating
between DNS related (general) overload and other (general) overload.
Thus, I do
