<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:31:30 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[OPNFLWPLUG-72] Packet out does not contain buffer id corresponding to the buffer id of the respective packet in.</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-72</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;Test Case:&lt;br/&gt;
=========&lt;br/&gt;
-&amp;gt; Connect two switches with 2 hosts attached to the controller&lt;br/&gt;
-&amp;gt;Install flow in the switches to punt the arp packet to the controller with max length as 40.&lt;/p&gt;

&lt;p&gt;{table=&quot;0&quot;, match=&quot;oxm&lt;/p&gt;
{eth_type=&quot;0x806&quot;}
&lt;p&gt;&quot;, dur_s=&quot;9&quot;, dur_ns=&quot;364000&quot;, prio=&quot;2&quot;, idle_to=&quot;1000&quot;, hard_to=&quot;1200&quot;, cookie=&quot;0x1&quot;, pkt_cnt=&quot;0&quot;, byte_cnt=&quot;0&quot;, insts=[apply{acts=[out&lt;/p&gt;
{port=&quot;ctrl&quot;, mlen=&quot;40&quot;}
&lt;p&gt;]}]}]}&lt;/p&gt;

&lt;p&gt;-&amp;gt; Ping from host1 to host2.&lt;/p&gt;

&lt;p&gt;The switch is sending packet-in with buffer id set to a value. The corresponding packet-out containing the payload of packet-in has buffer id set to OFP_NO_BUFFER instead of the actual value from the packet-in.&lt;/p&gt;


&lt;p&gt;The packet capture is attached.&lt;/p&gt;

&lt;p&gt;Another issue is that here the packet is malformed due to the insufficient size of the packet with no proper header. In this case should the controller send it out on an output port or simply ignore?&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Sindhuri.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Windows&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="27340">OPNFLWPLUG-72</key>
            <summary>Packet out does not contain buffer id corresponding to the buffer id of the respective packet in.</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="dbandyop@cisco.com">Debolina Bandyopadhyay</assignee>
                                    <reporter username="sindhuri.b@ericsson.com">Sindhuri B</reporter>
                        <labels>
                    </labels>
                <created>Thu, 20 Feb 2014 10:13:25 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:05 +0000</updated>
                            <resolved>Tue, 6 Jun 2017 09:27:59 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                                                                <comments>
                            <comment id="55391" author="sindhuri.b@ericsson.com" created="Thu, 20 Feb 2014 10:13:25 +0000"  >&lt;p&gt;Attachment buffer_id_issue.pcapng has been added with description: Refer to frames 3,4,5,6 for which the buffer id is not set to correct value.&lt;/p&gt;</comment>
                            <comment id="55386" author="dbandyop@cisco.com" created="Thu, 20 Mar 2014 18:50:38 +0000"  >&lt;p&gt;Sindhuri, while trying to reproduce this bug, in the packet-out - buffer_id it shows the value None and I don&apos;t see this value OFP_NO_BUFFER. Can you tell me the exact settings or configurations you have done at your end, due to which you are able to see that particular value?&lt;/p&gt;</comment>
                            <comment id="55387" author="sindhuri.b@ericsson.com" created="Fri, 21 Mar 2014 15:01:44 +0000"  >&lt;p&gt;Hi Debolina,&lt;/p&gt;

&lt;p&gt;I have used CPqD switches . You can install CPqD switch from internet.&lt;br/&gt;
Mininet command to create topology:&lt;br/&gt;
sudo mn --topo linear,2 --controller &apos;remote,ip=&amp;lt;controllerip&amp;gt;,port=6653&apos; --switch user&lt;/p&gt;

&lt;p&gt;From mininet prompt, you can use &#8220;h1 ping &#8211;c 5 h2&#8221;.  &lt;/p&gt;

&lt;p&gt;From Rest client I have configured flow to the switches:&lt;/p&gt;

&lt;p&gt;URI: &lt;a href=&quot;http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/0/flow/300&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:1/table/0/flow/300&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Xml body:&lt;/p&gt;

&lt;p&gt;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&amp;gt;&lt;br/&gt;
&amp;lt;flow xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt;&lt;br/&gt;
    &amp;lt;strict&amp;gt;false&amp;lt;/strict&amp;gt;&lt;br/&gt;
    &amp;lt;instructions&amp;gt;&lt;br/&gt;
        &amp;lt;instruction&amp;gt;&lt;br/&gt;
            &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt;&lt;br/&gt;
            &amp;lt;apply-actions&amp;gt;&lt;br/&gt;
               &amp;lt;action&amp;gt;&lt;br/&gt;
                &amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt;&lt;br/&gt;
                &amp;lt;output-action&amp;gt;&lt;br/&gt;
                    &amp;lt;output-node-connector&amp;gt;CONTROLLER&amp;lt;/output-node-connector&amp;gt;&lt;br/&gt;
                    &amp;lt;max-length&amp;gt;40&amp;lt;/max-length&amp;gt;&lt;br/&gt;
                &amp;lt;/output-action&amp;gt;&lt;br/&gt;
              &amp;lt;/action&amp;gt;&lt;br/&gt;
            &amp;lt;/apply-actions&amp;gt;&lt;br/&gt;
        &amp;lt;/instruction&amp;gt;&lt;br/&gt;
    &amp;lt;/instructions&amp;gt;&lt;br/&gt;
    &amp;lt;table_id&amp;gt;0&amp;lt;/table_id&amp;gt;&lt;br/&gt;
    &amp;lt;id&amp;gt;300&amp;lt;/id&amp;gt;&lt;br/&gt;
    &amp;lt;cookie_mask&amp;gt;255&amp;lt;/cookie_mask&amp;gt;&lt;br/&gt;
    &amp;lt;installHw&amp;gt;false&amp;lt;/installHw&amp;gt;&lt;br/&gt;
    &amp;lt;match&amp;gt;&lt;br/&gt;
        &amp;lt;ethernet-match&amp;gt;&lt;br/&gt;
            &amp;lt;ethernet-type&amp;gt;&lt;br/&gt;
                &amp;lt;type&amp;gt;2054&amp;lt;/type&amp;gt;&lt;br/&gt;
            &amp;lt;/ethernet-type&amp;gt;&lt;br/&gt;
        &amp;lt;/ethernet-match&amp;gt;        &lt;br/&gt;
    &amp;lt;/match&amp;gt;&lt;br/&gt;
    &amp;lt;hard-timeout&amp;gt;1200&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
    &amp;lt;flags&amp;gt;FlowModFlags &lt;span class=&quot;error&quot;&gt;&amp;#91;_cHECKOVERLAP=false, _rESETCOUNTS=false, _nOPKTCOUNTS=false, _nOBYTCOUNTS=false, _sENDFLOWREM=false&amp;#93;&lt;/span&gt;&amp;lt;/flags&amp;gt;&lt;br/&gt;
    &amp;lt;cookie&amp;gt;1&amp;lt;/cookie&amp;gt;&lt;br/&gt;
    &amp;lt;idle-timeout&amp;gt;1000&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
    &amp;lt;flow-name&amp;gt;Fo1&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
    &amp;lt;priority&amp;gt;2&amp;lt;/priority&amp;gt;&lt;br/&gt;
    &amp;lt;barrier&amp;gt;false&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Sindhuri.&lt;/p&gt;</comment>
                            <comment id="55388" author="abhijit2511" created="Thu, 17 Apr 2014 05:15:02 +0000"  >&lt;p&gt;Any update on this Debolina?&lt;/p&gt;</comment>
                            <comment id="55389" author="dbandyop@cisco.com" created="Thu, 17 Apr 2014 17:22:56 +0000"  >&lt;p&gt;(In reply to Abhijit Kumbhare from comment #3)&lt;br/&gt;
&amp;gt; Any update on this Debolina?&lt;/p&gt;

&lt;p&gt; We were looking into the &lt;a href=&quot;https://jira.opendaylight.org/browse/OPNFLWPLUG-72&quot; title=&quot;Packet out does not contain buffer id corresponding to the buffer id of the respective packet in.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;OPNFLWPLUG-72&quot;&gt;&lt;del&gt;OPNFLWPLUG-72&lt;/del&gt;&lt;/a&gt; which talks about the packet-out not having the buffer id for the corresponding packet-in which has the buffer id. While debugging we came across the code where the translation happens which is in the PacketInTranslator.Java from OFPlugin.&lt;br/&gt;
If you see this PacketInTranslator code, this takes in the message from the open flow and translates to mdsal message, while doing so it is not preserving the buffer id from our understanding.&lt;br/&gt;
So we were thinking to add a field in the PacketReceivedBuilder, effectively in the PackerReceiverImpl in the file PacketReceivedBuilder. We diescussed this with Michal Rehak and he mentioned to contact Ed Warnicke regarding this, as we are not sure on who else is using the PacketReceivedImpl and what implications it might have. This seems like a more architectural view question according to Michal.&lt;br/&gt;
Questions we had were:&lt;br/&gt;
1.	Is adding the field bufferid into the PacketReceivedImpl the right way to go?&lt;br/&gt;
2.	What modules should we be testing if we change this PacketReceivedImpl?&lt;br/&gt;
3.	This is something that we are still yet to debug, where is this received packet digested by mdsal and also the other half of the flow which is packet out needs to be debugged as well. Michal/Ed, if you guys know then you can point us there. We will debug as we go over the flow.&lt;/p&gt;

&lt;p&gt;We mailed Ed regarding the above questions but since its an enhancement bug, no response was received as it was not the priority that time.&lt;/p&gt;</comment>
                            <comment id="55390" author="jozef.bacigal@pantheon.tech" created="Tue, 6 Jun 2017 09:27:59 +0000"  >&lt;p&gt;No response more than 3 years. Closing.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13859" name="buffer_id_issue.pcapng" size="1960" author="sindhuri.b@ericsson.com" created="Thu, 20 Feb 2014 10:13:25 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>440</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=440]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02yw7:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>