I'm sure the OVS project would accept IPFix improvements to export more
fields or metadata, if anyone would like to prepare patches for that.
On Fri, Sep 13, 2019 at 10:41:22PM +0900, Motonori Shindo wrote:
> Rajesh,
>
> OVS supports NetFlow V5 and IPFIX (a.k.a. NetFlow v10). NetFlow V5 as a
>
Thanks for the info Peter
From: Peter Phaal
Sent: Friday, September 13, 2019 7:34:41 PM
To: Rajesh Kumar
Cc: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] OVS - Netflow/IPFix export of custom metadata.
On Sep 13, 2019, at 4:45 AM, Rajesh Kumar
Thanks for the info Shindo
From: Motonori Shindo
Sent: Friday, September 13, 2019 7:11:22 PM
To: Rajesh Kumar
Cc: ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] OVS - Netflow/IPFix export of custom metadata.
Rajesh,
OVS supports NetFlow V5 and IPFIX
> On Sep 13, 2019, at 4:45 AM, Rajesh Kumar
> wrote:
> The inbuilt OVS netflow export feature seems to export the 5 basic info
> present in the packet (src dst mac,src dst IP, port).
> Is there any option to export other data present in a packet.
>
> Without OVS, I was able to do netflow
Rajesh,
OVS supports NetFlow V5 and IPFIX (a.k.a. NetFlow v10). NetFlow V5 as a
protocol can't export information other than the pre-defined information
element such as src/dst IP address, src/dst port number, protocol, nexthop
address, input/output interface, etc. IPFIX, on the other hand, has
Hi,
The inbuilt OVS netflow export feature seems to export the 5 basic info present
in the packet (src dst mac,src dst IP, port).
Is there any option to export other data present in a packet.
Without OVS, I was able to do netflow export using a tool called pmacctd. It
supported exporting
