<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:20:27 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>[NETVIRT-4] traceroute does not work with L3 DVR</title>
                <link>https://jira.opendaylight.org/browse/NETVIRT-4</link>
                <project id="10144" key="NETVIRT">netvirt</project>
                    <description>&lt;p&gt;By default the traceroute tool uses UDP packets sent to an &quot;unlikely used port&quot; and receives ICMP TTL expired packets in response. The tool can also be configured to use TCP or ICMP. Currently, none of these methods are supported by the L3 DVR implementation. In the case of ICMP, resolving &lt;a href=&quot;https://jira.opendaylight.org/browse/OVSDB-191&quot; title=&quot;Unable to ping gateway when using L3 DVR - Lithium&quot; class=&quot;issue-link&quot; data-issue-key=&quot;OVSDB-191&quot;&gt;&lt;del&gt;OVSDB-191&lt;/del&gt;&lt;/a&gt; will work for traceroute as well. However, UDP and TCP methods require a different resolution.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="19925">NETVIRT-4</key>
            <summary>traceroute does not work with L3 DVR</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <status id="10004" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Verified</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="jhershbe">Josh Hershberg</assignee>
                                    <reporter username="jhershbe">Josh Hershberg</reporter>
                        <labels>
                    </labels>
                <created>Sun, 10 Jan 2016 13:52:21 +0000</created>
                <updated>Tue, 29 May 2018 14:58:12 +0000</updated>
                            <resolved>Wed, 15 Nov 2017 20:41:21 +0000</resolved>
                                    <version>Beryllium</version>
                                                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="36091" author="flavio@flaviof.com" created="Mon, 11 Jan 2016 14:43:02 +0000"  >&lt;p&gt;yes, we have no mechanism to correlate ttl expired events&lt;br/&gt;
to existing mac resolver service entries.&lt;/p&gt;

&lt;p&gt;known issue, but good to have it noted here!&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </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>4918</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=4918]]></customfieldvalue>

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

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