|
From: Daniel T. <ta...@fu...> - 2004-05-13 00:19:15
|
Hello I have attached a diff which adds ulog support to iptables_logger. It expects to find a standard ulog table (see mysql.table that comes with ulogd) in the database specified in the config file. To activate it, un comment the "table_schema" variable in the config file. It doesn't handle the ignore_ports options at all. Since ulog doesn't resolve hosts and uses protocol numbers, instead of names, I added host_cache and protos tables. The host_cache table is just a DNS cache and the protos table is similar to the ports table. ulog also does not provide a hostname for the firewall, so I added a default_host_value option in the config file. ulog doesn't log which chain the entry came from. Instead, it allows you to specify a prefix for the rule. I think this is far more useful anyway, so I mapped it to the chain column. I broke out the admin page and added an option to resolve ip addresses. It should be fairly easy to use. If you run the app on a linux machine, the "host" command should be available. It is much faster than the php "gethostbyaddr" command. To use this command instead of gethostbyaddr, uncomment the "host_resolution" variable in the config file. Note that if you run php in safe mode, you will get a warning about using an external program. If the program isn't located at '/usr/bin/host', you'll need to change utils/resolver_host.php. I hope this is useful... Dan |