You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to report an issue that I encountered. I am using flowd from mindrot.org to send the netflow data to my python script.
Unfortunately the Netflow implementation is not getting the template.
I checked the packets that are send by flowd and sometimes it send the information containing the template but the netflow implementation doesn't handle it. For reference I included the output and the template that is send by flowid 0.
Your script is probably missing a way to store received templates, as your output says: NetFlow v9 packet detected, but no templates dict was passed! For correct parsing of packets with templates, create a 'templates' dict and pass it into the 'parse_packet' function.
This is a bit confusing at first, but you can use the reference collector as an example:
# templates is passed as reference, updated in V9ExportPacket
export=parse_packet(pkt.data, templates)
You therefore need a dict templates = {"netflow": {}, "ipfix": {}} and then pass this dict into the parse_packet function, parse_packet(pkt.data, templates). That way your received templates can be used across multiple incoming streams from flowd.
Hi,
I wanted to report an issue that I encountered. I am using flowd from mindrot.org to send the netflow data to my python script.
Unfortunately the Netflow implementation is not getting the template.
I checked the packets that are send by flowd and sometimes it send the information containing the template but the netflow implementation doesn't handle it. For reference I included the output and the template that is send by flowid 0.
The rest is send by flowid = 256.
I wanted to define the template manually but I don't know how I could do it.
If someone has an idea on how to fix it. Please let me know.
Thank you in advance
Mike
The text was updated successfully, but these errors were encountered: