Based on your diagram, I'd think you'd want to run OVS inside VM2. This would
be configured as you described with those ovs-vsctl commands.
However, this seems like a fairly non-standard setup. Usually, the networking
is managed in the hypervisor, so VM1 and VM3 would just be wired up to OVS
I am new to openvswitch and openflow. I setup the following scenario
on a single physical machine:
VM1(veth1.0) --- (veth2.0) VM2 (veth2.1) - (veth3.0) VM3
VM1 and VM3 are two end-hosts. VM3 is to emulate an Ethernet switch.
VM2 should be controlled by ovs-vswitchd (possibly with t
On 30 May 2012 21:42, Ben Pfaff wrote:
> On Wed, May 30, 2012 at 09:38:05PM +0100, Haris Rotsos wrote:
> > I am writting to this list, because I notice a strange behaviour with
> the
> > ovs-vswitch distributed with the ubuntu/debian distribution.
> >
> > My confusion/problem(?) lies on the way t
On Wed, May 30, 2012 at 09:38:05PM +0100, Haris Rotsos wrote:
> I am writting to this list, because I notice a strange behaviour with the
> ovs-vswitch distributed with the ubuntu/debian distribution.
>
> My confusion/problem(?) lies on the way the ovs-vswitchd handles
> arptraffic. I initialize m
Hi all,
I am writting to this list, because I notice a strange behaviour with the
ovs-vswitch distributed with the ubuntu/debian distribution.
My confusion/problem(?) lies on the way the ovs-vswitchd handles
arptraffic. I initialize my switch as follows:
ovsdb-server /etc/openvswitch/conf.db --
