-
Notifications
You must be signed in to change notification settings - Fork 176
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
Openvswitch ovs-vsctl connection #99
Comments
Hello, |
Hello lspgn, Attached is a pcap sample. I can see the IPFIX flows in wireshark, but nothing is appearing in goflow. Thanks for your help. |
Could you give me the CLI arguments you are passing? |
After looking at the pcap, I noticed there are custom Enterprise fields in the templates. Unfortunately, this is issue #31 and the templates aren't properly decoded. I am currently working on a fix and hope to have something in the coming days (after some freeze). |
Gotcha! thanks for the help. I will just use NetFlow v9 for now. I will keep an eye on issue #31 for the future. |
FWIW here's a descriptive XML from ovs: https://github.com/openvswitch/ovs/blob/master/ofproto/ipfix.xml
|
I could make it work "partially" with ovs, standard fields are now recognized and collected ; there's not only the enterprise number parsing missing, but also variable length fields [1] such as string that are not supported currently in goflow. I can submit a fix after cleaning my work. [1] cf https://datatracker.ietf.org/doc/html/rfc7011#section-7 |
…int in existing netflow test - Existing netflow export test now supports netflow_v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv4 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99)
…int in existing netflow test - Existing netflow export test now supports netflow_v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv4 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
…int in existing netflow test - Existing netflow export test now supports netflow v5, ipfix, sflow. - The original test only validated the export of netflow v5 (legacy netflow) data, which does not support IPv6 by design. In order to validate flow data export in an IPv6 cluster, we can now choose between IPFIX and sflow; also, the test now supports an IPv6 endpoint; - For the time being we're only testing netflow v5 in IPv4 (as before) and sflow in IPv6, because: (1) The test itself is long (~5 minutes); (2) The current implementation of the flow collector container (cloudfare/goflow) doesn't support IPFIX data generated by OVS (cloudflare/goflow#99) Signed-off-by: Riccardo Ravaioli <[email protected]>
Hello everyone,
I would like to ask if anyone was able to use the openvswitch IPFIX with goflow.
I tried openvswitch/goflow with sFlow and NetFlow, and both work great. With IPFIX, nothing is shown on the collector.
Has anyone experienced the same issue?
Thanks.
The text was updated successfully, but these errors were encountered: