Michal Sedlak

What you can currently do is store the data in the Nffile format and then use a tool like Nfdump to read the data as CSV. There's a problem that...

> Thanks to these patches (mostly) I built it on FreeBSD. Unfortunately, it looks like linking went wrong or something or some includes are missing since for all the plugins...

> > Regarding the issue you mentioned, I so far haven't managed to try building IPFIXcol2 on FreeBSD myself to replicate and investigate the problem, but I would try building...

> It's significant progress. If it will be able to use UDP transport then we can do more tests, without UDP working it's not easy to feed it. Finally, if...

> > I didn't get further than that so far, but getting the value the BSD way or replacing the value with a constant might be all that's needed to...

Yeah, I'm planning to get this merged into master, I just want to go through all the changes and make sure everything is done properly, as some of the changes...

> Hi, we ran into the same issue. We have the firewalld process disabled. We also have ipfixcol running on the same server. ipfixcol listening l4 port 4444 is working...

> Yes, we did confirm by bringing up ipfixcol with port 4445. We saw that it is receiving and writing data. So, I can confirm that the port is accessible....

Is your issue just seeing the message "The instance holds information about 0 active session(s)." itself? That does not necessarily indicate any error, it's just an information that there are...

> Let me rephrase our problem. > > We have both ipfixcol and ipfixcol2 running on the same machine. ipfixcol has startup.xml file listening to port 4444 and ipfixcol2 configured...