<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:48:01 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>[VTN-96] Flowfilter actions &quot;VTNSetPortSrcAction&quot; and &quot;VTNSetPortDstAction&quot; is not listed in the flow entries installed to the switch</title>
                <link>https://jira.opendaylight.org/browse/VTN-96</link>
                <project id="10185" key="VTN">vtn</project>
                    <description>&lt;p&gt;I observed when i create flowfilter by setting VTNSetPortSrcAction and VTNSetPortSrcAction. It is created and ping success.&lt;/p&gt;

&lt;p&gt;While giving dumpflow in mininet it is not listed.&lt;br/&gt;
In log it says Flow action was ignored.&lt;/p&gt;

&lt;p&gt;Below are the test configurations, with mininet dumpflow and attached log.&lt;/p&gt;


&lt;p&gt;How to reproduce issue:&lt;br/&gt;
configuration:&lt;/p&gt;

&lt;p&gt;Created VTN, VBR Interfaces&lt;br/&gt;
if1 portmapping - &quot;tenant-name&quot;:&quot;vtn1&quot;, &quot;bridge-name&quot;:&quot;vbr1&quot;, &quot;interface-name&quot;:&quot;if1&quot;, &quot;node&quot;:&quot;openflow:2&quot;, &quot;port-name&quot;:&quot;s2-eth1&quot;&lt;br/&gt;
if2 portmapping - &quot;tenant-name&quot;:&quot;vtn1&quot;, &quot;bridge-name&quot;:&quot;vbr1&quot;, &quot;interface-name&quot;:&quot;if1&quot;, &quot;node&quot;:&quot;openflow:2&quot;, &quot;port-name&quot;:&quot;s2-eth1&quot;&lt;/p&gt;

&lt;p&gt;Flowcondition:&lt;br/&gt;
curl --user &quot;admin&quot;:&quot;admin&quot; -H &quot;Content-type: application/json&quot; -X POST &lt;a href=&quot;http://localhost:8181/restconf/operations/vtn-flow-condition:set-flow-condition&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/operations/vtn-flow-condition:set-flow-condition&lt;/a&gt; -d &apos;{&quot;input&quot;:{&quot;operation&quot;:&quot;SET&quot;,&quot;present&quot;:&quot;false&quot;,&quot;name&quot;:&quot;cond_1&quot;,&quot;vtn-flow-match&quot;:[{&quot;vtn-ether-match&quot;:{},&quot;vtn-inet-match&quot;:&lt;/p&gt;
{&quot;source-network&quot;:&quot;10.0.0.1/32&quot;,&quot;destination-network&quot;:&quot;10.0.0.3/32&quot;}
&lt;p&gt;,&quot;index&quot;:&quot;1&quot;}]}}&apos;&lt;/p&gt;

&lt;p&gt;Flowfilter:&lt;br/&gt;
 curl -v --user &quot;admin&quot;:&quot;admin&quot; -H &quot;Accept: application/json&quot; -H &quot;Content-type: application/json&quot; -X POST &lt;a href=&quot;http://localhost:8181/restconf/operations/vtn-flow-filter:set-flow-filter&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://localhost:8181/restconf/operations/vtn-flow-filter:set-flow-filter&lt;/a&gt; -d &apos;{&quot;input&quot;: { &quot;tenant-name&quot;: &quot;vtn1&quot;, &quot;bridge-name&quot;: &quot;vbr1&quot;, &quot;interface-name&quot;: &quot;if1&quot;, &quot;vtn-flow-filter&quot;: [{&quot;condition&quot;: &quot;cond_1&quot;,&quot;index&quot;: &quot;10&quot;, &quot;vtn-pass-filter&quot;: {}, &quot;vtn-flow-action&quot;: &lt;span class=&quot;error&quot;&gt;&amp;#91;{&amp;quot;order&amp;quot;:1,&amp;quot;vtn-set-port-src-action&amp;quot;:{&amp;quot;port&amp;quot;:1}},{&amp;quot;order&amp;quot;:2,&amp;quot;vtn-set-port-dst-action&amp;quot;:{&amp;quot;port&amp;quot;:3}}&amp;#93;&lt;/span&gt;}]}}&apos;&lt;/p&gt;


&lt;p&gt;Mininet ping between host h1 and h3:&lt;br/&gt;
mininet&amp;gt; h1 ping h3&lt;br/&gt;
PING 10.0.0.3 (10.0.0.3) 56(84) bytes of data.&lt;br/&gt;
64 bytes from 10.0.0.3: icmp_seq=1 ttl=64 time=22.9 ms&lt;br/&gt;
64 bytes from 10.0.0.3: icmp_seq=2 ttl=64 time=0.776 ms&lt;/p&gt;


&lt;p&gt;Dumpflow:&lt;/p&gt;

&lt;p&gt;mininet&amp;gt; dpctl dump-flows&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;
	&lt;ul&gt;
		&lt;li&gt;
		&lt;ul&gt;
			&lt;li&gt;s1 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0x7f5600000000000f, duration=8.022s, table=0, n_packets=7, n_bytes=630, idle_age=2, priority=10,in_port=2,vlan_tci=0x0000,dl_src=5a:1a:e5:19:5d:68,dl_dst=8e:f4:bd:ac:60:73 actions=output:1&lt;br/&gt;
 cookie=0x7f56000000000010, duration=3.012s, table=0, n_packets=0, n_bytes=0, idle_age=3, priority=11,arp,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68 actions=output:2&lt;br/&gt;
 cookie=0x7f5600000000000e, duration=8.039s, table=0, n_packets=6, n_bytes=588, idle_age=2, priority=13,ip,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68,nw_src=10.0.0.1,nw_dst=10.0.0.3 actions=output:2&lt;/li&gt;
			&lt;li&gt;s2 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0x7f5600000000000f, duration=8.031s, table=0, n_packets=7, n_bytes=630, idle_age=2, priority=10,in_port=3,vlan_tci=0x0000,dl_src=5a:1a:e5:19:5d:68,dl_dst=8e:f4:bd:ac:60:73 actions=output:1&lt;br/&gt;
 cookie=0x7f56000000000010, duration=3.018s, table=0, n_packets=0, n_bytes=0, idle_timeout=300, idle_age=3, priority=11,arp,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68 actions=output:3&lt;br/&gt;
 cookie=0x7f5600000000000e, duration=8.043s, table=0, n_packets=6, n_bytes=588, idle_timeout=300, idle_age=2, priority=13,ip,in_port=1,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68,nw_src=10.0.0.1,nw_dst=10.0.0.3 actions=output:3&lt;/li&gt;
			&lt;li&gt;s3 ------------------------------------------------------------------------&lt;br/&gt;
NXST_FLOW reply (xid=0x4):&lt;br/&gt;
 cookie=0x7f5600000000000f, duration=8.038s, table=0, n_packets=7, n_bytes=630, idle_timeout=300, idle_age=2, priority=10,in_port=1,vlan_tci=0x0000,dl_src=5a:1a:e5:19:5d:68,dl_dst=8e:f4:bd:ac:60:73 actions=output:3&lt;br/&gt;
 cookie=0x7f56000000000010, duration=3.03s, table=0, n_packets=0, n_bytes=0, idle_age=3, priority=11,arp,in_port=3,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68 actions=output:1&lt;br/&gt;
 cookie=0x7f5600000000000e, duration=8.057s, table=0, n_packets=6, n_bytes=588, idle_age=2, priority=13,ip,in_port=3,vlan_tci=0x0000,dl_src=8e:f4:bd:ac:60:73,dl_dst=5a:1a:e5:19:5d:68,nw_src=10.0.0.1,nw_dst=10.0.0.3 actions=output:1&lt;/li&gt;
		&lt;/ul&gt;
		&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26476">VTN-96</key>
            <summary>Flowfilter actions &quot;VTNSetPortSrcAction&quot; and &quot;VTNSetPortDstAction&quot; is not listed in the flow entries installed to the switch</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</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="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="siva-karthik@hcl.com">Karthik Sivasamy</reporter>
                        <labels>
                    </labels>
                <created>Sat, 9 Jan 2016 13:39:39 +0000</created>
                <updated>Thu, 19 Oct 2017 21:25:12 +0000</updated>
                            <resolved>Wed, 10 Feb 2016 07:54:59 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>VTN Manager</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="53023" author="siva-karthik@hcl.com" created="Sat, 9 Jan 2016 13:39:39 +0000"  >&lt;p&gt;Attachment setport.log has been added with description: Karaf log enabled TRACE for setport action&lt;/p&gt;</comment>
                            <comment id="53021" author="hideyuki.tai@necam.com" created="Fri, 15 Jan 2016 22:51:53 +0000"  >&lt;p&gt;I think it is not a bug.&lt;/p&gt;

&lt;p&gt;As the YANG model file explains, the `vtn-set-port-dst-action&apos; and `vtn-set-port-src-action&apos; actions only affect TCP or UDP packets on IPv4.&lt;/p&gt;

&lt;p&gt;FYI: &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow-filter.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;However, it seems to me that you just sent ICMP packets which were not TCP or UDP packets.&lt;/p&gt;

&lt;p&gt;I think if you send TCP or UDP packets into your virtual bridge, you would see flow entries which have an action which changes TCP or UDP port number.&lt;/p&gt;

&lt;p&gt;So could you check your scenario again?&lt;/p&gt;</comment>
                            <comment id="53022" author="siva-karthik@hcl.com" created="Wed, 10 Feb 2016 07:54:59 +0000"  >&lt;p&gt;This is not a bug.&lt;/p&gt;

&lt;p&gt;Verified when TCP packet is genreated in mininet and TCP is send into virtual bridge, port number is set in FLowentries. &lt;br/&gt;
i.e., actions &quot;VTNSetPortSrcAction&quot; and &quot;VTNSetPortSrcAction&quot; is listed in Flowentries. &lt;/p&gt;

&lt;p&gt;Hence closing the bug.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13707" name="setport.log" size="224488" author="siva-karthik@hcl.com" created="Sat, 9 Jan 2016 13:39:39 +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>4915</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=4915]]></customfieldvalue>

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

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