cosmostaylor

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 properly...

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.

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 to listen 4445....

Thank you. Could you please specify which files you request? Only the startup.xml files?

I attached the files. We are running on Red Hat Enterprise Linux Server release 7.9 (Maipo). [startup_ipfixcol.txt](https://github.com/CESNET/ipfixcol2/files/15390209/startup_ipfixcol.txt) [startup_ipfixcol2.txt](https://github.com/CESNET/ipfixcol2/files/15390212/startup_ipfixcol2.txt) Note: We did try localIPAddress empty and with the NIC IP as...

Hi again, Any ideas? Thanks in advance.

Hi Michal, Thank you. What we did is we tried ipfixsend2 with tcp (collector running tcp:4445) and udp(collector running udp:4445). The results are: tcp input -> success (The instance holds...

We tried the suggestion but unfortunately the result is the same. Yes, we also think that the problem is with the UDP. That is why we checked the libraries etc....

Maybe a dumb question but, is it possible that the udp library coming with ipfixcol2 is problematic so that it binds to the socket but can not listen/poll packets from...

Thanks for the comments Michal we will keep digging. In order for us to understand deeper and troubleshoot, under what conditions we receive "The instance holds information about 0 active...