Can anybody else reproduce this? If I start multiple pfcount instances bound to the same cluster id, it seems to cause a kernel panic after a varying amount of time, but always seems to happen. Using pfcount without setting a cluster id seems to work just fine. I'm using the latest version of PF_RING.
./pfcount -i eth1 -c 1 -l 1500 Regards, Will _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
