to:b...@ovn.org]
Sent: Tuesday, July 05, 2016 7:43 AM
To: Daniel Ye
Cc: Ben Pfaff ; Justin Pettit ; Wenyu
Zhang ; Wang Qiong ; dev@openvswitch.org
Subject: Re: [ovs-dev] [PATCH v2] ipfix: Add ingress and egress interface in
exporting flows
The odp_ports aren't meaningful at all outside of O
The odp_ports aren't meaningful at all outside of OVS, so they're almost
worthless. How do you intend for the receiver to interpret them?
If the IPFIX record doesn't otherwise say what bridge the ofp_ports
correspond to, then I suggest adding some way to identify the bridge;
for example, you coul
Hi Ben,
Thanks for review. In my opinion, the ofp_port may be the same on different
bridge. If so, we still don’t differentiate the flows
in this scenario. That’s why I choose to use odd_port.
Bests,
Daniel
> On Jul 5, 2016, at 5:22 AM, Ben Pfaff wrote:
>
> On Thu, Jun 30, 2016 at 08:48:43PM -
On Thu, Jun 30, 2016 at 08:48:43PM -0700, Daniel Benli Ye wrote:
> In virtual evironment, IPFIX is unable to differentiate flows
> between pair of VMs on different virtual network if their IP/mac
> are same.
>
> Network:
> VM1 < VNI1 > VM3
> VM2 < VNI2 > VM4
>
> In ter
In virtual evironment, IPFIX is unable to differentiate flows
between pair of VMs on different virtual network if their IP/mac
are same.
Network:
VM1 < VNI1 > VM3
VM2 < VNI2 > VM4
In terms of IP/mac:
VM1 == VM2
VM3 == VM4
Send 10 packets each from VM1
