The php firewall is blocking thees ip ranges for spam. Thats ok, but where is the source for this information?
$ip_array = array('24', '186', '189', '190', '200', '201', '202', '209', '212', '213', '217', '222' );
And why is this ip ranges blocked:
$ip_array = array('0', '1', '2', '5', '10', '14', '23', '27', '31', '36', '37', '39', '42', '46', '49', '50', '100', '101', '102', '103', '104', '105', '106', '107', '114', '172', '176', '177', '179', '181', '185', '223', '224' ); //'192',
I had to comment out 192 as i connect to my site locally.
And lastly why is this blocked:
ovh, kimsufi, dedibox, digicube ?
I am sure there is a good reason for blocking this ranges and isp's. What I am more interested in, is where the developer got this black list.
-
This question is impossible to answer. How is
$ip_arraybeing decoded?24is not an IP address. Is that part of an address? Or is it blocking24.x.x.xand186.x.x.xetc? If so that's blocking over 17% of the entire internet.And as for
ovh, kimsufi, dedibox, digicube- that's totally out of context so we can't answer why they're blocked because we don't know what it's blocking. Hostnames? User-Agents? Domains?I agree with Joe's comment - this script is not doing anything useful and is just giving you a false sense of security whilst blocking 17% of the internet.
OK to be fair it's more like 15.5% becuase
10.x.x.x,5.x.x.xaren't used in the wild and only part of172.x.x.xis on the internet. And if that's the case, why not block169.254.x.xwhile you're at it? It's also a bit rude to block 172 and 192 as well because parts of these ranges are internet-routable. All the more proof that this script isn't worth the time it took me to answer this questionFrom Farseeker
0 comments:
Post a Comment