Hi Bertrand, I am not sure whether there is a way to decode "Experimenter Action Body" using wireshark as in this case it refers to nicira action.
The capture seems to similar to NAT action from the highlighted portion if I am correct. The set-field(hex 19 decimal 25) action is inside a ct action(Hex 23 Decimal 35). I think you can refer [1] for the packet structure for set_field. We may need to embed this in a ct action inside the Conntrackcodec similar to the way we do for NAT action. Thanks Aswin [1] https://github.com/opendaylight/openflowjava/blob/76b6a1562776b15e65d753349f95906f443e5e51/openflow-protocol-api/src/main/yang/openflow-action.yang#L116 On Wed, Sep 6, 2017 at 12:15 PM, Bertrand Low <[email protected]> wrote: > Thanks for the pointer, Aswin. > > > > I now have some wireshark captures, but the “Experimenter action body” > could do with more details. > > > > I’ve attached a screen capture of what the set-field action for ct-mark > looks like in my wireshark. I’m running wireshark v2.4.1 which comes with > the openflow_v4 dissector. I didn’t install anything in addition to the > typical installation. > > > > Is there any way to get the “Experimenter action body” decoded? The > wireshark status bar displays “Unknown action body. > (openflow_v4.action.undecoded)” when I click on the [Experimenter action > body.] level. I am able to find the value that I had set as ct-mark near > the end of the highlighted hex, but as far as the other components of the > structure goes, the demarcation is unclear to me. > > > > Thanks, > > Bertrand > > > > *From:* Aswin Suryanarayanan [mailto:[email protected]] > *Sent:* September 5, 2017 12:27 AM > *To:* Bertrand Low <[email protected]> > *Cc:* [email protected]; > [email protected] > *Subject:* Re: request for guidance on adding action set_field for > conntrack label/mark > > > > Hi Bertrand, > > You could manually add the flow to the OVS which has ODL set as manager. > Then do a wireshark capture in the interface through which ODL is connected > to OVS. You should be able to see the packet structure in flow stats in the > dump. > > Thanks > > Aswin > > > > On Sat, Sep 2, 2017 at 5:57 AM, Bertrand Low <[email protected]> wrote: > > Hi OFP dev, > > > > I’m implementing the support for Conntrack CT_LABEL and CT_MARK match and > action. So far, I’ve managed to get the match portion of the support to > work, but I am having trouble finding the right headers and structure > format for the action portion. > > > > The action that I would like to support is set_field used in the conntrack > context. > > e.g. > > action=ct(commit, exec(set_field:1->ct_mark)) > > > > I’m adding my changes to ConntrackCodec.java. In the case of the NAT > action, it has an explicit subtype (NXAST_NAT_SUBTYPE = 36), but I don’t > see an equivalent for set_field of ct_label/ct_mark. > > > > Should I be using the SET_FIELD_CODE = 25 as the type? And if so, can you > point me to how the rest of the structure is defined? > > I would appreciate some guidance on what kind of structure (headers, > format) I need to send down to the OVS node. > > > > Also, does the “set_field” have to be wrapped by an “exec” in this case? > Again, I haven’t come across an “exec” header type in the ovs code. > > > > Thanks, > > Bertrand > > > > ::DISCLAIMER:: > ------------------------------------------------------------ > ------------------------------------------------------------ > ---------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > ------------------------------------------------------------ > ------------------------------------------------------------ > ---------------------------- > > >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
