ConfigServer Community Forum

Ah, you're right, my apologies. Sleep deprivation. This arrived right after a "blocked with too many connections" email generated by CSF. I'm on my wits' end here

As I'm still pondering (in another thread) why csf won't block an IP at all and actually miscategorizes it as IPV6, here's another email sent that appears to have issues identifying the IPs in question: Banned the following ip addresses on Tue May 20 13:09:01 EDT 2014 2400 with 266 connections That ...

Here's a good primer on IP range blocks: https://www.mediawiki.org/wiki/Help:Range_blocks

For your IP example, 115.238.236.0/24 would block 256 addresses, ending from 0 to 255.

So the question is, is CSF fooled into reporting an IP that cannot be blocked? Is it a glitch (since that IP isn't even IPV6 to begin with) ?

Ok. First off, IPV6 is disabled in WHM/CPanel.

Second, the CSF setting is already IPV6 = 0

I have not changed any of the default configuration regarding IPV6.

No, the VPS is on a ipv4.

I'm stumped as the 19.245.64.24 is blocked at Cloudflare level also. Looks like a mistranslation of the real IP by CSF?

Any help is appreciated.

Hi Sergio, I understand that's not an IP6 but I pasted the line verbatim, removing my server's IP. Here's some more of the email(s) - I trimmed the process list and changed the username. Time: Fri May 16 09:41:13 2014 -0400 PID: 19289 (Parent PID:17399) Account: USERNAME Uptime: 55 seconds Executabl...

Hello, I am frustrated, hence the choice of a username. :( Getting port-flooded daily, at times that I am supposed to be catching some ZZZ's. Once the portflooding begins, this IP appears in the email notifications, of which there are plenty: tcp6: 19.245.64.24:50654 -> [my VPS IP]:80 The port numbe...