Hi all,
I made some improvements to the postscreen-stats script. It can now generate
a google map of the locations of the blocked IPs.
I also added the support for the pygeoip python module, fixed a few bugs and
included a patch from Dan Larsson.
Check it out: https://github.com/jvehent/Posts
On 06.11.2011 17:54, Wietse Venema wrote:
Julien Vehent:
Also for this last query, it looks like 65% of the IPs cannot be
linked
to a country (XX = unknown). I'm not very familiar with the way
geo-ip
databases gather their data, is that normal numbers for zombies ?
This is not my experience.
Julien Vehent:
> Also for this last query, it looks like 65% of the IPs cannot be linked
> to a country (XX = unknown). I'm not very familiar with the way geo-ip
> databases gather their data, is that normal numbers for zombies ?
This is not my experience.
A few times a year I do a one-time pu
Julien Vehent:
> I'm also open to suggestions on how to improve the script. I'm no
> python expert, and there are probably tons of interesting information to
> extract from the postscreen logs.
To improve the script, you could count both the totals and per-client
stats. For my own tiny mail serv
Am 05.11.2011 01:12, schrieb Julien Vehent:
There is a script to do the log parsing:
https://github.com/jvehent/Postscreen-Stats
Any short report (without the IPs) would be interesting. If,
additionally, you can calculate the geo-localisation, that would be
great (but querying the database on hos
* Julien Vehent :
> Hi Folks,
>
> Like others before me, I'm curious about how well postscreen
> performs in the real world.
>
> I'm writing an article on Postscreen for the french issue of linux
> magazine. I got the setup part covered fine, but miss some
> statistics on how it runs.
> I have lo
