Hi,
Try to use "set-fail-mode standalone" and don't connect to OpenFlow controller
If you want more infomation, please check "ovs-vsctl"
thx.
pichuang, Ping-Chun Huang 黃秉鈞
Wireless Internet Laboratory
Computer Center, Department of Computer Science
National Chiao Tung University
2014-10-04
Hi,
Is there anyway to run openvswitch without openflow functionality?
--
Thanks
Tim
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
Hey Andrey,
Thanks for reporting the issue, Please see my reply below,
Hello,
>
> getting the lookalike message on 2.1.3 where the problem described in
> the conversation should not take a place:
>
Yes, v2.1.3 contains the fix commit 3601bd879 (datapath: Use exact lookup
for flow_get and flow_d
On Thu, Jul 3, 2014 at 7:42 PM, Alex Wang wrote:
> I'm not exactly sure about the dp flow you have... but yes, del-flows
> will purge all flows.
>
> Also, if you stop to traffic that hitting the 'more inclusive' flow, then,
> both flows ('inclusive' and 'phantom') should be deleted.
>
> Thanks,
>
> Sorry for delayed reply,
No problem at all.
> Do you have other iface from the same VM connected to the same esx
> switch as ens224?
Yes.
vswitch0
|
|-- ens192(base) 192.168.0.11
|
|-- ens224(base) -- OVS BR br-dmz -- veth/lxc 192.168.0.12
However, ens192 is not part of OVS:
[
Guru, do you think that we should remove this dependency from the
packaging now that pretty much any in-use kernel will have the module
built in? It sounds like it would make life easier for users.
On Fri, Oct 03, 2014 at 03:13:00PM +0100, Phil Daws wrote:
> Used the sed command and that worked a
Hey Chris,
Sorry for delayed reply,
I did more experiment on the netns and ovs, worked fine,
Do you have other iface from the same VM connected to the same esx
switch as ens224?
Thanks,
Alex Wang,
___
discuss mailing list
discuss@openvswitch.org
http:
On Fri, Oct 03, 2014 at 01:55:56PM +0200, Peter Nase wrote:
> i have a basic question about queue(s) in ovs.
>
> My Mininet-Network consists of one switch (s1) and three hosts (h1, h2, h3).
> The links between the hosts and the switch are configured as 1
> Mbps and communication works fine. I
I see,
Just curious, seems that you used linux bond right? May i know the bond
mode?
Are you aware of that ovs also supports bonding? And based on your
description, I think you may want to use bond-mode=active-back... in which
case, ovs will not mac learning on pkts from the standby iface.
Tha
Hi Alex,
No, this is an openstack installation, so, linux, ivm and openvswitch.
And the problem indeed was really due to the interfaces being in
promiscuous mode. I'll rebuild my networking node with this in mind.
Krist
On Fri, Oct 3, 2014 at 5:41 PM, Alex Wang wrote:
> Hey Krist,
>
> are you u
On Fri, Oct 3, 2014 at 2:03 AM, alexandre rochat
wrote:
> Hello,
>
> I try for many days to start Open vSwitch on XenServer 6.2. By default, OVS
> is in version 1.4.6 and i can make basic commands.
>
> i make the follow command for activate him on Xen :
> xe-switch-network-backend openvswitch
>
>
Hello all,
i have a basic question about queue(s) in ovs.
My Mininet-Network consists of one switch (s1) and three hosts (h1, h2, h3).
The links between the hosts and the switch are configured as 1 Mbps
and communication works fine. I started iperf in server mode on h3 and
use h1, h2 as cl
Hello,
I try for many days to start Open vSwitch on XenServer 6.2. By default, OVS is
in version 1.4.6 and i can make basic commands.
i make the follow command for activate him on Xen : xe-switch-network-backend
openvswitch
When i make modification like add the "lo" interface on the basic bridge,
Hey Krist,
are you using esx? if so, do you add the two ports of the bond on the same
switch in esx (or vsphere)? the two ports should be added to two different
switch~
Thanks,
Alex Wang,
On Fri, Oct 3, 2014 at 2:44 AM, Krist van Besien
wrote:
> Hi,
>
> It was indeed related to the interface
> The networking hosts have two interfaces, which are bonded. This is
> the cause of the ovswitch seeing arp requests also appearing on port
> 1, and thus incorrectly learning where that mac address is.
> I disabled on link, and the problem went away.
>
> However I need both those links for redund
Used the sed command and that worked a treat. Have OVS 2.3.90 running on CentOS
7.
- Original Message -
From: "Phil Daws"
To: discuss@openvswitch.org
Sent: Friday, 3 October, 2014 9:16:28 AM
Subject: Re: [ovs-discuss] OVS and CentOS 7
Good morning,
Built RPM via Git release, 2.3
Hello all,
i have a basic question about queue(s) in ovs.
As a example my Mininet-Network consists of one switch (s1) and three
hosts (h1, h2, h3).
The links between the hosts and the switch are configured as 1 Mbps
and communication works fine. I started iperf in server mode on h3 and
use
Hi,
I am new to OVS and with everything I found, I cannot get (what I consider) a
simple setup to work:
- I create an OVS on a host, setting an IP on the default internal interface
- I can now ping from this host to any other host on that subnet
- But I cannot ping to the OVS interface from any
Hi,
It was indeed related to the interfaces being in promiscuous mode. I
managed to find the root cause, and have a workaround.
On Fri, Oct 3, 2014 at 4:32 AM, Chris Bennett wrote:
>> I'm running my LXC base & container on top of VMware ESX, and thus my vSwitch
> has to be in promiscuous mode.
Good morning,
Built RPM via Git release, 2.3.90, last night and it passed all tests which is
great :) The problem I have now is that when I try and install the package it
says:
Error: Package: openvswitch-2.3.90-1.x86_64 (/openvswitch-2.3.90-1.x86_64)
Requires: openvswitch-kmod
I re
20 matches
Mail list logo
