On Mon, May 05, 2014 at 11:19:13PM +, Jason Ye (yisye) wrote:
> In my setup, an OVS2.0 switch is successfully connected to a
> controller w/ OF1.3. When the controller sends OFPMP_GROUP_FEATURES
> request to the switch, it returns OFError indicating
> OFPBRC_BAD_TYPE. What could be the issue he
Sorry, maybe I explained myself bad.
By using gre tunnels I created an overlay network between the openvswitches
which I also call "internal" because, except for specific events, traffic
which travels on this network will just be for hosts belonging to it.
So you say problem could be a loop?I am s
Yes, that way it works fine, I already tried it...so you confirm me that
for openvswitch to work I need at least a working external network
interface?
2014-05-05 22:51 GMT+02:00 Ben Pfaff :
> On Mon, May 05, 2014 at 10:49:31PM +0200, Pasquale Dir wrote:
> > I already read that article but that i
Problem is that for my project I need openvswitches which can be used to
make communicate internal hosts with external ones, if specific events
occur.
So my idea was the following: a generic openvswitch would have been like
-br0
---eth0
---gre0 tag2
If I would have needed to share some resource t
I have another problem.
I have an openvswitch linked to another openvswitch by a gre tunnel. This
tunnel belongs to the vlan 2. I have one Vm for each switch, each vm is
attached to the switch by a port tagged 2.
Now, everything works fine until I add my eth0 port to these openvswitches.
When I do
Ok, I hoped there was just a way to automatically turn it off...thanks
anyway.
2014-05-05 21:25 GMT+02:00 Ben Pfaff :
> On Mon, May 05, 2014 at 12:03:59PM +0200, Pasquale Dir wrote:
> > for all my bridges I've set the stp_enable option to true as I like to
> > provide multiple redundancy links.
I already read that article but that is a configuration I'd like to avoid
as I would need to double the number of my switches and ports (gre+tep for
each link).
I'd just like to know if eth0 should not be attached to the switch in order
for the gre tunnel to work or if I am doing something wrong.
On Mon, May 05, 2014 at 11:22:46PM +0200, Pasquale Dir wrote:
> Problem is that for my project I need openvswitches which can be used to
> make communicate internal hosts with external ones, if specific events
> occur.
>
> So my idea was the following: a generic openvswitch would have been like
>
On Mon, May 05, 2014 at 10:56:01PM +0200, Pasquale Dir wrote:
> Yes, that way it works fine, I already tried it...so you confirm me that
> for openvswitch to work I need at least a working external network
> interface?
I don't understand the question.
If you want a computer to interface to an ext
On Mon, May 05, 2014 at 10:49:31PM +0200, Pasquale Dir wrote:
> I already read that article but that is a configuration I'd like to avoid
> as I would need to double the number of my switches and ports (gre+tep for
> each link).
>
> I'd just like to know if eth0 should not be attached to the switc
On Mon, May 05, 2014 at 12:03:59PM +0200, Pasquale Dir wrote:
> for all my bridges I've set the stp_enable option to true as I like to
> provide multiple redundancy links.
> Anyway for my openflow application I would need to disable this behaviour
> when a controller is plugged in, as I'll handle m
On Thu, May 01, 2014 at 02:25:27PM -0400, Chen Chen wrote:
> Does ovs support gototable instruction in Openflow 1.2 or 1.3 now?
Yes.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
On Mon, May 05, 2014 at 02:58:16PM -0400, Phiho Hoang wrote:
> Hi Joe,
>
> > The 'INSTALL.Debian' and 'debian/openvswitch-switch.README.Debian' files
> in the top of the openvswitch tarball provide more detailed instructions
> for how to install it.
>
> Mininet team seems to have done a great job
Hi Joe,
> The 'INSTALL.Debian' and 'debian/openvswitch-switch.README.Debian' files
in the top of the openvswitch tarball provide more detailed instructions
for how to install it.
Mininet team seems to have done a great job of incorporating the
installation of OVS into Mininet install script.
$ m
On Mon, May 05, 2014 at 06:27:09PM +0200, Pasquale Dir wrote:
> I have another problem.
> I have an openvswitch linked to another openvswitch by a gre tunnel. This
> tunnel belongs to the vlan 2. I have one Vm for each switch, each vm is
> attached to the switch by a port tagged 2.
>
> Now, everyt
Hi, Justin
Today I have upgrade the OVS to 2.1.2 and use the vlan splinter option.
However, there is no improvement on the iperf test with vlan; the
throughput of using vlan is still half of without vlan.
During the test, I use ovs-dpctl dump-flows and observer that are
additional actions of push_
Hello,
for all my bridges I've set the stp_enable option to true as I like to
provide multiple redundancy links.
Anyway for my openflow application I would need to disable this behaviour
when a controller is plugged in, as I'll handle myself the routing through
openflow rules...would that be possib
Thank you so much, it worked.
2014-05-01 18:13 GMT+02:00 Ben Pfaff :
> On Wed, Apr 30, 2014 at 09:35:58PM +0200, Pasquale Dir wrote:
> > as long as no controller is associated to my openvswitch vlan tags assure
> > me vlan isolation.
> >
> > After setting the controller (floodlight in my case, b
I was using OpenvSwitch v 1.11.0 without problems.
But OpenvSwitch 2.0.0 and above all versions have a problem about netdev.
Altough interface is up, ovs-vswitchd logs that network is down. Problem is
reproduceable,
epair0a is Ethernet Pair. you can create it by "ifconfig epair0 create"
this comm
Have you added flows on "br2"? As per last row second column, you have
passed br0 as input.
Also share dump-flow using ovs-ofctl.
From: Hamid Tahaei
Date: Mon, 5 May 2014 21:12:05 +0800
To:
Subject: [ovs-discuss] ovs-ofctl add-flow
Hi everbody
I¹m new in ovs.
I want to connect two VMs via
Hi everbody
I’m new in ovs.
I want to connect two VMs via ovs port and ping them without connecting to
a controller. But after adding flows, they cannot see each other. Could
anybody help please
This is what Ive done:
*VM1*
root@mininet-vm:/home/mininet# ovs-vsctl show
987c42d0-eab0-43d9-a32b
21 matches
Mail list logo
