Paul wrote: Pony99CA wrote:
Paul wrote:Class B and Class C type network are old terms, and not really in use anymore. They are assigned via a subnetwork now (/8, /16, /24 etc).
That's irrelevant to what I said. Blocking a.b.*.* blocks an entire Class B network. Blocking a.b.c.* blocks an entire Class C network.
The point is that such blocking can span companies, ISPs and probably even countries. Or are you saying that's incorrect?
You actually know what a class A/B/C network is? Looks like you dont: http://en.wikipedia.org/wiki/Classful_network
IPs are not assigned anymore via a A, B or C, as that is (And was, and thats the problem now) way too much IP expensive. ISPs gets smaller ranges, that they actually can say that they really need.
You're right. To be precise, I should have said the equivalent
of a Class B or C network. I know that they don't tend to assign those any longer, but I should have known that sloppy word choice would lead into off-topic terminology nitpicking.
But the point is still that blocking an entire octet (or two octets) is possibly blocking more people than you intend, possibly even in different countries.
For example, here's a guest (likely a spammer) on my site:
Guest IP: 18.104.22.168 » Whois
Opera/9.0 (Windows NT 5.1; U; en)
Here's his WHOIS IP address range: 22.214.171.124 - 126.96.36.199. This IP range happens to be in Russia.
Blocking 91.201.66.* would be OK in this case because it would only ban people from that IP range in Russia.
However, if somebody gets a spammer from 188.8.131.52 (for example), they may decide to block 91.201.*.*. Unfortunately, that's not all in Russia. In this case, 184.108.40.206 - 220.127.116.11 is actually in Sweden, and 18.104.22.168 - 22.214.171.124 is in Germany.
So you have to more precise than using * blocking in many cases. That's the point that I was trying to make.