:%"PRIu32, a->queue);
}
Regards,
Ajme
On Thu, Mar 17, 2016 at 9:38 PM, Ben Pfaff <b...@ovn.org> wrote:
> You didn't mention that part. It makes a difference.
>
> It's deceptive to use the name OFPAT_ENCAP_GTP because the OFPAT_ prefix
> implies that this is a standard
wrote:
> Please don't drop the mailing list.
>
> OK, so you'll have to add code to support the new vendor actions, some
> in build-aux/extract-ofp-msgs, some in ofp-actions.c.
>
> If it's your vendor code then you can use any types you want.
>
> On Tue, Mar 15, 20
specification for details.
>
> On Wed, Mar 16, 2016 at 06:06:30PM +0530, Ajmer Singh wrote:
> > Hi Ben,
> >
> > I have started adding OFPAT_ENCAP_GTP action in ofp-actions.c file as
> > following:
> > taking reference of already added action "OFPAT_ENQUEUE&
Hi,
I have a requirement of adding GTP headers in open Vswitch source code. We
need to define 2 new actions: STRIP_GTP and ENCAP_GTP. these are the
extensions.
As per openflow specifications 1.0 and 1.1. If we add our 2 new actions
then following structure will look like as follows.
enum
-- Forwarded message --
From: Ajmer Singh <ajmersingh.t...@gmail.com>
Date: Fri, Mar 11, 2016 at 3:16 PM
Subject: Re: [ovs-dev] Where to add GTP tunnel headers in datapath flow
table of open vSwitch
To: Jesse Gross <je...@kernel.org>
Hi,
openflow1.3 specification su
EST
OFPT10_STATS_REPLY
OFPT11_STATS_REQUEST
OFPT11_STATS_REQUEST
thanks
ajmer
On Wed, Mar 9, 2016 at 3:56 AM, Jesse Gross <je...@kernel.org> wrote:
> On Sun, Feb 28, 2016 at 10:29 PM, Ajmer Singh <ajmersingh.t...@gmail.com>
> wrote:
> > Hi,
> >
>
Hi,
We want to dump the very first packet received in kernel space of open
Vswitch v.2.4. we have identified that ovs_vport_receive method
(datapath/vport.c) receives the packet in struct sk_buff structure from
eNodeB. we have added below vlogger api to print the dump.
but before that no printk
Hi,
I have added vendor extension in ONOS and now next target is to add the
same vendor extension for OVS (OpenVswitch-2.4). I have not much idea about
OVS and the code is very big ;) that's why difficult to understand or
figure out how we can add vendor extension in OVS. Can you please guide me
