Another abuser blocked
Found just this evening that from a range of addresses starting with 78.138.116, had 15 concurrent sessions open on this blog, causing the system to page heavily. So I blocked the network (78.138.116.0/23) in the router, restarted WASD. Within seconds, the same happened from address 78.138.117.* – so it seems blocking didn’t exactly work.
But scanning the WASD documentation, I ran into the [reject] section in the configuration. Now these netwrks are now both denied access to the web; either by the router, or if they get trough, by WAD itself.
Quite som other sites will be handled similarly.
What goes on behind the doors of the (private) data center