On Tue, 21 Sep 2010, Pablo Neira Ayuso wrote: > On 21/09/10 11:26, Jan Engelhardt wrote: > > On Tuesday 2010-09-21 04:25, Italo Valcy wrote: > > > >> Actually, I wanna something more simple and specific than the command > >> above. Using 'conntrack -E', I still have to parse the package events > >> NEW, UPDATE and DESTROY if I wanna know the of a NAT > > > > So use `conntrack -Ee NEW` to limit the output :) > > If that is still too much overhead, I'm sure you can directly use > > libnetfilter_conntrack's library interface to get at these events. > > You can refine this a bit more with: > > `conntrack -Ee NEW --any-nat' Yes, but it's strange to use 'conntrack' for logging. Isn't it simpler to use ulogd2 and the ulogd_inpflow plugin? Best regards, Jozsef - E-mail : kadlec@xxxxxxxxxxxxxxxxx, kadlec@xxxxxxxxxxxx PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt Address : KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
