On 5/30/15 10:19 AM, Ben Pfaff wrote:
Suppose we decided to support duplicate tunnels. Then, which one of the
set of duplicates is the ingress port for a packet received on the
tunnel? I don't know a reasonable answer.
I definitely see the potential complexity of that. I was thinking that
On Sat, May 30, 2015 at 10:16:50AM -0700, Keith Holleman wrote:
> 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
> track
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
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
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.
ovs-vsc
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.
ovs-vsc
