-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README.md bug and question regarding sending unirec data as IPFIX over UDP #81
Comments
Hi, why do you want to use unirec and not ipfix output plugin? Regarding to your issue: Let me explain the unirec output plugin parameters:
Thus I suppose, your desired arguments were: Karel |
Hi Karel,
to use both idpcontent and smtp plugins and "convert" ens192 traffic to IPFIX format and send to ${REMOTE_IP} and ${REMOTE_PORT}. Is that correct? Thanks, |
Hi Michal, Karel |
Hi Karel, Thanks, |
Based on feedback from #81, it was not very clear what is the output of ipfixprobe when some output plugin is used. The aim of this patch is to make the readme file more general - if a user enables some processing plugin (by `-p`), there are extended fields included in the output flow records. It works for `unirec`, `ipfix`, or `text` plugins.
Hello,
I've been trying to send the unirec data to the UDP netflow output and I tried to investigate the code but unfortunately I cannot find the way. Please let me explain the scenario I would like to do:
How could I do that? I have tried the following syntax but it does not work:
ipfixprobe -i 'raw;ifc=ens192' -p http -p idpcontent -p smtp -o 'unirec;i=b:,u:http:timeout=WAIT;p=http,(pstats,phists,idpcontent)'
I don't know how to define the output how to send unirec data using ipfix. Could you please help me?
Also, I am seeing a probable bug in the README.md. There's line:
However there is no definition to send IPFIX data to 127.0.0.1:4739 over the TCP connection so I guess the comment is misleading. Could you please clarify whether am I reading/understanding it wrong?
Thanks a lot,
Michal
The text was updated successfully, but these errors were encountered: