Re: [ovs-discuss] Preserve vxlan headers when sending to a non-vxlan port on bridge?

2015-08-21 Thread Sam Hague
On Fri, Aug 21, 2015 at 8:57 PM, Jesse Gross wrote: > On Thu, Aug 20, 2015 at 1:58 PM, Sam Hague wrote: > > > > > > On Thu, Aug 20, 2015 at 1:32 PM, Jesse Gross wrote: > >> > >> On Thu, Aug 20, 2015 at 8:20 AM, Sam Hague wrote: > >> > Is it possible to send vxlan encapsulated packets to a brid

Re: [ovs-discuss] Preserve vxlan headers when sending to a non-vxlan port on bridge?

2015-08-21 Thread Jesse Gross
On Thu, Aug 20, 2015 at 1:58 PM, Sam Hague wrote: > > > On Thu, Aug 20, 2015 at 1:32 PM, Jesse Gross wrote: >> >> On Thu, Aug 20, 2015 at 8:20 AM, Sam Hague wrote: >> > Is it possible to send vxlan encapsulated packets to a bridge port and >> > keep >> > the vxlan headers? >> >> It's not possibl

[ovs-discuss] Is there a way to set vxlan tunnel dst_port via flow?

2015-08-21 Thread Sam Hague
Is there a way to set the dst_port of the tunnel via flows? I know you can use "options:dst_port=xxx" to set it on the bridge port. ovs-ofctl will take options:dst_port=flow but I can't find what it would take to actually set the port in the flow. I imagine not since I can only see fields like "tu

[ovs-discuss] Open vSwitch balance-slb bond mode with two upstream switches

2015-08-21 Thread Jason Burns
I hope this is the right forum to ask this question. If not - feel free to direct me elsewhere. Can the balance-slb bond mode in Open vSwitch be used for a bond connected to two separate upstream switches? When I read the documentation [1] it states that only active-backup can be used to conne

Re: [ovs-discuss] openvswitch install on centos 6.6 issue

2015-08-21 Thread Gurucharan Shetty
Okay, then I was wrong about branch 2.4 supporting Centos 6.6. I have CC'd a couple of Kernel developers that will know the correct answer. On Fri, Aug 21, 2015 at 12:03 PM, ShapeHost wrote: > Hello, > > Thanks for the information, i tested the new 2.4. and i have the same > problem. :( > > /

[ovs-discuss] Open vSwitch 2.4.0 Available

2015-08-21 Thread Justin Pettit
The Open vSwitch team is pleased to announce the release of Open vSwitch 2.4.0: http://openvswitch.org/releases/openvswitch-2.4.0.tar.gz This release contains the largest number of new features of an Open vSwitch release. A few feature highlights of 2.4.0 include: - Support for the Rapid

Re: [ovs-discuss] openvswitch install on centos 6.6 issue

2015-08-21 Thread Gurucharan Shetty
On Fri, Aug 21, 2015 at 5:02 AM, ShapeHost wrote: > Hello, > > I have some problem with openvswitch install on centos 6.6 > 2.6.32-573.3.1.el6.x86_64. > > I tried to install many version of OVS like 1.9.0, 1.9.3, 1.10.0, 2.1.1, > 2.3.0. From what I understand, Centos6.6 is not supported with 2.3

[ovs-discuss] openvswitch install on centos 6.6 issue

2015-08-21 Thread ShapeHost
Hello, I have some problem with openvswitch install on centos 6.6  2.6.32-573.3.1.el6.x86_64. I tried to install many version of OVS like 1.9.0, 1.9.3, 1.10.0, 2.1.1, 2.3.0. Every time i have problems on this line : -- Starting Line # -

[ovs-discuss] OVS with DPDK 2.1.0

2015-08-21 Thread Paweł Bacławski
Hello, could you please tell me if OVS is already compatibile with recently released DPDK 2.1.0? Or what sould I do to make it work, when I am receiving "cannot link with dpdk" error - DPDK 2.0.0 works for me. Kind regards, Pawel Baclawski ___ discuss m

Re: [ovs-discuss] Leaking packets from one bridge to another or how can I isolate networks with OVS?

2015-08-21 Thread Ben Pfaff
On Fri, Aug 21, 2015 at 08:41:29AM +0200, Peter Schmitt wrote: > Hi, > thank you for the answer. Yes I saw that, but that does not explain why > I see > ARP requests from the host network on br1000. Maybe I did not explain > this quite well. > > Assume I have my normal home network here being 192.

Re: [ovs-discuss] questions about namespace, mtu and ingress policing for ovs internal port

2015-08-21 Thread ychen
and another step for reproducing the phenomenon is like that: 1. add port tap333 with ingress policing ovs-vsctl add-port br0 tap333 -- set interface tap333 type=internal -- set interface tap333 ingress_policing_rate=100 2. receive some packet from tap333 ifconfig tap333 up ifconfig tap

[ovs-discuss] questions about namespace, mtu and ingress policing for ovs internal port

2015-08-21 Thread ychen
I did some tests for internal ports, and found the following problems: 1. ovs ingress policing has not effect for internal port if this port is not in the default namespace 2. set interface mtu can not really change port's mtu 3. ingress policing statistics cleared after change port's mtu and add