I would just use the fail2ban package. Then, sit back and watch the frustration building up on the other side.<br><br>One time there was a kid from Pakistan. I watched him tried 6 times, got banned for 20 minutes, came back and tried again and again. I could image him sitting in front of the computer, running a script for 12-16 hours straight, went to sleep and tried again the next day. After 3 days, he did not come back.<br>
<br>Bao<br><br><div class="gmail_quote">On Mon, Jan 12, 2009 at 5:50 PM, John E. Kreznar <span dir="ltr"><<a href="mailto:jek@ininx.com">jek@ininx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
"Emerson, Tom \(*IC\)" <<a href="mailto:Tom.Emerson@wbconsultant.com">Tom.Emerson@wbconsultant.com</a>> writes:<br>
<br>
> 3) generate, in real time, an e-mail report of the breakin attempt --<br>
> one e-mail per attempt :)<br>
<br>
Another thing you can do is launch an nmap scan against the offending<br>
address. This has often enough led to prompt cessation of the attack<br>
that I think it's actually sometimes noticed on the other end in real<br>
time.<br>
<br>
- --<br>
John E. Kreznar <a href="mailto:jek@ininx.com">jek@ininx.com</a> 9F1148454619A5F08550 705961A47CC541AFEF13<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.6 (GNU/Linux)<br>
Comment: Processed by Mailcrypt 3.5.8+ <<a href="http://mailcrypt.sourceforge.net/" target="_blank">http://mailcrypt.sourceforge.net/</a>><br>
<br>
iD8DBQFJa/NnYaR8xUGv7xMRAhJ5AJ9xPKzW3kQakRcTpFPOqcajAjNTPgCeMop6<br>
yUVoPiqavO2LRrYdUb5DVic=<br>
=gCzM<br>
-----END PGP SIGNATURE-----<br>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>Best Regards.<br>Bao C. Ha<br>Hacom OpenBrick Distributor USA <a href="http://www.hacom.net">http://www.hacom.net</a><br>voice: (714) 564-9932<br>8D66 6672 7A9B 6879 85CD 42E0 9F6C 7908 ED95 6B38<br>
<br>