Hi Jan
As discussed and agreed at OVSCON, I submitted a patch to bring the userspace
connection tracker established state
In line with that of the kernel.
I used a similar patch to what I earlier suggested earlier in this thread,
adding a test and also made some documentation updates.
Some of
… I think this is wrong and using one zone per Security Group would probably
solve this specific issue.
[Darrell] Yes, using zoning differently was one suggestion back in Aug/2017 to
solve the issue.
However, there is a more fundamental problem.
Here is an
From: Jan Scheurich
Date: Saturday, November 4, 2017 at 4:54 AM
To: Darrel Ball , Rohith Basavaraja
Cc: "d...@openvswitch.org"
Subject: RE: [ovs-discuss] Conntrack issue in OVS (2.6)+DPDK
Hi
Hi Jan/Darrell,
Sorry I couldn’t respond earlier as I was on PTO on Friday and didn’t had mail
access.
Thanks, Jan for detailing the problem and providing the examples. I also think
It will be good if we can get some time to discuss this during OVS conference.
I am still catching up on all the
Hi Darrel,
The example pipeline I crafted was not meant to be a realistic conntrack
application but to demonstrate the semantic differences between userspace and
kernel implementation and to discuss our problems with the current
documentation.
I fully agree with your proposal for a proper
From: Jan Scheurich
Date: Friday, November 3, 2017 at 6:22 AM
To: Darrel Ball , Rohith Basavaraja
Cc: "d...@openvswitch.org"
Subject: RE: [ovs-discuss] Conntrack issue in OVS (2.6)+DPDK
Hi
Hi Darrel,
I have now been able to actually test the example pipelines I provided earlier.
Turns out that the first one I sent was correct. Please note that it was not
meant as realistic conntrack pipeline but just to demonstrate the misalignment
between userspace and kernel conntrack and the