Hello, > In the case when "ulog2" instead "ulog" in the config - it fails even > sooner. See output below... I noticed that there is no table ulog, but > since it 's written so in sample config file, and there is a view, > named "ulog" in the DB schema - I supposed that should be so. The > "timestamp" row it's failing - passed normally when "ulog" table is > used. I wrote ulogd2_ct and not ulog2 ;) The table argument contains the list of fields that will be needed as INPUT key. In the SQL schema ulog and ulog2 are for packet based logging. The flow based logging table is ulog2_ct. >> Ok, it seems you've pointed to the wrong 'table' option. You should not >> point to ulog but to ulog2_ct. BR, -- Eric Leblond INL : http://www.inl.fr NuFW, Now User Filtering Works (http://www.nufw.org) -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
