Hello,
the OVS in my mininet environment is losing packets of a flow which
sends packets to the SDN controller:
I have a linear topology consisting of: Host1 <-> OVS1 <-> OVS2 <->
Host2. Both switches are connected to an SDN controller outside of the
virtual machine where mininet is running.
Thanks for your proposal but it does not work !
regards
2017-02-27 12:36 GMT+01:00 Zhao Jun :
> Hi David,
>
> I have never used OpenStack, but I had the similar issue when I was using
> AWS EC2.
>
> Have you tried the following commands.
>
> killall dhclient && ovs-vsctl add-br mybridge -- set
Dears,
I have defined two ovs bridges, each one of them is deployed in one Virtual
Machine (VM) based on this simple topology:
Internet - OVS1 LAN OVS2 -Internet
I used the following commands for OVS1:
ovs-vsctl add-br mybridge1
ifconfig mybridge1 up
ovs-vsctl a
On Tue, Feb 28, 2017 at 04:41:02PM +0800, lg.yue wrote:
> it does not tell where errors are? not sure whether this is helpful.
The errors reported here are unusual; I have not seen them before. Can
you tell us more about your setup? Is there anything unusual about your
machine or your operat
On Mon, Feb 27, 2017 at 04:21:26PM +0100, José Luis Millán wrote:
> On Fri, Feb 24, 2017 at 6:59 PM, Ben Pfaff wrote:
>
> > On Fri, Feb 24, 2017 at 01:10:23PM +0100, José Luis Millán wrote:
> > > I am developing a simple utility tool that maintains connections with a
> > > list of switches and ad
On 03/08/2017 10:12 AM, David Gabriel wrote:
> Dears,
>
> I have defined two ovs bridges, each one of them is deployed in one
> Virtual Machine (VM) based on this simple topology:
> Internet - OVS1 LAN OVS2 -Internet
> I used the following commands for OVS1:
>
Create a bash script using cat << quotes and put your commands there and
finally bash it, that way you keep your current SSH connection and a new daemon
modifies the interfaces and ask for the new IP in the bridge.
Make sure you get the same IP you had when you ask the DHCP request with
dhclien
I checked the current python OVSDB IDL implementation, and found out that
the way local cache is handled during transaction commit is like this, as
commented in idl.py:
Committing a transaction rolls back all of the changes that it made
to
the IDL's copy of the database. If the tr
On Wed, Mar 08, 2017 at 03:25:47PM -0800, Han Zhou wrote:
> I checked the current python OVSDB IDL implementation, and found out that
> the way local cache is handled during transaction commit is like this, as
> commented in idl.py:
>
> Committing a transaction rolls back all of the change
On Wed, Mar 8, 2017 at 3:36 PM, Ben Pfaff wrote:
>
> On Wed, Mar 08, 2017 at 03:25:47PM -0800, Han Zhou wrote:
> > I checked the current python OVSDB IDL implementation, and found out
that
> > the way local cache is handled during transaction commit is like this,
as
> > commented in idl.py:
> >
>
10 matches
Mail list logo
