[GBP-52] DestinationMapper has L3 flow that matches on L2 - OpenDaylight JIRA

XML

Word

Printable

Details

Type: Bug
Status: Resolved
Resolution: Cannot Reproduce
Affects Version/s: unspecified
Fix Version/s: None
Component/s: General
Labels:
None
Environment:

Operating System: All
Platform: All

External issue ID:
3317
Priority:
High

Description

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.

Attachments

Gerrit Reviews

- Issue Only
- Show All Reviews
- Show Open Reviews
- Show All Issues
- Show Open Issues

No reviews matched the request. Check your Options in the drop-down menu of this sections header.

Activity

People

Assignee:: Konstantin Blagov

Reporter:: Thomas Bachman

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Due:: 05/Jun/15

Created:: 21/May/15 3:21 AM

Updated:: 15/Jun/15 4:23 AM

Resolved:: 15/Jun/15 4:23 AM