Sorry for using the wrong term (LTS, not LTE) and misclaiming it
(branch-2.1
is not a LTS branch).
We just recommend you to use branch-2.1, that branch should work fine.
There is no new LTS branch for ovs.
Thanks,
Alex Wang,
On Mon, Jun 16, 2014 at 5:10 PM, Alex Wang wrote:
> Sorry for this
Sorry for this very delayed reply,
After talking within ovs-team, we think it is best to use branch-2.1
which is LTE branch of OVS. If you still observe the issue, we will
work on a fix.
Thanks,
Alex Wang,
___
discuss mailing list
discuss@openvswitch.o
Dear representative,
I checked on the vtep.xml file under the openvswitch/vtep directory.
There is a "last_error" tab saying that it will show "A human-readable
description of the last error on the connection to the manager;"
When we dig into the code, it really does not make sense. can y
Hi,
Sorry, let me explain once more with exact commands. This time, i tried a
different topology.
First i created a mininet topology (custom):
h1 = self.addHost( 'h1' )
h2 = self.addHost( 'h2' )
h3 = self.addHost( 'h3' )
h4 = self.addHost( 'h4' )
s1 = self
On Thu, Jun 05, 2014 at 05:32:47PM +0530, Arpit Kumar wrote:
> Hi all,
> I have machines set up (say m1 and m2) and an external openflow controller
> (say C).
> I have an ovs-switch on m1 which has some flow rules and the machine m2 is
> sending tcp packets to m1 via the ovs switch.
>
> When the f
