Re: [ovs-discuss] ovs_assert(classifier_is_empty(>cls)) failed when restart openvswitch service.

2017-12-08 Thread Zhanghaibo (Euler)
Hi Ben, Thanks very much for your reply. We checked patchs of bug fixes since 2.7.0 released, but did not find any patch that looks could fix the problem, so we did further investigation to this issue. Here is our findings, would please kindly give your comments? Thank you. 1. In flow

Re: [ovs-discuss] OVS 2.8.1 changes the rates of data packets!

2017-12-08 Thread Ben Pfaff
It seems like you're just jumping to conclusions here. What have you done to understand the situation? On Fri, Dec 08, 2017 at 05:59:57PM -0800, Dawood Sajjadi wrote: > when I remove the wireless interfaces from the bridge, there is no problem. > However, as soon as adding the wireless

Re: [ovs-discuss] OVS 2.8.1 changes the rates of data packets!

2017-12-08 Thread Dawood Sajjadi
when I remove the wireless interfaces from the bridge, there is no problem. However, as soon as adding the wireless interfaces to the bridge, the problem shows up. So, it seems OVS (at least) is a part of the problem. On Fri, Dec 8, 2017 at 5:55 PM, Ben Pfaff wrote: > On December

Re: [ovs-discuss] OVS 2.8.1 changes the rates of data packets!

2017-12-08 Thread Ben Pfaff
On December 8, 2017 5:53:44 PM PST, Dawood Sajjadi wrote: >I created a bridge using OVS 2.8.1 in Ubuntu 14.04. The bridge contains >4 >physical ports including one ethernet and three wireless ports. The >ethernet port is connected to a laptop that generated dummy traffic

[ovs-discuss] OVS 2.8.1 changes the rates of data packets!

2017-12-08 Thread Dawood Sajjadi
I created a bridge using OVS 2.8.1 in Ubuntu 14.04. The bridge contains 4 physical ports including one ethernet and three wireless ports. The ethernet port is connected to a laptop that generated dummy traffic using Iperf. So, the ethernet port is used as the incoming port and the generated

Re: [ovs-discuss] Failed assertion in ovs-vswitchd when running OVN

2017-12-08 Thread Ben Pfaff
Thanks for testing! I applied this to master. I don't think it needs backporting, because branch-2.8 doesn't have this assertion. On Thu, Dec 07, 2017 at 06:59:40PM -0800, Kevin Lin wrote: > The patch worked for me! (network works, and no more warnings in ovs-vswitchd) > > > On Dec 7, 2017, at

Re: [ovs-discuss] SSH over GRE tunnel, MTU 1500 devices in VMs on same physical host

2017-12-08 Thread Orabuntu-LXC
So just to update this in case it helps anyone. The reason MTU 1500 was working in this setup is because the traffic wasn't going over the GRE tunnel which as Sherlock Holmes might have said "once you have eliminated the impossible, whatever remains must be the truth" which is to say it's

Re: [ovs-discuss] ipsec_gre not working in OpenWRT

2017-12-08 Thread Ansis Atteka
I am trying to enable ipsec_gre tunnelling between two openwrt. [ANSIS}:Is the iptables rule that sets skb_mark to 1 for incoming ESP packets in effect? Are you using ufw or firewall-cmd or some other iptables pipeline where following invocation "debian/openvswitch-ipsec.init:iptables -D

[ovs-discuss] ipsec_gre not working in OpenWRT

2017-12-08 Thread José Miguel Guzmán
Hi Guys I am trying to enable ipsec_gre tunnelling between two openwrt. I created a physical and internal bridge, based on http://docs.openvswitch.org/en/latest/howto/userspace-tunneling/ (although I am using kernel space tunnelling) # Creates Internal Bridge ovs-vsctl --may-exist add-br br-int

Re: [ovs-discuss] OvS on ARM

2017-12-08 Thread José Miguel Guzmán
OK I found the reason In case it is useful for somebody else, it is because the kmod-openvswich package is not including the vport-gre.ko, vport-lisp.ko, vport-*.ko modules. When those kernel modules are loaded, tunneling works! JM El lun., 13 nov. 2017 a las 2:16, José Miguel Guzmán (<