Peter Haag

@gabrielmocan - no worries - the default remains a single port. As I mentioned, this requires more work to implement. Meanwhile as a workaround, one can startup multiple collectors on...

Up to now, it catches all, what comes along the wire. But a template selector could be implemented.

Yes - true - but it was not meant to create a csv output :) but I will check, if the change does not break other things.

In order to be more flexibel I propose to replace the old csv code with an user defined such as `nfdump -o 'csv:%tsr,%bpp'` It needs some work to implement.

As `go-nfdump` can read nfdump binary files, a custom importer written in Go would be most efficient, I guess.

The master repo is updated with IP spoofing for the packet repeater. It's enabled with option -A. See nfcapd(1) Please check and report back.

Issue closed. Feel free to reopen, if you run into problems.

With the code changes in that latest master repo, you can forward records natively with nfdump protocol 250. Use `nfreplay -v 250 ....` and make sure the receiving end is...

As this is now integrated, I close the ticket.

Not sure if, you made progress on this issue. As far as it concerns nfcapd and the repeater, it sends out the received packet as soon as it received one....