On Sun, Jul 26, 2015 at 09:57:04PM +0300, Vadim Kochan wrote: > On Sun, Jul 26, 2015 at 08:39:04PM +0200, Daniel Borkmann wrote: > > On 07/25/2015 06:09 PM, Vadim Kochan wrote: > > >From: Vadim Kochan <[email protected]> > > > > > >Seems it was caused by specifying all netfilter groups > > >when flushing connections. > > > > > >Used separated nfct instance w/o netfilter groups to > > >flush ipv4/ipv6 connections. > > > > > >More info can be fetched from the issue item on github: > > > > > > https://github.com/netsniff-ng/netsniff-ng/issues/145 > > > > > >Signed-off-by: Vadim Kochan <[email protected]> > > > > Applied, thanks. > > BTW is it really needs to flush connections ? > Because counters will be cleared too, and they will not reflect > the real data flow through the connection ? > > Regards,
Seems I understand, this is for catch existing connections through the event-driven way, but I assume it will be possible too if dump everything once to save the counters, and then do a polling. -- You received this message because you are subscribed to the Google Groups "netsniff-ng" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
