Closed acherla closed 1 year ago
It's supported.
You have to open a socket for it -listen nfl://...
@lspgn Per the config it already defaults to sflow://:6343,netflow://:2055 . Which means the container should already be opening a socket to both, we are routing the traffic to 2055, but the above error still shows up. It does properly parse v9 and v10 traffic, but fails to parse v5. This is because the current parser doesnt even contain a decoder for v5
edit: Looks like i found the legacy decoder
Yes I agree this could be improved by sharing the socket associated with NetFlow. This dedicates one socket for template-based messages.
I assume this was answered. Closing.
Any plans to support Netflow v5 for goflow2? We are receiving errors in the goflow2 adapter when attempting to deserialize netflow v5 traffic using the latest build of goflow2.