IP/host filtering in log files?

[senthil sen]

Hello All,

I am trying to find repeated IP hits to the server in the log file or how to find which IP has the highest number of hits to the server or has done the most damaged? This is not only for IP's but also for any host name or any user having the highest entry in the server log?

Thanks,

[Charles Lyons]

You're welcome. Despite the question marks though, there isn't a question here, just a set of statements about what you want to do. So what have you thought about or tried, and what problems have you been having? Then we'll go from there...

[Tim Holloway]

Ah well, I'm not exactly fluent in malayam, tamil or urdu. I think I can see the question in there, even if it doesn't match the question marks.

First, the number of attacks isn't related to the amount of damage done. I have typically 10,000 attempts made on one of my FTP servers every day. So far they have all bounced. But it would take only one successful attack on any IP or port to get my machine owned.

On the Fedora/Red Hat architecture, there's a package called logwatch that will scan your logfiles every day and email a summary of this and other things as well. By default it gets sent to the root account on the local machine, but you can override that and send it to whomever and wherever you prefer.

Here's a small typical excerpt:

Logged 35 packets on interface eth0
  From 58.241.151.74 - 1 packet to tcp(1433)
  From 60.190.223.137 - 2 packets to tcp(4899)
  From 61.138.125.17 - 1 packet to tcp(22)
  From 61.147.115.37 - 1 packet to tcp(2967)
  From 61.158.143.86 - 1 packet to tcp(2967)
  From 64.50.116.178 - 2 packets to tcp(2967)
  From 66.226.30.189 - 1 packet to tcp(1433)
  From 69.197.23.139 - 1 packet to tcp(1334)
  From 72.9.239.250 - 1 packet to tcp(21)
  From 91.193.130.50 - 1 packet to tcp(3389)
  From 93.100.16.90 - 1 packet to tcp(22)
  From 121.11.85.222 - 1 packet to tcp(3389)
  From 122.160.227.165 - 1 packet to tcp(4899)
  From 122.224.34.19 - 1 packet to tcp(1433)
  From 122.224.199.126 - 1 packet to tcp(1433)
  From 125.65.165.139 - 2 packets to tcp(3128)
  From 201.235.146.149 - 1 packet to tcp(22)
  From 202.97.184.174 - 3 packets to tcp(1433)

You can see that after all these years, the SQL Slammer is still alive and well!