break the consistency with sFlow and netflow in
OVS, so I believe it’s not appropriate.
The main feature was the OpenFlow “sample” action. Efforts should concentrate
on that IMHO.
Bests,
Daniel Benli Ye
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Saturday, April 23, 201
s not appropriate.
The main feature was the OpenFlow “sample” action. Efforts should concentrate
on that IMHO.
>
> Bests,
> Daniel Benli Ye
>
> -Original Message-----
> From: Ben Pfaff [mailto:b...@ovn.org]
> Sent: Saturday, April 23, 2016 12:55 AM
> To: Daniel Ye
> Cc: We
,
Daniel Benli Ye
-Original Message-
From: Ben Pfaff [mailto:b...@ovn.org]
Sent: Saturday, April 23, 2016 12:55 AM
To: Daniel Ye
Cc: Wenyu Zhang; dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH v1] Support port level IPFIX
On Tue, Apr 19, 2016 at 03:55:10PM +0800, Daniel Benli Ye wrote:
&g
On Tue, Apr 19, 2016 at 03:55:10PM +0800, Daniel Benli Ye wrote:
> From: Benli Ye
>
> This patch enables port level IPFIX. Before this patch, OVS supported
> per bridge IPFIX and per flow IPFX, and exporting packet tunnel headers
> is only supported by bridge IPFIX. This patch adds port level IPF
From: Benli Ye
This patch enables port level IPFIX. Before this patch, OVS supported
per bridge IPFIX and per flow IPFX, and exporting packet tunnel headers
is only supported by bridge IPFIX. This patch adds port level IPFIX
for easy configuration and port level IPFIX also supports exporting
pack
