Re: [ovs-dev] ovn: SFC Patch V3

2017-06-08 Thread Mickey Spiegel
egress of the port-pair was configured >> as the ingress eth.) Any other scenarios that come to mind ? >> > > I cannot think of a good reason why a packet would end up on the egress > pipeline on HV1 with outport == 1. > After thinking about it more, I think it is OK if flags.loopback i

Re: [ovs-dev] ovn: SFC Patch V3

2017-05-10 Thread Mickey Spiegel
K if flags.loopback is left as 0. If this case is ever triggered and the second time around through the ingress pipeline still sets outport = 1, then the Table 34 loopback check will detect that outport == inport and drop the packet. Mickey > > Regards > > > > John > > *F

Re: [ovs-dev] ovn: SFC Patch V3

2017-05-09 Thread John McDowall
h.) Any other scenarios that come to mind ? Regards John From: Mickey Spiegel <mickeys@gmail.com> Date: Monday, April 24, 2017 at 6:39 PM To: John McDowall <jmcdow...@paloaltonetworks.com> Cc: "ovs-dev@openvswitch.org" <ovs-dev@openvswitch.org> Subject: Re: [ovs-dev] o

Re: [ovs-dev] ovn: SFC Patch V3

2017-04-24 Thread Mickey Spiegel
On Mon, Apr 24, 2017 at 12:56 PM, wrote: > From: John McDowall > > > Fixed changes from Mickey's last review. > > Changes > > 1) Fixed re-circulation rules > Still a few modifications required. See comments inline. I just typed

[ovs-dev] ovn: SFC Patch V3

2017-04-24 Thread jmcdowall
From: John McDowall Fixed changes from Mickey's last review. Changes 1) Fixed re-circulation rules 2) Fixed match statement - match is only applied to beginnning of chain in each direction. 3) Fixed array length of chain of VNFs. I have tested thi sup to