On Mon, Nov 28, 2016 at 04:47:30PM +0100, Simon Horman wrote:
> On Sat, Nov 26, 2016 at 01:36:00PM -0800, Ben Pfaff wrote:
> > On Fri, Nov 25, 2016 at 03:46:55PM +0100, Simon Horman wrote:
> > > Hi Ben,
> > >
> > > On Wed, Nov 23, 2016 at 11:18:14PM -0800, Ben Pfaff wrote:
> > > > Before Open vSwi
On Sat, Nov 26, 2016 at 01:36:00PM -0800, Ben Pfaff wrote:
> On Fri, Nov 25, 2016 at 03:46:55PM +0100, Simon Horman wrote:
> > Hi Ben,
> >
> > On Wed, Nov 23, 2016 at 11:18:14PM -0800, Ben Pfaff wrote:
> > > Before Open vSwitch 2.5.90, IPFIX reports from Open vSwitch didn't include
> > > whether t
On Fri, Nov 25, 2016 at 03:46:55PM +0100, Simon Horman wrote:
> Hi Ben,
>
> On Wed, Nov 23, 2016 at 11:18:14PM -0800, Ben Pfaff wrote:
> > Before Open vSwitch 2.5.90, IPFIX reports from Open vSwitch didn't include
> > whether the packet was ingressing or egressing the switch. Starting in
> > OVS
Hi Ben,
On Wed, Nov 23, 2016 at 11:18:14PM -0800, Ben Pfaff wrote:
> Before Open vSwitch 2.5.90, IPFIX reports from Open vSwitch didn't include
> whether the packet was ingressing or egressing the switch. Starting in
> OVS 2.5.90, this information was available but only accurate if the action
> i
Before Open vSwitch 2.5.90, IPFIX reports from Open vSwitch didn't include
whether the packet was ingressing or egressing the switch. Starting in
OVS 2.5.90, this information was available but only accurate if the action
included a port number that indicated a tunnel. Conflating these two does
no
