Re: [ovs-discuss] "unknown keyword out_port" after update to 2.5

2016-08-10 Thread Ben Warren
> On Aug 10, 2016, at 5:18 AM, DEMBLANS Mathieu wrote: > > Hello everyone, > After updating from 2.3.1 to 2.5.0, I have an issue I didn’t previously had. > When I try to add a new rule containing the “out_port” parameter in ofctl, I > obtain a “ovs-ofctl: unknown keyword out_port” > An example

Re: [ovs-discuss] ovs-vswitchd disconnecting UNIX socket

2016-04-23 Thread Ben Warren
Thank you very much! That’s all I need to know. > On Apr 23, 2016, at 2:07 PM, Ben Pfaff wrote: > > On Sat, Apr 23, 2016 at 11:45:12AM -0700, Ben Warren wrote: >> Thanks for the explanations! >>> On Apr 23, 2016, at 10:15 AM, Ben Pfaff wrote: >>> >>>

Re: [ovs-discuss] ovs-vswitchd disconnecting UNIX socket

2016-04-23 Thread Ben Warren
Thanks for the explanations! > On Apr 23, 2016, at 10:15 AM, Ben Pfaff wrote: > > On Fri, Apr 22, 2016 at 11:25:26PM -0700, Ben Warren wrote: >> As you can see, the disconnects happen when the datapath ID changes, >> presumably due to adding interfaces? Only the additio

[ovs-discuss] ovs-vswitchd disconnecting UNIX socket

2016-04-22 Thread Ben Warren
Hi, I’m seeing the ovs-vswitchd process disconnect its UNIX socket, and am wondering if it’s anything to worry about. My Openflow client is able to re-attach and work again, and it only seems to be at startup time. Here’s the switch log (/var/log/openvswitch/ovs-vswitchd.log: = 2016-04-23

Re: [ovs-discuss] Stripping VLAN tags in Openflow 1.1+

2016-03-10 Thread Ben Warren
On Mar 10, 2016, at 5:47 PM, Ben Pfaff wrote: > > On Thu, Mar 10, 2016 at 05:24:43PM -0800, Ben Warren wrote: >> Thanks Ben >>> On Mar 10, 2016, at 11:05 AM, Ben Pfaff wrote: >>> >>> On Thu, Mar 10, 2016 at 10:51:35AM -0800, Ben Warren wrote: >>>

Re: [ovs-discuss] Stripping VLAN tags in Openflow 1.1+

2016-03-10 Thread Ben Warren
Thanks Ben > On Mar 10, 2016, at 11:05 AM, Ben Pfaff wrote: > > On Thu, Mar 10, 2016 at 10:51:35AM -0800, Ben Warren wrote: >> Hi, >> >> I’m wondering how to strip VLAN tags when using OpenFlow version 1.1 or >> greater messaging. The “strip_vlan” action in “o

[ovs-discuss] Stripping VLAN tags in Openflow 1.1+

2016-03-10 Thread Ben Warren
Hi, I’m wondering how to strip VLAN tags when using OpenFlow version 1.1 or greater messaging. The “strip_vlan” action in “ovs-ofctl” seems to be version 1.0-only. The “parse_op_flow_mod_str()” function returns 0xa, which = (OFPUTIL_P_OF10_STD_TID | OFPUTIL_P_OF10_NXM_TID). I’ve tried the fo

Re: [ovs-discuss] Assertions/crashes in lib/cmap.* on conntrack branch

2016-01-06 Thread Ben Warren
Hi Ben, > On Jan 5, 2016, at 4:25 PM, Ben Pfaff wrote: > > On Wed, Dec 30, 2015 at 02:13:27PM -0800, Keith Holleman wrote: >> To follow up on this issue, we wanted to recreate this on a simpler host >> and setup and are able to reproduce this very easily also there. The >> information and steps

Re: [ovs-discuss] Assertions/crashes in lib/cmap.* on conntrack branch

2016-01-05 Thread Ben Warren
> On Jan 5, 2016, at 4:25 PM, Ben Pfaff wrote: > > On Wed, Dec 30, 2015 at 02:13:27PM -0800, Keith Holleman wrote: >> To follow up on this issue, we wanted to recreate this on a simpler host >> and setup and are able to reproduce this very easily also there. The >> information and steps are bel

Re: [ovs-discuss] Assertions/crashes in lib/cmap.* on conntrack branch

2015-12-17 Thread Ben Warren
gt; also able to reproduce if you, for example, reduce the number of > revalidator/handler threads to 1? > > ovs-vsctl set Open_vSwitch . other_config:n-revalidator-threads=1 > ovs-vsctl set Open_vSwitch . other_config:n-handler-threads=1 > I tried these commands, unfortunately no improve

Re: [ovs-discuss] Assertions/crashes in lib/cmap.* on conntrack branch

2015-12-16 Thread Ben Warren
any fixes. thanks, Ben > On Dec 8, 2015, at 3:00 PM, Ben Warren wrote: > > Hi Joe, > > Sorry for taking so long to get back to this. >> On Nov 23, 2015, at 6:54 PM, Joe Stringer wrote: >> >> On 20 November 2015 at 10:05, Keith Holleman >> wrote

Re: [ovs-discuss] Assertions/crashes in lib/cmap.* on conntrack branch

2015-12-08 Thread Ben Warren
Hi Joe, Sorry for taking so long to get back to this. > On Nov 23, 2015, at 6:54 PM, Joe Stringer wrote: > > On 20 November 2015 at 10:05, Keith Holleman wrote: >> >> Follow-up email here has the backtrace for the second method of >> reproduction. In this case the bridge is not deleted, it wa

Re: [ovs-discuss] writing a flow rule in OF15

2015-10-25 Thread Ben Warren
Hi Anees, Everything from “priority” on has to be a single argument according to your shell: quote it properly and don’t use any spaces. —Ben > On Oct 25, 2015, at 5:12 PM, Anees Mohsin Hadi Al-Najjar > wrote: > > Dear all, > > I am trying to write rules in latest OVS version, 2.4, and usi

Re: [ovs-discuss] conntrack marks in ovs not showing up

2015-09-17 Thread Ben Warren
Thanks for responding Joe. > On Sep 17, 2015, at 9:18 PM, Joe Stringer wrote: > > On 15 September 2015 at 23:54, Ben Warren <mailto:b...@skyportsystems.com>> wrote: >> Hi, >> >> I’m working off Justin Pettit’s ‘conntrack’ tree @ >> https://githu

[ovs-discuss] conntrack marks in ovs not showing up

2015-09-15 Thread Ben Warren
Hi, I’m working off Justin Pettit’s ‘conntrack’ tree @ https://github.com/justinpettit/ovs/tree/conntrack, and can’t seem to get marks to work. Here’s an example of a flow (FTP server) === ovs-ofctl add-flow br0 "table=3,cookie=0xb0b,priority=32000,ct_state=+new+trk,tcp,tp_dst=21 actions=ct(

Re: [ovs-discuss] conntrack feature detection

2015-09-01 Thread Ben Warren
> On Sep 1, 2015, at 11:02 AM, Ben Pfaff wrote: > > On Tue, Sep 01, 2015 at 10:55:51AM -0700, Justin Pettit wrote: >> >>> On Aug 31, 2015, at 8:40 PM, Ben Warren wrote: >>> 1. Is there a way, apart from parsing the output of ‘ovs-ofctl >>> —version’

[ovs-discuss] conntrack feature detection

2015-09-01 Thread Ben Warren
Hi, It’s exciting to see conntrack support being accepted in the Linux kernel. We’ve been building based on the justinpettit/ovs tree and so far it works like a charm. Nice work! Two questions: 1. Is there a way, apart from parsing the output of ‘ovs-ofctl —version’ to determine if the instal