https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/GBP-52 groupbasedpolicy <p>DestinationMapper has an L3 flow that is matching on what should be L2 traffic. Pinging within a subnet on the same node was causing it to match on the L3 flow, which was decrementing the TTL. It should match on the L2 flow instead.</p> <p>Operating System: All<br/> Platform: All</p> GBP-52

DestinationMapper has L3 flow that matches on L2

Bug Resolved Cannot Reproduce Konstantin Blagov Thomas Bachman Thu, 21 May 2015 03:21:51 +0000 Mon, 15 Jun 2015 04:23:35 +0000 Mon, 15 Jun 2015 04:23:35 +0000 unspecified General Fri, 5 Jun 2015 00:00:00 +0000 0 2 <p>See my comments <a href="https://jira.opendaylight.org/browse/GBP-33" title="IPv6 some features require PacketIn PacketOut for full support (currently limited)" class="issue-link" data-issue-key="GBP-33">GBP-33</a>. That should fix this.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/21673/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/21673/</a></p> <p>I believe this pastebin describes the problem, and potential solution:</p> <p><a href="http://pastebin.com/eMbnd0Ea" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/eMbnd0Ea</a></p> <p>Misunderstanding. Traffic intra-subnet is not L2. If its an IP packet, it should match on the L3 flows.</p> Development External issue ID 3317 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i0356f: