Lately I started to be more careful with blogs happens on the server. I found that I have a blog widely read, with many hits. An obvious example is in the picture below:
1. If IP is blocked from WordPress -> Dashboard traffic reaches the server and there.
2. If a server is 100 blogs ... each one should block the same IP. (Headache)
3. From the same IP can try to look for security is vulnerable points, the other open ports. (I know I said two reasons. Unu`'s bonus)
Another way of an IP block access to a site, is editing the file .htaccessIn folderu root, where there are site files (usually public_html). I used to fantasize like that through June 2007 when I wrote the post "Deny Access to IP Spammer".
Method of blocking IPs. Htaccess, I do not recommend anyone, of one reason: the more loaded file. Htaccess, the loading time of the site grows. If 100 files. Htaccess would have many 50 the Directive on Apache (HTTP Server), you can put two candles candy :)
I think the third method is the best .. IP blockingfixes may level server, all portsUsing iptables.
In the picture above, it is seen IP 184.108.40.206, trying to spam pages from blog. Lock him at the server level is as follows.
root @ server [~] # / Sbin / iptables -I INPUT -s 220.127.116.11 j DROP
root @ server [~] # / Sbin / service iptables save
Saving firewall rules to /etc/sysconfig/ iptables: [OK] root @ server [~] #
whois (ripe.net): 18.104.22.168
inetnum: 22.214.171.124 - 126.96.36.199
Describe: Dragonara Alliance Ltd
Ok. If IP comes from a region where they are sure they do not want visitors per server (either through the web or by mail), I have handy option to block access to two class C (Class C subnet), encompassing all IPs beach between 188.8.131.52 and 184.108.40.206.
/ Sbin / iptables -I INPUT -s 220.127.116.11 / 24 j DROP
/ Sbin / iptables -I INPUT -s 18.104.22.168 / 24 j DROP
/ Sbin / service iptables save
iptables -L, to see the list of IPs "Chain INPUT".