Ben,
Thanks for the quick feedback and patch. I was going to be able to test
it in a few days but I see on the dev alias that Alex has already done
so and you guys are working through the failed unit-test.
Dang, so I take it from the nature of the patch that what you are doing
is failing the second add of the duplicate tunnel. This requires the
user of OVS to manage any duplicate tunnel usage in some other layer and
handle tracking the reference/users. Is that correct? Perfectly
reasonable solution but I love when someone else solves my problems :-)
-K
On 5/26/15 6:48 PM, Ben Pfaff wrote:
On Tue, May 19, 2015 at 01:48:24PM -0700, Keith Holleman wrote:
Running OVS 2.3.0 on Ubuntu from a debian package.
I am creating two interfaces that are tunnels with duplicate configuration
as shown below and noticed that this causes some interesting behavior.
Everything appears to work but in reality, only one of the of-ports is able
to send traffic.
I agree that that's surprising and undesirable.
I sent out a patch that I believe should fix the problem, although I
have not yet fully tested it. Would you try it? It is against master,
though I could backport it to branch-2.3 if necessary.
The patch is at:
http://openvswitch.org/pipermail/dev/2015-May/055573.html
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
