Removing the netblocks from my server firewall corrects this issue.

I’m hoping to keep many netblocks and am reviewing for false positives.

Can you provide what IP Addresses are used for the Location service on Live Traffic?

(1) the problem with .htaccess based filtering of the bad guys it is that
every.
single.
line.
you.
add.
slows.
your.
site.
down.
.. which is why it is often better to block a whole IP range instead of individual offenders.

(2) if you identify a serial offender provider like OVH and start to dig out their RIPE allocations you discover that they have scattered their allocations over more than 1950 entries which makes filtering them hard until you rework that mess back into something more practical like CIDRs. Unless, of course, you like having a slow site..

In general, you can pretty much exclude any major hoster without any impact on true site vistors, because they’re humans, not hosted computers, but to do that efficiently without immediately bumping into issue (1) as above is using CIDR notation. The .htaccess file supports it.

Please consider adding a CIDR input.

I saw a post from about two years ago and at that stage you did not support the format but were planning on to implement it.

122.248.245.244/32 O.K
54.217.201.243/32 O.K
54.232.116.4/32 (Faild with msg. IP is in the list)
192.0.80.0/20 O.K
192.0.96.0/20 O.K
192.0.112.0/20 O.K
195.234.108.0/22 O.K
192.0.96.202/32 (Faild with msg. IP is in the list)
192.0.98.138/32 (Faild with msg. IP is in the list)
192.0.102.71/32 (Faild with msg. IP is in the list)
192.0.102.95/32 O.K

Example 1: 195.47.89.*
Example 2: 195.47.*.*
Example 3: 195.*.*.*

Since not all blocked IPs fit Class A, B, or C IP ranges, but rather CIDR subnets of the aforementioned, this functionality would be most kindly appreciated.

Please advise.

Thanks, kindly

NovaNumismatics Admin

$cidr_array_no = array(
'xxx.xxx.xxx/16',
'xxx.xxx.xxx/17',
'xxx.xxx.xxx/11',
'xxx.xxx.xxx/14',
'xxx.xxx.xxx/13',
'xxx.xxx.xxx/22',
'xxx.xxx.xxx/24'
);
// Loop through the array:
foreach ( $cidr_array_no as $cidr ) {
   // Check IP vs CIDR:
   if ( ipCIDRCheck( $_SERVER['REMOTE_ADDR'], $cidr ) ) {
      // IP matches, block it:
      return 'BLOCK';
   }
}

Can you check it please?

I have a number of entries in my blacklist that are of the type 123.123.*.* (yes, in some cases I have taken to blocking full class B ranges, but I digress).

Three issues:

1 – I still see IP addresses in that range arrive in the firewall 404 listing, which suggests that the wildcards may not actually work
2 – The format above is as per plugin help, but can I also use the CIDR notations such as 123.123.0.0/16? This is what is normally used in network environments.
3 – is there a way to make AIOWPS pick up a range when it flags an IP address as blacklisted in the 404 list? So, would it be possible to flag that 123.123.1.2 (to use the above example) is indeed blacklisted?

Cheers!

Blacklist of extra IP addresses prior to country code
190.244.,93.100.,112.209.,100.43.,178.65.,66.86.,163.172.,100.43.,66.102.,174.34,175.45,173.212,173.234,151.80,77.88,180.76,188.163.,5.9.,69.30.,175.45.

regards
max