<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:20:50 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-150] floating IP translation should also change MAC addresses</title>
                <link>https://jira.opendaylight.org/browse/NETVIRT-150</link>
                <project id="10144" key="NETVIRT">netvirt</project>
                    <description>&lt;p&gt;This bug was discovered when trying to use learn security groups - though the bug is due to bad floating IP MAC changes.&lt;br/&gt;
We knew there are some missing MAC changes there but we were never affected - here&apos;s a classic case.&lt;/p&gt;

&lt;p&gt;Pinging from VM to 8.8.8.8:&lt;br/&gt;
Packet from VM on ingress arrives with destination MAC of internal gateway - fa:16:3e:bf:56:c7&lt;br/&gt;
This causes a rule for egress to VM to be added, matching on this source MAC&lt;/p&gt;

&lt;p&gt;However, the return ping uses the source MAC of the router gateway (10.64.0.1) - 00:1c:73:4e:d3:31&lt;br/&gt;
This shouldn&apos;t happen, in the floating IP translation the MAC of the internal gateway should be set, probably here where we change &quot;router&quot; in the metadata -&lt;br/&gt;
cookie=0x8000004, duration=2784.697s, table=25, n_packets=766, n_bytes=74900, priority=10,ip,nw_dst=10.64.98.3 actions=set_field:10.0.123.3-&amp;gt;ip_dst,write_metadata:0x222e0/0xfffffffe,goto_table:27&lt;/p&gt;

&lt;p&gt;Need to also review reverse flow - NAT from VM to outbound - should we change source MAC to router gateway? (in this case the source mac is changed to floating IP MAC in table=28, but it might be more correct this way..)&lt;/p&gt;

&lt;p&gt; cookie=0x8000004, duration=4824.160s, table=26, n_packets=0, n_bytes=0, priority=10,ip,metadata=0x222e0/0xfffffffe,nw_src=10.0.123.4 actions=set_field:10.64.99.6-&amp;gt;ip_src,write_metadata:0x222e2/0xfffffffe,goto_table:28&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="20071">NETVIRT-150</key>
            <summary>floating IP translation should also change MAC addresses</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="tomer.pearl@hpe.com">Tomer Pearl</assignee>
                                    <reporter username="alonko@hpe.com">Alon Kochba</reporter>
                        <labels>
                    </labels>
                <created>Thu, 15 Sep 2016 18:06:10 +0000</created>
                <updated>Thu, 15 Dec 2016 15:50:25 +0000</updated>
                            <resolved>Thu, 15 Dec 2016 15:50:25 +0000</resolved>
                                    <version>Boron</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="36432" author="tomer.pearl@hpe.com" created="Sun, 18 Sep 2016 13:17:17 +0000"  >&lt;p&gt;A similar issue exist when packets traverse between subnets.&lt;br/&gt;
The source mac of the packets are of the VMs and not of the router&lt;/p&gt;</comment>
                            <comment id="36433" author="koby.aizer@hpe.com" created="Thu, 15 Dec 2016 15:50:25 +0000"  >&lt;p&gt;Mac addresses were removed from SG rules, so this issue should not occur. &lt;/p&gt;

&lt;p&gt;Generally, probably need to to do MAC address changes after each L3 routing, will probably be covered as part of the DVR task for Carbon&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>6728</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=6728]]></customfieldvalue>

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

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