Premium WeedHex 636 Posted September 2, 2021 Premium Share Posted September 2, 2021 Hello, I'm a bit hurry but want to suggest you to change a syserr to track better a thing. Fine: input.cpp Quote -sys_err("HANDSHAKE phase does not handle packet %d (fd %d)", bHeader, d->GetSocket()); to +sys_err("HANDSHAKE phase does not handle packet %d (fd %d) (source %s:%u)", bHeader, d->GetSocket(), d->GetHostName(), d->GetPort()); Like this, if this error will get trigger, you know where does it come. On OVH servers they're attempting to handshake from random Russian IP bot that guess my IP + port of cores. 1 6 Link to comment Share on other sites More sharing options...
arlinamid 1139 Posted September 2, 2021 Share Posted September 2, 2021 Another solution for unwanted client acessing to the server. Thanks to @martysama0134 2 1 2 Best regards, Arlinamid Link to comment Share on other sites More sharing options...
Active Member Helia01 2150 Posted September 23, 2021 Active Member Share Posted September 23, 2021 On 9/2/2021 at 6:38 PM, WeedHex said: Hello, I'm a bit hurry but want to suggest you to change a syserr to track better a thing. Fine: input.cpp Like this, if this error will get trigger, you know where does it come. On OVH servers they're attempting to handshake from random Russian IP bot that guess my IP + port of cores. Russian hackers are to blame for everything (nope). On 9/2/2021 at 8:05 PM, arlinamid said: Another solution for unwanted client acessing to the server. Thanks to @martysama0134 This will not help in this situation. Link to comment Share on other sites More sharing options...
Active Member Helia01 2150 Posted September 23, 2021 Active Member Share Posted September 23, 2021 after adding this fix, you can analyze the sysser file by fail2ban + pf 1 Link to comment Share on other sites More sharing options...
Recommended Posts